Release page

Release 'Title' page provides the features for management and monitoring of ticket groups and looks:

release details page

There are the following operations can be executed on this page:

  1. Opening another release details clicking on open another button and selecting a release.

  2. Expanding the release configuration clicking on details button. It expands the configuration, which can be updated (see release fields here):

    release details with configuration

    If you want to save changes, click on save button. Otherwise, collapse the configuration.

  3. Release the release clicking on Release button.

    Only releases which all attached tickets are in Migrated, Completed, or Canceled statuses can be released.

  4. Changing view perspective:

    view perspective change

    Release has two view perspectives:

    1. Integration scenarios perspective shows scenarios added to tickets attached to the release. Here you can:

      1. Add new scenario clicking on Add Scenarios button (available only if the release hasn’t been released yet). It opens Create new tickets for chosen scenarios dialog box:

        create new tickets for choosen scenarios

        In this dialog box configure properties of new tickets (see almost all of them here):

        1. Ticket creation strategy identifies how objects should be distributed between tickets: One ticket per scenario or All scenarios in one ticket.

        2. Test cases attachment strategy identifies whether test cases should be attached during tickets creation, or not: Attach all available test cases for chosen scenarios or Don’t attach any test cases. If Attach all available test cases for chosen scenarios is selected, ticket’s integration objects lookup and test cases attachment (all found test cases for resolved integration objects) will be processed for each created ticket.

          After configuring new ticket properties click on Add Scenarios. It opens 'Select integration scenarios' dialog box where you can select the objects (submit the dialog box to close it).

          If you have selected unnecessary objects, you can select them and click on Delete Scenarios button.

          Click on Save to create new ticket(s). Selected objects with all dependent objects will be attached to created ticket(s).

          Selected objects should be licensed for DevOps or Migration (see Configure Object Licenses for details).

      2. View integration scenario details clicking on the link of source integration scenario. It opens Integration Object Details page.

      3. View ticket details clicking on scenario tickets and selecting the ticket. It opens ticket page.

    2. Tickets perspective shows attached tickets and provides functionality for ticket management. Here you can:

      1. Attach tickets clicking on Attach Tickets button and selecting the tickets.

        You can attach tickets that are not associated with any release.

        Attach Tickets button is available only if the release hasn’t been released yet.

      2. Detach tickets selecting unnecessary tickets and clicking on Detach Tickets.

        Detach Tickets button is available only if the release hasn’t been released yet.

      3. View ticket details clicking on its id. It opens ticket page.

      4. Monitor ticket stages switching between Prepared, In Development, In Transport, Migrated, and Completed tabs.

        These tabs correspond to ticket stages described here.

      5. Move tickets to next stage depending on previous one:

        1. To development on Prepared tab.

        2. Start transport on In Development tab.

        3. Finish transport on In transport tab.

          To development, Start transport, and Finish transport buttons are available only if the release hasn’t been released yet.

      6. Create Development tickets from selected migration tickets on Migrated tab. It creates development tickets on target system which can be used for moving current development landscape to production.

        Create Development tickets button is available only if the release hasn’t been released yet.

      7. Migrate Transport Configuration of selected migration tickets on Migrated tab. It opens 'Migrate Transport Configurations' dialog box:

        migrate tc

        Where you can configure:

        1. Fill values of parameters inherited from target by static values from source landscape

        2. Migrate passwords if possible (PRO only)

          Migrate Transport Configuration button is available only if the release hasn’t been released yet.