Controlling access to project summary reports

If I have a permissions scheme that provides the Browse Projects privilege, how can I prevent a role or user that has that privilege from generating summary reports of issue status etc from the project Summary page ?

1 answer

1 accepted

0 votes

You can't. Not without modifying the JIRA source. Anyone with browse access can generate reports and search for those issues.

Thanks for that. I presume that I am correct in my understanding that a user can't create or edit issues in a project unless he has Browse Projects privilege for the project ?

Actually, it is possible to set it up so that people can create issues without then being able to see them. As this is immensely annoying and confusing for the users and causes a support call for almost every single issue creation, I simply don't do it. I suspect it's the same for edit, although I don't think I've ever seen that tried.

Suggest an answer

Log in or Join to answer
Community showcase
Sarah Schuster
Posted Jan 29, 2018 in Jira

What are common themes you've seen across successful & failed Jira Software implementations?

Hey everyone! My name is Sarah Schuster, and I'm a Customer Success Manager in Atlassian specializing in Jira Software Cloud. Over the next few weeks I will be posting discussion topics (8 total) to ...

3,095 views 13 18
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
Atlassian Team Tour

Join us on the Team Tour

We're bringing product updates and pro tips on teamwork to ten cities around the world.

Save your spot