-
Type:
Bug
-
Resolution: Fixed
-
Priority:
High
-
Affects Version/s: 11.13.1
-
Component/s: Azure DevOps Connector, Features - Action, Jira Connector - Sync
-
1
-
Severity 2 - Major
-
No
Summary
Feature and Story lose Jira links in Jira Align when the ADO connector is configured with Product mapping to the same Product ID as the Program ID in Jira Align. Editing features/epics in Jira or Jira Align can cause link loss or duplicate features.
Version info
Found in:
Current Cloud version:11.13.1
Description
Issue Summary
When the ADO connector is configured with a Product mapping to the same ID as Program ID with Product ID (e.g., ID = 10), all the Story under synced epics lose their Jira links in Jira Align.
Additionally, if a synced feature is edited and saved in Jira Align, the Jira link is removed from the feature. If the same feature/epic is then updated in Jira, a duplicate feature is created in Jira Align instead of updating the original.
Steps to Reproduce
- Create a program in Jira Align with. For this example, I am using program ID = 286. After you create your program, take note of the actual program ID assigned by the system.)
- Create a Jira project mapped to Jira Align program created in step 1
- Find or create a Jira Align product with the same ID as your program.
- In ADO connector settings > Items > Feature > Product
- In Jira, create an Epic in the project from step 2 and let it sync to Align
- Create a Feature in Jira, wait for it to sync
- Create stories under the Epic in Jira and let them sync to Align.
- Edit and save the Feature in Jira Align.
- Make an update to the same Feature/Epic in Jira.
Expected Results
- Stories and features under a synced epic/feature should retain their Jira links in Jira Align.
- Editing a feature/epic in either Jira or Jira Align should not break the link or create duplicates.
Actual Results
- Stories under the synced feature/epic do not have Jira links in Jira Align.
- If a synced feature is edited and saved in Jira Align, the Jira link is removed from the feature.
- If the same feature/epic is then updated in Jira, a duplicate feature is created in Jira Align instead of updating the original
Workaround
Remove the mapped Product in the ADO connector mapping and remap it with a new ID. However, this may affect other programs with matching IDs.
- Don't delete the old Product mapping right away.
- First, create the new Product in Jira Align.
- Then, update (remap) the ADO connector to use the new Product.
- This helps avoid losing links or causing sync problems.
If you need to remove the old mapping, do so only after everything with the new Product is working.
- blocks
-
ACE-8731 Loading...
- causes
-
ALIGNSP-29051 Loading...
- is connected to
-
JAIAC-6993 Loading...
- mentioned in
-
Page Loading...