Issue Summary

This is reproducible on Data Center: (yes) / (no) 

Steps to Reproduce

1. Make sure in Jira ALign - Jira setup setting the following toggle is set to unidirectional 
   1. Allow story sync from Jira Align to Jira - "Jira to Jira Align sync"
2. Now, open any story and then go to the parent feature.
3. On the parent feature, move it to the unassigned backlog (if it's scoped to a PI) or leave it as it is if it's already in the unassigned backlog. Click save.
4. Move the feature from unassigned backlog to any PI. click save
5. Now, perform any update on the story in JSW either update workflow or description or summary.

Expected Results

• Since we have a unidirectional setup thus the changes in JSW on the story should flow into Align,

Actual Results

• The story in Align stops getting any updates from Jira and goes completely out of sync. Please see the screenshot attached of the audit log of the Align story.

In the screenshot, it becomes clear that the story is considered updated even though it just inherits the PI from the parent feature but the connector considers this as an update and is now no longer pulling any updates from JIra.

This was impacting hundreds of stories for a customer as there were plenty of features moved from the unassigned backlog into a PI during the pre-PI planning stages.

The below exception is thrown in the xxxxxxx.log file:

...

Workaround

The current workaround is to make sure that the following setting is set to "bi-directional" in the Jira settings of Align.
Allow story sync from Jira Align to Jira 

And for the existing stories which are no longer in sync due to this issue and are showing errors in their Audit logs, in order to update all of them you have to follow the steps outlined in the following writeup under the heading
"How to Fix"

https://community.atlassian.com/t5/Jira-Align-articles/How-to-Resolve-quot-No-changes-were-pulled-in-from-Jira-a-Jira/ba-p/2139846