It's not the same without you
Join the community to find out what other Atlassian users are discussing, debating and creating.
I have a JIRA project with a permissions scheme with the following access details:
For this project I don't want any user to be able to see any issue as occasionally the issues contain sensitive information. This information should only be viewed by the reporter (could be anyone with a JIRA account) and the small subset of users who have privileges to work on issues in this project.
Where I'm having trouble is allowing the reporters to be able to view the issues they create. The issues are created successfully for any JIRA user as the reporter, but then they can't view their issues since they are not a part of the allowed user group to browse or work on issues.
In looking at the available permissions scheme choices, I don't see a way to allow reporters of issues to only view issues they create - it appears to be an all or nothing scheme for the Browse option.
Am I missing something here?
Appreciate your help pointing me in the right direction, or telling me this can't me done.
Thank you.
We have this setting working for us. You shouldn't be afraid to add relevant users to Browse Projects permission. We have added all relevant users to this setting (reporter, watchers, assignee, etc.). This should make relevant users see only the tickets which they are part of. Otherwise - they won't be able see their issues too.
Make sure they have also the Edit Issues & Add Comments, if needed.
Thank you for this. I now see that there are more granular options (e.g. specifically selecting the reporter).
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.
Actually, I think you want this: https://confluence.atlassian.com/display/JIRA/Current+Reporter+Browse+Project+Permission
If you just put "browse = reporter" into the permission scheme, it makes ALL issues in the project available to all the users who have create issue.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thank you, Nic. This is what I ended-up doing. Peter pointed me in the right direction, and you confirmed. Thanks a bunch!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
This approach requires you to have the JIRA administrative rights. The main aim of this article is to help you achieve an organized, easy-to-maintain workflows in your JIRA instance thereby, reducin...
Connect with like-minded Atlassian users at free events near you!
Find a groupConnect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.
Start an AUGYou're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.