We use Jira for software bug/remediation. The bugs are classified into 3 categories, Low, Medium or High. The reporter is the user of the software, and the assignee the software dev team. Can we restrict the ability to the software team to only be able to close a Jira with a low priority? At the moment, they are able to close all the tickets. Thank you
You can add a condition on the transition that would prevent certain groups or other requirements to be met in order to transition the issue. You can learn more here: https://confluence.atlassian.com/adminjiracloud/advanced-workflow-configuration-776636620.html
For more advance conditions you should look at JSU or ScriptRunner. These plugins allow for additional more complex conditions to be implemented.
JSU can certainly solve your concern. With JSU, you may easily create conditions that would meet a list of parameters first before a transition takes place. This way, it won't anymore close all the tickets but just those you have marked low priority.
There is no need for scripts. JSU configures workflows without coding and has an easy-to-use interface that eliminates tedious coding and time-consuming testing, debugging, and error-fixing. Perhaps you could find out more on this link: https://confluence-apps.beecom.ch/display/JSU/JSU+Configuration+Guide
Hope this helps.
Learn how to use two new reports for next-gen projects in Jira Cloud: Cumulative flow diagram and Sprint burndown chart. Ivan Teong, Product Manager, Jira Software, demos the Cumulative ...
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