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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.