JIRA's system reports permissions

I need the ability to control users access to the default system reports. But I do not see where this can be accomplished.

3 answers

1 accepted

Thanks for looking into.

1 vote

Ah, ok, so removing them completely is a valid thing to do.

I can't remember exactly which plugins you'll need to look at, but work your way through all the plugins on the "manage add ons" page. You'll mostly need to be looking at "system" plugins, and when you find ones that say "reporting", you should find each report is listed as a module, which you can disable.

Do this one at a time, and don't turn off the entire add-on - just the modules.

Yeah, I saw most of these inder the reports plugin. But it says the following:

"These add-ons are integral parts of your JIRA system. They cannot be uninstalled. Disabling or removing them will have serious effects, and could make JIRA inoperable. Only make changes here if instructed by Atlassian Support."

Yes, that is a generalised warning because it's a minefield to know which ones might be dangerous to disable.

However, as long as you are ONLY looking at reports, AND you only shutdown modules rather than whole plugins, (and no shared modules! Just the report modules) then you should be fine.

Don't know if it makes a difference but I probably should have led off with I am using on demand, I am not hosting it.

It does not look like I have sysadmin rights, so I assume this was the reason why.

So I am not sure if I should have sysadmin rights, or if this is not possible for me to do.

Oh, right, well I'm afraid you're stuck then. You can't mess with plugins in OnDemand.

0 vote

There is no ability to restrict access.

The reports will not leak information about any issues that the user cannot see though, so there's no real need to restrict them.

The reason is not security related. The issues in the system were initially created by and for developers from emails just to track for personal use. So the dates created, resolved etc. are not accurate.

Now it is being rolled out to be used as an actual ticket system. We want to leave the history, but most of these reports will be inaccurate. The users do not need the reports even if the data was accurate. And rather than have to explain this to every new user it would be best if this feature could be disabled or restricted.

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,314 views 14 20
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