4.3.  Integration for Atlassian JIRA

Table of Contents

4.3.1. Configuration
4.3.2. Synchronization

Atlassian JIRA has broad use cases, including release planning and management, bug tracking and sprint planning for agile teams. The JIRA Integration is used to automate the pushing of test results from Squish Test Center to JIRA. The JIRA Integration allows you to manually map JIRA issues to Squish Test Suites/Cases. This mapping allows for automated tasks within the JIRA platform. For example, automatically opening a defect ticket if a test uploaded to Squish Test Center has failed.

4.3.1. Configuration

Once you have downloaded JIRA, log in to Squish Test Center. Hover over your user icon, and choose Global Settings. At the bottom of the page, under Other Settings, choose JIRA. Once you have activated the JIRA integration, you should have access to the following settings.

Adding JIRA account information to Squish Test Center.

Configuration synopsis

Server URL

URL of JIRA instance

Username

JIRA Account username

Password

JIRA Account password

For the fields below, you can set the External Project Settings combo box to Default (Global) to set the default value for all JIRA projects, or, to configure a specific JIRA project, you can first select that project in the combo box.

Fields

This lets you specify which values to use during JIRA issue creation for the different custom fields of your JIRA issues. This setting expects a comma separated list of key=value pairs (e.g. Status=Open, Priority=5).

Workflow

When your JIRA platform is configured to use non-standard workflow definitions, this option can be used to let the JIRA integration know about them.

This option always needs 4 comma-separated parameters, given in this order: Active=metaID, AtransD=metaID, Disabled=metaID, DtransA=metaID, otherwise ticket creation will fail:

  • 'Active' and 'Disabled' are the names of the states which the JIRA Integration should use when updating states (in the JIRA standard workflow, these would be called 'Open=1' and 'Closed=6'). A PASSED update would lead to a ticket being 'Disabled' and a FAILED update would lead to a ticket being 'Activated'.

  • 'AtransD' and 'DtransA' are the names of the transitions leading from 'Active' to 'Disabled' state and vice versa must be given (in the JIRA standard workflow, these would be called 'CloseIssue=2' and 'ReopenIssue=3').

  • For each of these names also the <metaID> must be given, separated by '=' sign.

Filter

This field expects a custom JQL-Query. You can use this setting to select only a specific subset of Tickets which should be synchronized with Squish Test Center.

The Project Associations settings can be used to specify which JIRA Projects should be mapped to which Test Center Project. You have to select a Test Center Project in the Project dropdown which will reveal which JIRA Projects are associated to the currently selected Test Center Project. To change the association of a JIRA Project simply click on it.

If no JIRA Projects are listed, you can use the Sync Projects button to retrieve the current list of JIRA projects from your JIRA instance.

4.3.2.  Synchronization

The synchronization between Squish Test Center and JIRA can be used to achieve traceability so you can easily jump back and forth between both systems and it can be used to transfer test result information to JIRA.

Pulling causes information about the Issue Tickets in JIRA to be transferred to Squish Test Center. Once the information is in Squish Test Center you can manually map which Squish Tests are associated with which Issue Tickets. Once the associations have been made, you can get an Overview in Test Center of your Issue Tickets and the associated Test Status.

Furthermore this allows you to push Test Results to JIRA. A failed result will put the JIRA ticket into a failed state (based on the workflow settings) while a passed result will put the JIRA ticket into a resolved state. Furthermore the Description of each linked ticket will be extended with a list of Backlinks to the related test results.

Note that you can also use the testcentercmd commandline tool to perform the push and pull actions.

4.3.2.1.  Pull

Pulling mappable entities from the external system:

  • Navigate to a batch of a project and select the integration in the navigation bar. Pull entities from the associated foreign integration project by clicking Pull. You should now see a table with entries from your integration.

  • To map Squish Test Center tests to your integration entities, click the Edit button of a table entry on the rightmost Mapping column. Select tests to associate in the dialog and click Apply Changes.

4.3.2.2.  Push

For most integrations, you would want the accumulated result to be pushed to your integration system for viewing. If you have mapped an entity from your integration to Squish Test Center tests, you can manually push the results of the current batch by clicking the Push button.

4.3.2.3.  Ticket Creation

When creating tickets from Squish Test Center, the Title of the created tickets will be Test Center Created Bug for test suite followed by the name of the test item selected in Squish Test Center.