Open Category List

Adding Statuses In My Jira For 2 Way Integration

3 minutesread

For creating a 2-way bug tracking system integration between Applause and your Jira, you will need to provide the following statuses :

  1. Jira status that will mark the equivalent Applause bug as ‘Ready to verify’.
  2. Jira status that will resolve the equivalent Applause bug.
  3. Jira status that will be set on your Jira issue when the equivalent Applause bug verified successfully.
  4. Jira status that will be set on your Jira issue when the equivalent Applause bug failed verification.

2wayjira_flowdiagram

Editing Active Jira Workflows

If you are editing an existing, active Jira project, it is suggested that you copy or make a backup of the workflow.

Some versions of Jira may block adding outgoing transitions if the workflow is in “Draft” status (editing an active workflow). To add the transitions, you can make a copy of the workflow (under Jira Administration > Issues > Workflows). The newly copied workflow will be Inactive and will support adding the statuses and transitions described below.

Once you are done adding the transitions, you can set the Project’s Workflow to the new copy: Under Jira Administration > Projects, click the project name and to reach the Product Settings page. Then, click Add Workflow > Add Existing and select the new workflow name and the issue types (i.e. Bug). Then, Publish the changes.

 

Adding Statuses

For adding a new status in your Jira instance do the following:

  1. Login to Jira with an admin user.
  2. Press on the gear on the top-right corner and choose ‘Issues’.

1

  1. Choose ‘Statuses’ on the left menu.
  2. Click the ‘Add Status’ button.
  3. Fill the new status details in the dialog.

2

 

Adding Transitions

Now, you need to setup the transitions to/from these statuses as follows.

First, make sure that a transition exists that leads into the “Ready to Verify” status (or its equivalent in your system) from your usual workflow (i.e. “Code Merged” to “Ready to Verify”). If a transition does not exist, add it according to the directions below.

Second, add transitions between your “Ready to Verify” status (or equivalent) to the “Verify Passed” status (or its equivalent) and between your “Ready to Verify” status to the “Verify Failed” status if they are not specified. It is suggested that you disable the “Allow all statuses to transition to this one” option for both the “Verify Passed” and “Verify Failed” statuses in the workflow (so that you maintain control of when approved fix verification results trigger a transition).

Third, in case of a mismatch in the bug verification results (Passed for one tester, but then failed for a different tester), Applause will update your Jira issue status twice: once for the passed verification and second for the failed one. For supporting this functionality your Jira needs to have ‘Transitions’ between your Passed verification status and your Failed verification status.

To create a transitions between statuses, do the following:

  1. Login to Jira with an admin user.
  2. Press on the gear on the top-right corner and choose ‘Issues’.
  3. Choose ‘Workflows’ on the left menu.
  4. If you have a workflow for your project press on ‘Edit’ next to it, otherwise create a new workflow and then edit it.
  5. Click on the ‘Diagram’ button.
  6. Example: Add transition from Passed to Failed verification:
    1. Click on the ‘Add transition’ button.
    2. In the dialog, choose your verified passed Jira status as the ‘From status’ and the failed Jira status as the ‘To status’.
    3. Name the transition and press on ‘Add’.

3

  1. Example: Add transition from Failed to Passed verification:
    1. Click on the ‘Add transition’ button.
    2. In the dialog, choose your verified failed Jira status as the ‘From status’ and the passed Jira status as the ‘To status’.
    3. Name the transition and press on ‘Add’.

 

For instructions on how to set up 2 Way Jira Integration in the Applause Customer App see the help page: New Applause Platform

0
0
67
3 minutesread

Related Knowledge Base Posts