Tickets page

Tickets page shows all existing tickets and looks:

tickets

At least one landscape has to be created. See this page to learn how to create landscape.

Ticket ID is generated automatically based on the prefix and corresponding incremented number. Prefix can be configured through irt.config.ticket-id-prefix parameter (see Figaf Tool application running for more details).

On this page you can:

  1. Create new ticket clicking on Create Ticket button. It opens 'Create new ticket' dialog box, where the following options can be set:

    1. Title of the ticket. The same title can be used for several tickets.

    2. Release defines release, to which created ticket will be attached. See release page for details about release.

    3. Assignee defines the user, to whom the ticket will be assigned.

    4. Type defines type of new ticket. Since 2.11 release the following ticket types are available:

      1. Development is used with development within one landscape.

      2. Migration is used when it is needed to migrate objects from one landscape to another.

    5. Landscape defines a landscape for development ticket. See Landscapes page for details about landscapes.

    6. Source Landscape, Target Landscape, and Migration Landscape define landscapes for migration ticket. Defined landscapes have to satisfy the following:

      1. Source Landscape and Target Landscape have the same count of Agents (Landscape items) and do not have shared Agents.

      2. Migration Landscape must consist of two items: the 1st items from Source Landscape and Target Landscape correspondingly.

    7. External ticket id identifies an external ticket (e.g. in Jira).

    8. External ticket link defines a link on the external ticket. If you define the value, you can navigate directly to the external ticket from Figaf Tool.

    9. Description defines additional information.

    Related test suite Test Suite: Test cases for ticket <Ticket ID> is created and linked with new ticket.

  2. Resolve selected ticket(s) clicking on Resolve button or cancel them clicking on Cancel button (see Resolve or cancel several tickets).

  3. Select existing ticket(s) and delete it(them) clicking on red trash button.

    Tickets attached to any release can’t be deleted. If you want to delete such tickets, you have to detach the tickets from the release and after that delete them.

  4. View a ticket details clicking on its details button. It opens ticket page.

  5. View linked release details clicking on <Release Title>. It opens release page.

  6. Show only pending - hides tickets in a final state (COMPLETED, MIGRATED, CANCELED). The filter runs on the server and the choice is remembered per browser.

1. Resolve or cancel several tickets

Resolve and Cancel buttons process all selected tickets at once:

  • Resolve applies to tickets In transport whose active transports are all imported.

  • Cancel applies to tickets In transport or In development.

Tickets in other statuses are left out, and the confirmation message says how many tickets of the selection can be processed. Confirm the message Every ticket that can be resolved will be resolved now. For the tickets that cannot be resolved yet you will be asked which status to set. (or the same one for canceling) to start.

All tickets that can be resolved (canceled) are processed right away. If some tickets couldn’t be, the Configure statuses for unresolved tickets dialog (Configure statuses for the tickets that were not canceled for Cancel) opens and lists only those tickets together with their transports (Technical Ticket Id, Ticket Name, Technical Transport Id, Transport Status). Choose a Transition for every ticket:

  • RESOLVE - available only when the ticket can be resolved;

  • TO_DEVELOPMENT - moves the ticket back to development;

  • CANCEL - cancels the ticket;

  • SKIP - leaves the ticket as it is.

Then click on Update tickets statuses to apply the chosen statuses, or on Skip to leave all listed tickets untouched.

Tickets whose transports were imported in one batch change status together (see ticket status transitions). Such tickets are listed in the dialog together with the other tickets of the batch, even if only one of them was selected, and SKIP isn’t offered for them - the transition is chosen for the whole batch.

Resolving or canceling a ticket from its ticket page is unchanged and uses the Batch Tickets resolution dialog.