For one of our project when you create an issue and set priority field, it automatically gets changed to the default priority value. Where is this being set ?
I can set priorities on another project and they are not being overwritten but on one specific project priority is being set to a default. I'm not sure where to change this.
Thanks,
Fiona
Have you check the history tab to see if the field is being changed? It could be an automation rule.
Yes - it is not. There is nothing in history to show the change. My hunch is that the project that this is happening on is using the Default Field Configuration Scheme and it's something to do with that but I'm not sure what I would change in a new field configuration scheme to make this not happen
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
There is a default generally selected for priority but that simply chooses the priority if one is not selected. So there are no automation rules then?
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.
Ok, a bit stuck on what might be going on so can you share a few screenshots:
also, I assume if you change the priority after created it persists?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks @Jack Brickey I found the issue ! There was a workflow post-trigger function setting it to Minor !! This wasn't showing up in history or automation which is why it was so hard to find.
This answer on a related issue helped me think about checking the workflow https://community.atlassian.com/t5/Jira-Software-questions/Why-is-my-default-priority-not-selected-when-I-create-an-issue/qaq-p/1740906
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Ugh....that should never be done especially if the workflow is a default workflow. 😣
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.