Jira Create Issue Screen not displaying defaults for Priority Field

[Jonathan D_Airo]

We have multiple projects with different Priority Schemes set for each one (with each one having a default priority value set).  If we navigate to a particular project and click on create, the priority field does correctly show its default value.

We have users that create issues across multiple projects, so they click create and then choose project from within the create issue screen. From here it does not display the default value for priority field.  They will have to choose the default value, or navigate directly to the project then click create.  It is a very minor issue, but it has been pointed out!

Is this a known bug?  

Thank You!

[Shiva Kumar Hiremath]

Hi @Jonathan D_Airo ,

The global “Create Issue” screen in Jira does not automatically refresh or update the fields based on the project selected after the initial screen load. This means that if a user selects a different project after opening the create issue screen, the default values (like priority) may not update to reflect the new project’s settings

[Jonathan D_Airo]

Thanks for the insight!  I will see if the issue remediates when I upgrade Jira to v9.12.15 soon.  

[Harshit Grover]

Hi @Jonathan D_Airo ,

This seems to be a Jira version issue . If your Jira version is old that might be the issue

I have the same setup as you mentioned in Jira Data Centre (9.12.8) and I am not facing this. 

On Create screen of any project , default value which is set for the project is visible.

Even I change the project from drop down list of create screen , default value which is set for the project is visible. 

1. You can check the version of your Jira. 

2. Should also check the default priorities again in Priority Schemes.

3. Can refresh the page of your browser after changing the project from the drop down list , which may prompt Jira to reload the context and display the correct default values.

4. You could set up an automation rule to automatically set the priority field to the correct default value when an issue is created in a project.

[Jonathan D_Airo]

Thanks, I am planning to upgrade Jira soon, possibly remediate the issue.  I will try it in our test environment, since it occurs there as well.  I suggested an automated rule, but didn't get approval for that (yet)