Some of the testers in my project are not so technical - they seem not to get it that they should only create bugs / change requests but no other issues
Is there a way to role specific limit the ability to create so specific issues ?
This isn't possible in JIRA out of the box. As permissions are based around issue operations(create, edit , updated etc) instead of specific issueTypes.
Still, with the use of plugins this can be achieved. Using client side JS this can be done with Behaviour plugin(part of script runner) or in the validation phase of the "create" transition of the workflow you can add the check that only users with QA role should only be allowed to create bugs and no other types.
thanks for your feedback!!!
1. using the Validation on the "create" transition works !
(if I validate on a permission that the QA people certainly don't have (e.g. delete all comments...) they cannot create the issue).
However, the JIRA error message names the permission is missing - and this is confusing to QA people("why on earth would someone need the permssion to delete comments while creating an issue...")... but the solution works ...
2. In did not find sufficient documentation on how to limit the creation of issues based on the behavior functionality of scriptrunner (which we have installed)
Maybe you could elaborate a little?
IMHO Atlassian should expand the validation of transitions by user groups - which would solve the problem a lot more conveniently
In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to have–in order to produce a reliable long-term roadmap. We're tur...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs