How to configure permissions if users with the role tester should only be able to create bugs / CRs?

Sven Koch September 25, 2017

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 ?

1 answer

0 votes
Tarun Sapra
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
September 25, 2017

Hello Sven,

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.

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

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.

Sven Koch September 27, 2017

Hi Tarun, 

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

Suggest an answer

Log in or Sign up to answer