Are you in the loop? Keep up with the latest by making sure you're subscribed to Community Announcements. Just click Watch and select Articles.

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!


Align Feature not Syncing w/ Jira Cloud: 400:Bad Request, priority: The priority selected is invalid

Scenario: When a feature is create in Align, it is not syncing with Jira Cloud.

Steps taken: Verified priorities matched and the custom field id is correct

Align Priorities:

  • Not Set
  • Low
  • Medium
  • High
  • Critical

Jira Priorities:

  • Showstopper (not used with Jira Epics (Align Features)
  • Critical
  • High
  • Medium
  • Low
  • Not Set (Default)

Admin > Jira Settings > Default Jira Align story priority: customfield_10000 

This is a new issue brought to our attention today (02/28/2023), previously this was not a problem and it doesn't apply to all features.  Many are syncing as expected.

Is there another area that may need to be completed or has something changed recently in our instance of Jira Cloud or Jira Align?

Screen shots available but unable to attach to this question.

Thank you!


2 answers

For the Features that aren't syncing to Jira cloud, what does the audit log within the Feature state is the issue?  Open the Feature and click on "audit log" in the right pane to look for errors in syncing.

If it's failing on the priority, that is typically not a "customfield_XXXX" field. 

Navigate to your Jira Cloud administration gear - Issues - Priorities.  Find the priority you want it to default to and choose edit.  You should then see an "ID =" in the url.  That is the number you want to add to the "Default Jira Align story priority" box under Jira Setup tab in Align. 

Attached is one of mine.

Screenshot 2023-02-28 at 2.49.49 PM.png

Thank you Shannon, that was the first thing I looked at.  In our instance, that field has always had "customfield_xxxxx" in front of it.  I removed that and added just the ID and will watch to find out if it helps. :)

Like Shannon Wright likes this

I also should have mentioned that the audit log shows the 400 error in the title of this question.

Another thing to check is each project in Jira can have their own priority scheme.  If you have this set, you need to ensure the project it's going to has that priority in it otherwise it will fail to update it.

Thanks again Shannon, this instance of Jira was in place when I joined the organization.  To my knowledge we're not using any type of priority scheme and this is a project that has been in place and using Jira Align for a few years.  This is the first report of features not syncing because of the priority, the features with the issue are all part of the same Epic and Initiative, out of 21, only two will not sync and have this error in the activity log.

I'm officially stumped and will open a ticket.

Thank you for offering some ideas though!

0 votes
Allan Maxwell
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Feb 28, 2023

Under Admin -> Jira Settings -> Jira Setup TAB -> any Configure link ...scroll to the bottom and make sure all the Priorities from Jira are mapped.

Screenshot 2023-02-28 at 2.50.32 PM.png

Thank you Allan.  I also checked this and they are correct however, there are several old priorities that were removed when we moved from the data center to the cloud.  These are not mapped and haven't been since the migration last year.  I don't think this is the issue because this is a new problem. 

Just out of curiosity and to keep our instance current, do you know if there's a way to remove the old ones? 

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events