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

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!

Becky


Answers:
author: Shannon Wright
body: 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](https://community.atlassian.com/t5/image/serverpage/image-id/242995i8C5820BAAA957467/image-size/large?v=v2&px=999 "Screenshot 2023-02-28 at 2.49.49 PM.png")

comments: author: Rebecca Hylek
body: 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. :)


author: Rebecca Hylek
body: I also should have mentioned that the audit log shows the 400 error in the title of this question.


author: Shannon Wright
body: 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.


author: Rebecca Hylek
body: 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!


author: Allan Maxwell
body: 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](https://community.atlassian.com/t5/image/serverpage/image-id/242997iA68DEBAF67BA6BD7/image-size/large?v=v2&px=999 "Screenshot 2023-02-28 at 2.50.32 PM.png")

comments: author: Rebecca Hylek
body: 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?


Tags: cloud