I have a JIRA project with a permissions scheme with the following access details:Any JIRA user can create an issue in this projectOnly a small subset of users can work on the issues (e.g. assign, edit, comment, resolve, close, etc.)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.

Community
Q&A
Jira
Questions
Restrict Viewing an Issue to Reporter, Assignee, and Watchers

How can I use Advanced Branching in Automation for unique results?

I created an automation a while back that sends emails daily to the assignee of any issue that is overdue. This resulted in numerous individual emails for some users and I was asked to instead send out bulk emails.

Here is my basic workflow:

When the rule is triggered, run a JQL query to find all issues that are in an active status.
I then pass the results through an IF statement checking for issues that have assignees and are currently overdue.
Within the IF, I added an Advanced Branch that does an action for each assignee from the issues that passed. (This is where I need help.)
I use the variable {{currentAssignee}} from the Advanced Branch to run a JQL lookup that returns only the issues assigned to that user.
Finally, I trigger an email with those results in bulk.

It almost works. The problem I run into is Automation doesn't filter the assignees for unique users. So if a user has five overdue issues, they will receive five identical emails with all of the issues listed.

I've searched and come up empty-handed trying to find a way to filter the list of assignees for unique ids. Any help is appreciated.

Screenshot below:

2 answers

1 accepted

5 votes

Answer accepted

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.