Changing Project in Create Screen Ignores the Default Priority

[PeteToscano]

For quite a while now, we've been dealing with a problem with create screens in our Jira DC instance. Do others see this problem? 

Whenever someone opens a new issue in a create screen and changes the project to anything other than the one the screen opened on, the priority on the redrawn screen goes from the starting project's default priority to the first priority in the new project's priority set. 

For example, our HELP project has four priorities: 

• Immediate
• High
• Medium
• Low

The default is Medium. If someone clicks on the Create button and the project is already set to HELP, then the priority on the form is the correct default: Medium. However, if the create screen is on any other project and the user changes the project to HELP, the priority field defaults to Immediate. Closing the create screen and reopening it raises the correct priority. 

This behavior is not specific to our HELP project. Switching to any other project displays the same behavior. 

Of course, users don't necessarily notice this field, so we frequently have to follow up to verify the set priority, and the staff is becoming inured to seeing the Immediate priority because 95% of the time, it's unintentional. 

I've tested this on a Mac using Safari, Firefox, and Chrome. We're running Jira Software DC 9.12.18.

Do others have this problem? If so, is it fixed in newer versions?

Thanks,
Pete

[Radek Dostál]

https://jira.atlassian.com/browse/JRASERVER-70389

There are multitudes of duplicates and similar bugs over the time. I kind of lost track what does or doesn't get "refreshed" when you switch project/issue type, but priority is on that list.

[Mirek]

Well not quite sure if this is a bug since Jira have it own logic of setting default priority. Here are some documents that describe that a little bit

https://support.atlassian.com/jira/kb/how-jira-selects-the-default-priority-for-the-issue-even-when-default-priority-is-set-to-none/

https://support.atlassian.com/jira/kb/how-does-jira-allocate-a-priority-to-a-jira-ticket-if-no-default-priority-is-set/

Overall I think it is a pretty common question that is why docs were created. 

Example of a similar "problem" -> https://community.atlassian.com/forums/Jira-questions/Why-is-my-default-priority-not-selected-when-I-create-an-issue/qaq-p/1740906

So maybe you can verify exact order or add some new priories and check how this would behave?