-
Suggestion
-
Resolution: Fixed
-
None
-
2
-
2
-
NOTE: This suggestion is for JIRA Server. Using JIRA Cloud? See the corresponding suggestion.
Please allow JIRA administrators to see private filters and dashboards in the GUI.
Some use cases:
- A user created a filter, forgot to share it, sent the link by mail to some people who should use it, and ran off for holiday. Sure, the people who got the mails will complain. The adminstrator should be able to acces the filter in the GUI and to share it.
- People who leave the company do not delete their private filters and dashboards before they go. Over time, this relicts will pile up. Adminstrators should have the option to clear private filters and dashboards after a user has left.
It's not feasible to query the database to find out which private filters exist and who the owners are, and alter the database.
First, functionalities in the GUI would be more convenient to use.
Second, you cannot assume that JIRA administrators have access to the database. In our company, I have to contact central administration and ask them if they could run queries and clean up which would be completely unnecessary if I had some more options in the GUI.
Regards, Evelin
- duplicates
-
- Closed
- relates to
-
- Gathering Interest
[JRASERVER-46013] JIRA administrators should be able to see private filters and dashboards
I as Admin want to have the option on the admin-GUI to filter for private filters + inactive users. By doing so, I want to have the possibility to do a one click removal of all private filter, who fulfil this criteria.
Re: Jira Server...this also wholly interferes with the Configuration Manager add-on, which calls for running an Integrity Check prior to snapshots & deployment...the Integrity Check pulls up dozens of old private filters from Inactive users referencing removed objects, but I'm unable to remove/modify these filters from anywhere in the application.
Why would Botron's Configuration Manager and Atlassian provide/support a PAID (and expensive) add-on with a key feature that basically tells me "Hey, this is broke, but nothing you can do about it, because Jira doesn't provide any option to edit/remove these forgotten, unused & irrelevant filters because they're Private"?
It's a filter. A search query. Why does Jira persist a blanket lock-down on private search queries, especially by Inactive users? This makes no sense, and renders Botron Configuration Manager close to useless, as I can't include Filters, subscriptions or dashboard because of old, useless data that should be deleted if it's no longer managed by the original user...not worth paying for.
Hi everyone,
In Jira 8.11, we’re giving Jira admins the power to edit and delete private filters and dashboards. Admins can view and search for all existing filters and dashboards from the administration area.
These pages already existed (Shared filters/dashboards), but until now they only included filters that were shared by their owners. Now, it will also include private filters/dashboards.
After clicking the filter/dashboard name, you can navigate to it and modify it just like its owner—improve the JQL or gadgets' settings, share permissions, and more.
With this feature, admins should get full control over obsolete and incorrect filters and dashboards, and can help their users set things right.
You can download the 8.11 EAP version here.
Preparing for Jira 8.11 will give you an overview of the changes we intend to make in Jira 8.11.
Daniel Rauf
Jira Server and Data Center developer