QMetry for Jira v3.x issues due to sudden Jira UI changes.

Date : 29-Apr-2020

The issue is fixed. Atlassian has rolled back their changes. Now users should not face below issues on any newly created QMetry Test assets, Story or Bugs. To fix these issues on Test Assets, Story, Bugs created since 24th April (during the issue life), run QMetry Re-index for the project selecting the time frame from 24th April 2020. Furthermore, we are still in contact with the Atlassian team to get the reason behind this sudden change in the Jira APIs.

Date : 24-Apr-2020

Atlassian has made some recent changes to Jira Cloud APIs that have resulted in many QMetry functionalities to break down. The changes to Cloud APIs include – issue creation, update, and get detail APIs that are used across QMetry for Jira 3.x Cloud for creation, updating and linking processes. These APIs are used to save & fetch test case/test scenario/test run issues type details in QMetry Database.

QMetry team is working on these issues on the topmost priority to incorporate these changes in QMetry. We will keep the update posted here as we make progress on these issues. The workarounds are available and provided for the critical issues which will indirectly help the users to achieve the required outcome from the affected action.


  • Description: User would not be able to add Story, Test Case, and Test Scenario to the Test Run. After Selecting the issues and clicking on the Submit button to add them to the Test Run, they will get the error message as: 'Failed to link issue(s) with test run´'

  • Workaround: Use the Manage Test Case screen to link the Test Cases to Test Run.

  1. Navigate to Manage Test Cases screen.

  2. Select the Test Cases you want to link with Test Run and click on Bulk Update. You will see this option 'Create Test Run' & 'Add to Test Run' as shown in the attached screenshot:

  3. Select the Test Run you want to link Test Cases with. You can even create a new Test Run using the 'Create Test Run' option in Bulk Update drop-down.

  4. Users will be able to see Test Cases linked to Test Run in Test Run's detail page (Issues in Test Run).


If a user wants to link a Story/Test Scenario to a Test Run, then follow the steps given below:

  1. Go to the issue detail page of the Story or Test Scenario that you want to link to the Test Run.

  2. In the Test Run section of the Story/Test Scenario click on 'Add to Test Run'.

  3. Link the Story/Test Scenario to the required Test Run.

Issue2: Cloning a Test Run gives error “Account Id does not exist.”

  • Description: User gets an error while cloning a Test Run, they will get an error as "Failed to clone Test Run due to following error: Account ID XXXXXXXXXXXXX does not exist."

  • Workaround: Clone a Test Run using QMetry Import Export Utility:

    • Export the required Test Run using the Import-Export utility tool. To export the test run use JQL "key = <Test Run>".

    • Re-import the same Test Run with 'Import Option' as 'Create New' for the Test Run field and 'Replace All with' for the Test Case field.

Issue3: When a Test Case/Test Scenario/Test Run details are updated, the updates are not visible on the Story/Test Scenario/Test Run linkage screen or Test Execution screen.

  • Description: User updates the details of the Test Case/Test Scenario/Test Run, then updated details of the QMetry issues could not be displayed on the linked test assets detail page (Jira issues, Test Run, Test Scenario) or on the Test Execution screen.

  • Workaround: Re-indexing of the project should update most of the details of the Test Case, Test Scenario, and Test Run.

Issue4: Adding/updating the Test Steps of a Test Case on the Jira issue detail page gives an error “Internal Server Error'.

  • Description: While adding/updating the Test Steps to the Test Case, then the newly created Test Steps are not being saved on the Test Case detail page.

  • Workaround: From the Manage Test Case screen, the user can add the new Test Steps to the Test Case.

  1. Navigate to Manage Test Cases

  2. Expand the respective Test Case (+), add the steps > Save.

  3. Either user can create a new Test Case by clicking on the button “Create New Test Case“ and add the steps.