Issue Summary

In the 11.0 Release Notes, the following information is found;

Jira connector: Corrected story behavior after closing a sprint
As part of delivering suggestion JIRAALIGN-2010, we’ve updated story sync behavior between Jira and Jira Align when a sprint is closed. Consider the following scenario:
1.A story is incomplete, and belongs to a sprint in Jira.
2.The sprint is closed in Jira.
3.The incomplete story is moved to the backlog in Jira.
After a sync, the story can be found in the unassigned backlog inside of Jira Align. Previously, this story would remain in the closed sprint

Transitioning the sprint to the next sprint functions correctly as described in the r11.0 release note, but, the issue arises when the sprint is moved to the backlog within the completed sprint. In order to address this in JA, the stories in Jira must be resynced or a sync can be triggered using a JQL query from the Jira Settings integration tab after the sprint is completed.

This is reproducible on Data Center: (yes) 

Steps to Reproduce

1. Step 1. Created new project in Jira and Program in JA.
2. Step 2. Created sprint and team on Jira and JA
3. Step 3. Go to backlog in Jira and start sprint 1.
4. Step 4. Created Story on Jira and assigned the sprint 1
5. Step 5.Go to backlog in Jira and click complete sprint and select Move open issues to Backlog
   
6. Step 6. The sprint field in the story was removed, and the story was moved to the backlog section on the Backlog page.
   
7. Step 7. Checked the story in JA; the sprint remained. Went to the backlog page and confirmed that the story is listed under completed sprint, not in the unassigned backlog section.
   

Video Records - STR
https://www.loom.com/share/d0a7e0a60ba44b268868e1936d2c5815

Expected Results

The sprint of Story in JA should be moved to Unassigned backlog without extra steps

Actual Results

The sprint of story in JA still belongs to the closed sprint, not unassgined backlog

Workaround

1. make an update in Jira after the sprint is completed and the stories in JA are moved to the backlog.
2. trigger a sync with a JQL from the Jira integration tab in JA> Admin> Jira Setting, stories in JA are moved to the backlog.