You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
In Jira Align Support we would start by looking at the Audit Logs of the Story, and if the Story is synchronised with Jira, also the Jira History of that Story.
It's usually possible to determine the trigger from there.
Feel free to log a ticket with us over at https://support.atlassian.com
Looking forward to hearing from you!
Hi Kammili, I want to recognize that you may have the perception that JA "automatically changed the state and assignee of a user story", but I know for a fact that it can't do that.
You see, there are several configuration items that impact how data is updated in Jira from Jira Align. There is even a setting that will preclude JA from making ANY updates to Jira.
However, if JA is incorrectly configured or, if the Jira Admin changes the Jira configuration, without notifying the Jira Align Admin, that can make it look like the scenario you posed above.
Jira Align requires specific permissions on certain fields in Jira, as well as both forward and reverse state mapping of Jira Align states to Jira workflow states.
If these configuration items are mismatched or permissions have changed such that (a) it blocks updates to previously writable fields or (b) the Jira Align connector logic can't resolve these workflow or field update changes, a rollback will occur on the Jira Align connector. This can result (a) reverting data to the previous state and assignee or (b) bouncing a Jira Align record to the JA "Pending Approval" state, if changes result in states that are unmapped/mis-mapped.