-
Suggestion
-
Resolution: Unresolved
-
5
-
Issue Summary
When the story’s sprint is changed to Unassigned backlog in JA, the sprint field is not updated in Jira
Steps to Reproduce
- Step 1 Ensure Admin > Jira Settings > Jira Setup tab > "Allow Jira Align to assign stories to sprints" = Yes
- Step 2 Take an existing story in JA that exists in any sprint and assign it to the Unassigned Backlog & Save
- Step 3 Wait for natural sync to run
Expected Results
Story's sprint value in Jira is updated to "Blank", which puts it in the Backlog
Actual Results
The story is not updated and stays in the current sprint
Â
Additional Information
Test 1) Changed the sprint from A to B in JA and wait to sync to Jira
Result 1) Sprint is changed to B in Jira
Test 2) Removed the sprint and blank in sprint field in Jira and wait to sync in JA
Result 2) Sprint is synced to Unassigned Backlog
Test 3) Changed the sprint from A to Unassgiend Backlog in JA and wait to sync in Jira
Result3) Sprint is not updated in Jira and stays in the A (current) sprint
Â
Business impact = high :
As the Sprint is not updated on Jira, it will revert the value on Jira Align back to the Sprint that was assigned, meaning that:
JA - Change from Sprint A to Unassigned
Jira - Nothing changes
Next sync cycle, if any change is pulled from Jira, JA is reverted to Sprint A by the connector
Workaround
Currently there is no known workaround for this behavior. A workaround will be added here when available
- mentioned in
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
- relates to
-
ALIGNSP-13008 Loading...
-
ALIGNSP-16137 Loading...
- resolves
-
ALIGNSP-15453 Loading...