Meet the new BigPicture navigation
A faster, smarter, and more intuitive way to work is here. We’ve redesigned BigPicture navigation to give you a smoother experience and better access to what matters most.
→ Discover what’s new, explore key improvements, and review feature name updates on the New navigation page.
→ The rollout will happen gradually, and the previous navigation will be retired in September 2026.
Jira custom field limitations (Priorities module)
With recent Atlassian API changes, you may encounter the following limitations in the Priorities module when working with Jira custom fields.
Field values appear empty
Limitation description If you add Jira custom fields to the view in the Priorities module, their values will appear empty. This happens because the custom fields aren’t included in the relevant Jira screen.
Priority score can’t be calculated
Limitation description If you’re using a prioritization template with metrics linked to Jira fields, the priority score won’t be calculated unless those fields are added to appropriate Jira screens.
In Configuration, you can check what prioritization template is in use and see if metrics are based on Jira fields.
Solution
To resolve the above limitations, add the required fields to the appropriate Jira screens. See full instructions in the Add a field to a screen Jira article.
If you can’t access Jira settings, contact your Jira admin.
Once the necessary fields are added to Jira screens:
The values of Jira fields added to the column view will be visible.
The priority score will be calculated when a prioritization template based on Jira fields is in use.