I would like to configure JIRA in such order that Priority is set to Empty on Create Issue transition, i.e. by default priority is shown is empty in Create issue screen and user must select any type of priority in order to create issue.
Could you please help me how to configure it?
Currently, I don't think that's possible. I did however find this feature request : https://jira.atlassian.com/browse/JRA-13048
* Vote, so that it will receive more attention
* Watch it, so that you will receive any and all updates
* Comment, and give your opinion on the matter
Please note that implementation of new features falls under Atlassian's Implementation of New Features Policy : https://confluence.atlassian.com/display/DEV/Implementation+of+New+Features+Policy
FWIW, in january 2016, Atlassian has indicated that they're basically not doing this. (text below copied from their ticketing system - https://jira.atlassian.com/browse/JRA-13048)
Atlassian Update – 4 January 2016
Thanks for voting and commenting on this issue. Your feedback is key to helping us understand how you use JIRA so we can continue improving your experience. We have reviewed this issue over the last few days; unfortunately we don't have any plans to support this in JIRA for the foreseeable future.
I understand that our decision may be disappointing. Please don't hesitate to contact me if you have any questions.
Product Manager, JIRA Platform
I would like to understand why Atlassian thinks that a Required field having a default value set is correct behavior. The purpose of the Required field is to make the user ENTER/SELECT a value. If you default it, the users will skip right over the field. Then Projects end up with 1000's of Jira tickets with Priority = Medium setting. How is that beneficial?
I totally agree with the guys here, that Priority field MUST be empty to force the user actively chose the prioritisation of the field. This makes sense from Project Management point of view and it is required to have.
Atlassian, you should listen more to the clients' requests.
We've done the same but the issue we have is we want the user to have to actively think about what the priority should be when adding the issue, or moving it to a new status. Having it required but empty would prompt them to think about it before it's moved through the workflow
We can run a filter to show all of those with 'Not Prioritsed' but it does rely on us going back and checking those regularly
I took your advice and added a new priority called "Not Prioritized", set it as the default value, and then added a Validator to ensure it is changed as part of Transition: Create, as shown below (2 in italics).
The transition requires the following criteria to be valid:
However, it is not working for me. :(
That is, even when I create an issue, which shows default Priority = Not Prioritized, and Submit the issue, it allows this Priority value to remain "as is", not preventing the user from being able to create the issue.
Does anyone have any idea on why it's not working?
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events