Issue Summary

• If the current Jira Sprint is being set to completed, but not all stories associated to that sprint are Done/Completed, then Jira pops-up a wizard to assist with moving the stories to the next sprint
• If the stories are moved using this wizard, and that next Jira sprint is immediately started then the stories in Jira Align (JA) can end up losing their sprint association and being sent to the backlog
• A review of the JA Audit log for an affected story will show the following sequence
  • Shortly after the story changed sprint in Jira, the Jira Connector moved the JA story correctly from the old sprint to the new sprint
  • The next update in the audit log recorded that the Jira Connector changed the sprint of the story from the old sprint again but this time to [], to the backlog. Note: this log entry may not be immediately after the first log entry, but can be after a short delay, as it depends on when the board sync timer next runs.
  • There is no entry in the audit log showing the sprint moving back from the new sprint to the old sprint first.
  • The image below shows the sequence as displayed on screen, where, in the example, the old sprint is 2527, and the new one as 2534 and it can be seen that the spring changes from 2527 twice but never changes from 2534. A time gap between the changes of 5 minutes is also shown in the example

• If no further action is taken, then the JA Story will remain in the backlog and will not match the sprint set in Jira, however while in this state:
  • any new sync of the story from Jira to JA will set the sprint back to the correct new sprint in JA (so fixes the problem)
  • any new sync of the story from JA to Jira may move the story to the backlog in Jira

Steps to Reproduce

1. Using the current active sprint in Jira, make sure that there pending (not Done) stories associated to the active sprint and that the statuses and sprint assignments of the pending stories show correctly in JA
2. Make that the next sprint exists in Jira and is correctly mapped to a JA sprint
3. Close the active sprint in Jira, and use the pop-up wizard to move the pending stories to the next sprint.
4. Immediately start that next sprint
5. Wait at least an hour (or run a Sync Board Now operation) and check to see if the sprint assigned to the related JA story is still set (if you check too soon you may see either the original active sprint still set, or that the next sprint is set)

Expected Results

The JA sprint of a story that was moved between Jira Sprints should match what is set in Jira and not be set to the backlog or []

Actual Results

The Sprint of the JA story is incorrectly set the the backlog or []

Workaround

To avoid the problem:

After closing the original Jira Sprint and moving pending stories with the wizard, wait until a board sync has occurred. We suggest leaving at least an hour before starting the next Jira Sprint (or run a Sync Board now in the Jira Management area of Jira Align and let that finish)

To fix the JA sprint assignment in stories that have already been sent to the backlog

choose from one of the following:

• Use the Jira Integration page to run a JQL pull of stories in the project that were created or updated from one day before the sprint was completed in Jira
• If only a small number of affected stories, make a small change each story in Jira and wait for that change to sync to JA
• If the sprint has been removed from the Jira Stories as well, then correct the sprint assignment in Jira and wait for this to sync to JA