Issue Summary

When a Story's parent is changed in Jira, it doesn't update in Jira Align in certain cases. Manual custom JQL sync is needed.

Scenario 1

• Feature A was the original parent.
• Feature B is the new parent but in the Canceled state in Jira Align.
• The Story was moved from Feature A to Feature B in Jira.
• Reinstating Feature B and changing the parent for the Story had a few seconds of difference.
• When the Story was moved from Feature A to Feature B, Feature B was still in a cancelled state, and Jira Align saw the Story as without a parent.

Expected Results

The connector should handle the Story parent change from Feature A to Feature B after Feature B is reinstated.

Actual Results

1. In Jira, the Story is moved to a new parent Feature B.
2. In Jira Align, Feature B is still in the canceled state or has not been created.
3. Sync happens, and the Connector is unable to find Feature B.
4. The connector removed the parent, and the Story became an orphan.

Scenario 2

• Story 1 has parent Feature 1
• Story 1 is in project 'ABC' and Feature 1 is in project 'FGH' (note that they are in different projects)
• In Jira Plan, create a new Feature called Feature 2 and move Story 1 from Feature 1 to Feature 2
• While still in Jira Plan, go to 'Review changes' and click on 'Save selected changes in Jira.'
• This will create a new Feature 2 and change the parent of Story 1 to Feature 2 simultaneously.
• When the sync happens, Story 1 will be updated first, and then Feature 2 will be created. There are several seconds of delay between these two events, causing the Connector to not see Feature 2 when Story 1 is updated.
• This is because when the connector pulls updates from Jira, it follows the alphabetical order of the project key. For example, Story 1 is updated first because it is in project 'ABC', and Feature 2 is created later because it is in project 'FGH'.
• If I switched it so that Feature was in project 'ABC' and the Story was in project 'FGH', then it worked.

Expected Results

• The connector should handle the Story parent change from Feature 1 to Feature 2 after Feature 2 is created.

Actual Results

1. Feature 2 is created, and the parent of Story 1 is updated to Feature 2 in Jira
2. Connector sync happens
3. Story 1 got updated first, and the Connector could not find Feature 2
4. The connector removed the parent, and the Story became an orphan.
5. Feature 2 is created

Workaround

This can be fixed by running the custom JQL sync or making a small change to the description of the Story in Jira.