Hi everybody,
We configured a single project with multiple issues types. Users can access the issues both via issue browser and kanban boards.
Now we have created a new issue type named "AT" in the same project. In this project we have a project role named "Sales". We need that the users in the "Sales" role to have the following policy:
- They must be able to only create issues of "AT" issue type. (If this is not possible, it isn´t a show stopper).
- An user that is in the "Sales" role must be able to only see the issues he created himself as "reporter". He must not see any issues created by the others users in the "Sales" role.
For the others users´s roles, theirs permission is set on the project permission scheme and it´s working fine for limiting the actions we need for each role.
By other articles in this community, it seems that "issue security scheme" can addess this requirement. But they are missing end-to-end instructions on how to really make it work. They only cover "pieces" of the procedure / configuration. So, I would appreciate if someone could provide the step-by-step configuration to achieve this requirement.
Our Jira version is 7.8.4.
Many Thanks,
Antonio
Antonio,
Make use of Issue Level Security.
https://confluence.atlassian.com/adminjiraserver073/configuring-issue-level-security-861253265.html
victor
Hi Victor, many thanks for you time. But this is a kind of standard answer that doens´t solve the problem alone. It´s just part of a possible solution. There are additional steps that should be applied in order to make it to work and I had some trouble in putting togheter these pieces.
In the meanwhile, I found a simpler solution. When editing a permission in the issue permission scheme, there is a "show more" option. When I clicked on this, for my surprise it presented more options, including "reporter". So, I just select it and it worked as needed.
Many Thanks,
Antonio
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.