You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
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
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.
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.
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!
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?