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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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."
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Oh, right, well I'm afraid you're stuck then. You can't mess with plugins in OnDemand.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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.
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.