We're trying to assign priorities to work items and the option isn't even available. When we first started using Jira we were able to assign priorities to work items (Tasks, Epics, Stories, etc.) without any problem. However, at some point the ability to manage priorities for tasks disappeared. The work item priorities still show up in the boards and lists but no one is able to edit them. All new work items get a "Medium" priority by default and it can't be changed.
I have Administrator access and have tried several suggestions outlined in some of the comments/questions here. Nothing has been successful. We have a single priority schema (Default) which is associated with our spaces and it's using the default priorities.
We are pretty new to Jira so I'm sure I'm missing something easy. Again, no one can edit priorities (even Admin) but everyone can see them.
This is a known bug with a workaround: https://jira.atlassian.com/browse/JRACLOUD-98791
I applied the workaround in our Jira system and it seemed to work. Thanks for all the help, everyone.
Hi, @Richard Hurt
Check, that Priority field is on Edit screen.
Also, if you add this field on Create Issue screen, can you change it during issue creation?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Good call, worth checking both. If the scheme turns out to have multiple options and it's still stuck, screen config is probably the next thing to look at. Between those two, that should cover most cases like this
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Richard Hurt, first the immediate fix, since that's what's blocking you.
A visible-but-uneditable Priority field is almost always one of two things:
(Project settings → Details tells you which type you're on.) One of those almost always unfreezes it. Varun's point about the scheme is also worth a quick check, though you've said yours is unchanged from default.
Worth separating two things, though: setting a priority once, and keeping priorities right as work shifts. The field fixes the first. The second where a project's priorities genuinely change week to week is where most teams struggle, because a static field set once quietly goes stale.
Full disclosure, I work on Everview, that second problem is what we built for. It connects to your Jira (Jira stays your source of record) and gives you a live view where you re-prioritise across a project as things change, so priority reflects what's actually happening now instead of a label set weeks ago.
On the Atlassian Marketplace if it's useful: Everview.ai
Hope the screen fix sorts the immediate blocker either way!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Richard,
Sounds like your Priority Scheme might only have one option assigned to it — I've seen this exact thing before. If "Medium" is the only value in the scheme attached to your project, the field shows up fine but the dropdown basically has nothing else to offer, so it looks frozen even for Admins.
Worth checking: go to Jira Settings > Issues > Priority Schemes, find the one tied to your project (you can confirm which one under Project Settings > Details), and see if Medium is really the only priority listed. If so, just add the others back in (Highest, High, Low, Lowest) and it should start working again.
Let me know if that's not it and I can help dig further.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I don't think this is the problem. Both the Priority Scheme and Priorities are unchanged from the default Jira configuration.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Richard,
Since the scheme and priorities are unchanged from default, this might actually be a Team-managed vs Company-managed thing instead.
If your project is Team-managed (pretty common for newer setups), there's a known limitation — the system Priority field can't really be customized there. It's tied to the global default scheme, and there's no way to override it per-project like you can in Company-managed projects. That would explain exactly what you're seeing — visible, stuck on Medium, no way to change it even as an Admin.
Quick way to check: Project Settings > Details will tell you if it's Team-managed or Company-managed.
If it turns out to be Team-managed, most people work around it by creating their own custom field (call it something like "Priority") with the values they actually want, since the built-in one can't be touched.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
This is a Team-managed project and we don't really want to change the Priority fields (the default ones are fine). We just want to be able to set/change the priority for a specific work item.
It appears as if Jira has updated something and now we have a smaller, more concise Create Task model window. If I expand the window I can see a "Priorities" dropdown and am able to change it to whatever I need.
However, I still cannot edit it after the work item is created. The "Task" work item is configured with the Priority field in the Description fields but it still doesn't show up.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I moved the Priority field down into the Context section and there was no change. I can still set the priority when creating a work item but I cannot change it.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Richard,
Thanks for testing that. Since Priority still isn't showing up in Details at all, not even greyed out, a few things worth trying:
1. Hard refresh (Ctrl+Shift+R / Cmd+Shift+R) or try an incognito window, sometimes layout changes don't reflect right away even after saving.
2. Try creating a brand new test task and see if Priority shows up there. If it does on new tasks but not this existing one, that's a useful clue.
3. Double check the save actually stuck, reopen the Task work item type's layout settings and confirm Priority's still under Context fields and didn't revert or get dropped.
If none of that works, this is starting to look like a genuine bug rather than something you're missing, might be worth reporting to Atlassian Support at that point.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I deleted my TEST work item and created a brand new one. I was able to change the priority on creation but not after it had been created. I also tried using a completely different browser (Safari) that I had never logged into Jira with and it was the same experience; no ability to edit priority after the task was created.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Richard,
That rules out cache/browser as the cause, so this is genuinely looking like a bug at this point rather than anything on your config side. You've checked the scheme, the field placement, tested on a totally fresh item, and even a completely separate browser, so there's not much more to troubleshoot from the Community side.
Worth two things:
1. Check status.atlassian.com for any known Jira issues, there's been a broader UI/behavior rollout happening this month (part of the 2026 Summer Release) that's touched a few other areas, so it's possible this is related.
2. Raise it directly with Atlassian Support at this point, referencing everything you've already ruled out (scheme, field section, cache, multiple browsers, new item test). That'll save them time and get you a faster answer, since this looks like it needs backend investigation.
Sorry I couldn't get you all the way there, but at least you've got a clean, well-documented case to hand off to Support now.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.