-
Bug
-
Resolution: Unresolved
-
Medium
-
None
-
11.8.1
-
2
-
Severity 3 - Minor
-
No
Issue Summary
In the indirect sync process, data from parents and grandparents should automatically sync to Jira without the need to update the Feature directly.
However, when there is a Capability exists between Feature and Epic, changing the parent Epic of that Capability does not trigger the indirect sync to Feature in Jira.
As a result, the grandparent of the Feature in Jira remains unchanged.
This is reproducible on Data Center: (yes)
Steps to Reproduce
- Make sure Program has Capability enabled
- Configure Jira Connector setting to sync Epic parent and Capability parent value using Jira custom fields.
- Sync a Feature 1 that has parent Capability Capability 1 and grandparent Epic Epic 1 to Jira.
- Confirm parent and grandparent names populate on the Feature 1 in Jira.
- In Jira Align, change the parent of the Capability 1 from Epic 1 to Epic 2.
- The grandparent name on Feature 1 in Jira will not change to Epic 2 even if you update the description of the Capability 1.
- Now, update the description of the Epic 2 or the description of the Feature 1.
- Indirect sync will trigger and grandparent name on Feature 1 be updated.
Expected Results
Indirect sync for Feature will trigger when parent of the Capability is changed.
Actual Results
Indirect sync will not trigger and will cause Feature to have previous (old) grandparent info in Jira.
Workaround
Trigger indirect sync by updating description of either the grandparent Epic or Feature directly
- relates to
-
-
- Closed
-
- causes
-
ALIGNSP-28689 You do not have permission to view this issue
| Form Name | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|