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 and Jira Status not in Sync; How to resolve it?

We have integrated Jira (Atlassian Cloud) and Jira Align. 

The Stories in Jira have already been completed and Sprint is closed in Jira but Jira Align does still showing State prior to Accepted.

What could be the issue and what is the suggested resolution?

2 answers

1 accepted

0 votes
Answer accepted
Rich Sparks Atlassian Team Sep 08, 2020

For additional details, you can read this article in Community:

And the Jira Integration guide in the Jira Align help system has even more information: 

Thanks Rich;

I do not see any issue with the mapping for individual projects.

However, I noticed that under State Mapping tap "5-Accepted" Jira Align state is not there.

I understand to initiate forceful sync up I need to use the following Jira Setting->Jira Integration->Run?

Hi Rich,

I looked into the audit log of Stories in Jira Align, which indicates old date that means current update from Jira are not syncing up.

Is there a way to force-run the update?

Is there any permission which would enable to update the "Accepted" status in Jira Align, which is grayed out in Jira Align

Rae Gibbs Atlassian Team Sep 10, 2020

Hey Vinay - If you are using Jira Cloud, there is an issue that has been going on since 9/1.  Stories that have a sprint assigned and have been updated since this date, are not syncing over to Jira Align.  Was this working prior to 9/1?  If so and you are a Jira Cloud user, you may be falling prey to this issue.  The fix will be going in the 10.78 release tomorrow.  Here is the bug for your reference, .

Thanks Rae! I got to know about this ongoing issue yesterday & awaiting for the fix release.


Additionally, I am finding some features (Jira Epics) are not syncing up with respect to "Program Increment" custom field.  Audit Log of the features includes... 

Failed to update JiraID : 46952 - Response: 400 BadRequest Json: {"errorMessages":[],"errors":{"customfield_10004":"Field 'customfield_10004' cannot be set. It is not on the appropriate screen, or unknown."}}

How to resolve it?

Rae Gibbs Atlassian Team Sep 10, 2020

First confirm in Jira that customfield_10004 is present on the create and edit screens.  That is a common culprit of that error.  If you confirm it is, then I would recommend submitting a support ticket for further investigation.

0 votes
Rich Sparks Atlassian Team Sep 08, 2020

When you set up the connection between Align and Jira, you need to tell Align how to map the Jira issue state to one of the Align states. This is done in the Administration screens and needs to be done for each Jira project that you connect to Align. (Different Jira projects may have different workflows, so that's why it is done for each project.)

For the Stories, you need to go into the Jira Align Project Administration screen (Administration | Jira Settings | Manage Projects. There you'll see the projects you've got connected to Align. Screen Shot 2020-09-08 at 12.46.48 PM.png


Then you click on "State Mapping" for the project you want. Pick the Story from the dropdown and you'll see the Align states. Pick the appropriate state from the dropdown list.

Screen Shot 2020-09-08 at 12.44.52 PM.png

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events