How can I restrict a project so that a reporter can only see issues they have submitted, but no others?

In my a few of my companies' JIRA projects we would like to restrict the visibility so that end users (reporters of issues) can only see the issues they have submitted themselves, but no other issues within the project.

I have been looking through the permissions settings in JIRA, and I cannot find a simple way to accomplish this. Is this actually possible in JIRA?

3 answers

1 accepted

Accepted Answer
1 vote

You need to do two things

1. Assuming you've been using the default permissions, you'll need to unpick them. Jira's default is to use the group "jira users" to say "can log in", but ALSO whack that into the role of "users" in every new project. You'll need to remove that group from every project (replacing it with other groups, or individuals as befits your permission schemes). OR, you can create a new group, whack every existing user into it and then go into Admin -> General permissions and swap it for "jira users"

2. Once you've done that, enable "reporter browse". It's off by default, whcih is why you've not seen it. See https://confluence.atlassian.com/display/JIRA/Current+Reporter+Browse+Project+Permission - Be careful though - you should ONLY use it in "Browse" in a permission scheme. For "comment", "edit", "log work" and the rest, it's fine to use the normal "Reporter".

Nic, this is exactly what I was looking for. Thanks!

If I want just a single project to "restrict a project so that a reporter can only see issues they have submitted, but no others?"...but leave every thing else in my Jira installation untouched - can I do this?

The instruction above seem to imply some global changes are required.

 

I'd rather isolate required changes to a single project.

Yes, you probably do need to make global changes - the defaults are generally set up to allow anyone who is a user to get into all the projects - you need to undo that.

Too bad - we were hoping to set up a "presonal to do" project with these characteristics.

 

Thanks for the quick reply.

0 votes
Timothy Chin Community Champion May 08, 2014

You should be creating issue level security schemes for this project (https://confluence.atlassian.com/display/JIRA/Configuring+Issue-level+Security).

In a security level, add the reporter and all internal staff so that they can view the issue.

This does rely on the users setting security correctly, or coding it to do it for them.

Atlassian use the "reporter browse" permission. It's easier and automatic.

You should be creating issue level security schemes for this project (https://confluence.atlassian.com/display/JIRA/Configuring+Issue-level+Security).

In a security level, add the reporter and all internal staff so that they can view the issue.

Suggest an answer

Log in or Sign up to answer
Community showcase
Posted Tuesday in Jira

Looking for anyone who made the switch to Data Center

The Jira Marketing team is putting together an ebook on migrating to Data Center. We're looking for pro tips on how you staffed your project team and organized your Proof of Concept. Share yo...

34 views 0 2
Join discussion

Atlassian User Groups

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!

Find my local user group

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

Groups near you