Understanding scenarios where external Requirements from Jira are converted to internal QMetry requirements and external Issues are removed from the QMetry project

In this article, we will explore scenarios where external Jira requirements are converted to internal in a QMetry <> Jira-integrated project, and issues from Jira are removed, along with the reasons behind these occurrences.

When do Jira-imported requirements become internal QMetry requirements (without an external key)?

1. An Integrated Jira project is removed

   • If an integrated Jira project is removed from the QMetry project, Jira requirements will be converted into internal QMetry requirements (without external keys).

2. Issue Type unmapped/removed

   • If a specific Jira issue type (e.g., story, task, epic, etc) mapped to QMetry's "Requirements" module is removed or unmapped from the integrated QMetry project, the associated/related requirements will become internal QMetry requirements.

3. Issue Type Change

   • If a requirement's issue type is changed to another issue type that is not mapped with QMetry's "Requirements" module, it will become an internal requirement.

4. Issue moved to non-integrated Jira project

   1. If a requirement is moved to a Jira project that is not integrated with QMetry, it will also become an internal requirement.

When are external issues removed?

• If these above-listed scenarios occur for Jira Issue types that are mapped with QMetry’s “Issues” module, then all the synced Jira issues in QMetry will be removed/deleted.

--

How does QMetry <> Jira sync work in the background?

QMetry relies on Jira webhooks to receive issue updates and reflect them in real-time.

1. When an issue is created in Jira, the Jira system notifies QMetry using its web-hooks, that a new issue is created - and QMetry pulls the Jira issue with all the details to QMetry.

2. Similarly, when an Issue is updated in Jira (e.g., changes to description, summary, or labels), the Jira system notifies QMetry using a webhook, and QMetry pulls the updates in the issue.

3. When an issue is moved from one Jira project to another Jira project that is NOT integrated with QMetry, Jira does not send a webhook to notify QMetry about the move of the issue. As a result, there is no way for QMetry to know that the Jira issue has been moved to another project. So QMetry keeps the issue untouched as there was no update received.

   • To address this, QMetry has given a feature to manually trigger a full sync. To do this, go to QMetry > Projects > Project/Release/Cycle > “Your_project” > Edit > “Integration” tab.

   • This will force bring those changes/updates to QMetry, and any issues moved to a Jira project not integrated with QMetry will be removed and no longer appear in QMetry.

4. If Jira Projects A and B are both integrated with different QMetry projects, and when an issue is moved from Jira Project A to Project B, Jira Project B notifies QMetry and creates the issue there. As a result, the issue will no longer appear in the QMetry project linked to Jira Project A (source), but will now appear in the QMetry project linked to Jira Project B (destination).

IMPORTANT NOTE:

• QMetry relies on webhooks sent by Jira to receive issue information and update them in QMetry. Sometimes, the webhook for one or more issues may not be received to QMetry, which could explain why certain issues or their updates may appear missing. Webhooks from Jira may fail to be sent due to factors beyond control, such as issues on the Jira side, network blips/disruptions, or other external variables. As a result, on rare occasions, you might notice missing updates.

• The manual sync feature has been purposefully designed to address such rare discrepancies. It allows users to bring in any missed updates from Jira to QMetry, particularly when external factors might occasionally disrupt the sync. We suggest running a manual sync when you notice a missing update for one or more issues, while live syncing continues to work as expected for most other issues.

How to force run manual Jira Sync?

1. Navigate to QMetry > Projects > Projects / Release / Cycle > Select “Your_project” > Edit.

2. “Integration” tab > expand the “Integration URL” > Check the box “Sync All” > click on the “Sync” icon next to it to initiate the manual “full sync” for the associated Jira projects as shown below:
   
   

   Open

   

   1. Sync All: Enabling this check-box and clicking the sync will sync complete data between QMetry and Jira (syncing all the Jira assets to QMetry).

   2. Sync: Clicking on the sync button without enabling the Sync All check-box would just sync the updated assets from Jira. The "Sync" option should be used when there are structural changes made in Jira like adding new fields, updating the existing fields in Jira layouts, or when the QMetry-Jira integration was stuck or broken due to some reason.

3. To check the sync progress.

   • Go to the Integration menu > Click on Integrations > Select the “Integration Scheduler Status” tab > Wait for all sync activities to be completed.

Once the sync is complete, the Jira data should be correctly synced in the mapped QMetry project.