Priority field missing from Issue View for Project Admin

[Max Braun]

I'm a project admin on a team-managed project and can't view or edit the Priority field inside the issue detail modal. It is completely missing from the "Details" panel, though the priority icons show up fine on our board and backlog.

I have already verified:

1. It’s not hidden in the collapsed fields section.

2. Priority is actively placed in the main layout section via the configuration gear.

Despite having admin rights and the field being on the layout, it won't render inside the ticket.

I also can't change it from the list view.

[James Gamble]

Hola Max,

Since this is a team-managed project, I wouldn’t start with the classic Jira screen scheme settings unless this turns out not to be team-managed after all. Team-managed projects handle fields through the project’s own work type and layout settings, so the first thing I’d check is the specific work type where Priority is missing.

Go to Project settings, then Work types, open the affected work type, and confirm that Priority is available there and not just visible on the board or backlog. Then open an issue of the same type, use the configure/layout option in the issue view, and make sure Priority is visible for that work type.

If Priority is already in the layout but still doesn’t render, I’d check whether you can edit other fields on that issue. If you can’t edit other fields either, this may be an Edit work items/Edit issues permission problem rather than a layout problem. Being a project admin doesn’t always mean the account has every issue permission in every project configuration.

I’d also test with a newly created issue in the same project and same work type. If Priority appears on new issues but not on old ones, it may be related to the values or migration/history of the existing issues. If it’s missing everywhere, I’d ask a Jira admin to check the project’s priority scheme and ensure that valid priorities are available.

The clue here is that the priority icons still show on the board and backlog, so Jira does know the field/value exists. The problem seems to be specific to rendering or editing Priority in the issue view.

Thanks,

James

[Max Braun]

Hi James. Yes I've configured the work types and moved Priority all over the place trying to get it to show up. I can move around the other fields without issue. This is a new project that I created that hasn't been messed with much. We have another Software Space that shows Priority and works just fine.

[James Gamble]

Hola Max,

The next thing I’d check is whether this is actually an edit-permission or priority-scheme problem in the new Software Space.

Even if you’re a project admin, I’d test whether you can edit normal issue fields inside the affected issue, not just move fields around in the layout. For example, try changing Summary, Assignee, Labels, or another editable field directly from the issue view. Atlassian's Cloud KB states that fields may be missing from the view issue screen when the user doesn’t have the Edit Issues/Edit work items permission, especially if the field doesn’t already have a value. That would also align with you not being able to change Priority in the list view.

Reference: https://support.atlassian.com/jira/kb/why-cant-i-see-certain-fields-on-the-view-issue-screen-in-jira/

Atlassian also has a related KB for cases where users can’t edit work item fields, including Priority, due to permissions, workflow restrictions, or other configuration.

Reference: https://support.atlassian.com/jira/kb/cannot-edit-work-item-fields-in-jira-cloud/

If other issue fields edit fine, then I’d compare the new Software Space against the Software Space where Priority works. Specifically, check the assigned priority scheme for each space. In Jira settings, go to Work items, then Priority schemes, and compare which scheme is assigned to the working space versus the affected space. Atlassian’s priority scheme documentation states that priority schemes control which priorities are available for a space and which default priority is assigned to newly created work items.

Reference: https://support.atlassian.com/jira-cloud-administration/docs/manage-priority-schemes/

You can also check the site priority list under Jira settings> Work items> Priorities.

Reference: https://support.atlassian.com/jira-cloud-administration/docs/manage-priorities/

I’d also create one brand-new test issue in the affected space and another in the working space, both using the same work type. If Priority appears in the working space but not in the new one, using the same account and a similar work-type layout, that’s a strong sign the issue is specific to the new space’s configuration or a Jira Cloud bug.

One other thing I found is that Atlassian has tracked inconsistencies where Priority can still appear in some places, such as boards, lists, or linked work items, while not behaving the same way in the issue view. That’s not necessarily the exact same bug, but it does mean I wouldn’t rely on the board/backlog icons as proof that the issue view is configured correctly.

Reference: https://jira.atlassian.com/browse/JRACLOUD-94709

So I’d check in this order:

• First, confirm you can edit other fields directly on the affected issue.
• Second, compare the priority scheme between the working and non-working Software Spaces.
• Third, create a clean test issue in each space with the same work type.

If those all check out and Priority still won’t render, I’d open a ticket with Atlassian Support and include these details: it’s a new team-managed Software Space, Priority is already on the work type layout, other fields render and move normally, the board/backlog show priority icons, list view editing doesn’t work for Priority, and another Software Space works correctly. That should give Support enough to investigate a backend configuration issue or a Cloud UI bug.

Thanks,

James

[Max Braun]

Thanks for your help James. Jira has been a frustrating time suck for our team since we started using it, so we just switched to something else.

[Varsha Joshi]

Hi @Max Braun 

One thing I would check/have your Jira admin check is the Screen settings where you want Priority Field to be shown. By default, I do not think that is added.

It is possible that edit view might use a different screen.

Hope this helps.