Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Default of System field is not used.

bjoern February 4, 2025 edited

Hello community,

it was considered the right thing to hide the system field Priority in some projects.
I tried to bring this back, simply by clicking Show in the screen configuration for one of those.

Prio_on_screen.PNG

So this has worked, Prio is visible and the scheme used by the Project is the Generic one, with default value Medium.

Priorities.PNG

 

 

But when I edit an item, the newly visible Priority field populates with Blocker.
Any thoughts?

Thanks a lot
Björn

1 answer

1 accepted

1 vote
Answer accepted
Trudy Claspill
Community Champion
February 4, 2025

Hello @bjoern 

Welcome to the Atlassian community.

As per the documentation:

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

...the Default Priority value is set only for newly created issues. That default value is not applied when editing issues.

If you need to set existing issues to that Priority value you could do that by filtering for the issues that currently have no Priority value, and using Bulk Change to set the value.

bjoern February 4, 2025

Had I only waited for your answer instead of trying myself for the past 3hrs (not kidding).

Kudos, Trudy

Like Trudy Claspill likes this

Suggest an answer

Log in or Sign up to answer
TAGS
atlassian, loom, loom for training, loom for teaching, video training, async learning, online education, screen recording, loom tutorials, loom use cases, atlassian learning, team training tools, instructional video, virtual training tools

🛗 Elevate Your Training and Enablement with Loom

Join us June 26, 11am PT for a webinar with Atlassian Champion Robert Hean & Loom’s Brittany Soinski. Hear tips, stories, and get your burning questions answered. Learn how Loom makes training and enablement easier. Don’t miss it!

Register today
AUG Leaders

Atlassian Community Events