Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Jira Align automatically changed the state and assignee of user story

Jira Align automatically changed the state and assignee of user story

2 answers

0 votes
Heidi Hendry Atlassian Team Mar 16, 2022

Hi Kammili,

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

Looking forward to hearing from you!

0 votes
Matt Magee Atlassian Team Mar 16, 2022

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.

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events