Uploaded image for project: 'Jira Data Center'
  1. Jira Data Center
  2. JRASERVER-41269

Allow administrators to manage private filters, subscriptions and dashboards owned by other users

    • 1,683
    • 75
    • Hide
      Atlassian Update – 1 July 2020

      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.

      • To view filters, go to Administration > System > Filters.
      • To view dashboards, go to Administration > System > Dashboards.

      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

      Show
      Atlassian Update – 1 July 2020 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. To view filters, go to Administration > System > Filters . To view dashboards, go to Administration > System > Dashboards . 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
    • We collect Jira feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      NOTE: This suggestion is for JIRA Server. Using JIRA Cloud? See the corresponding suggestion.

      Currently JIRA administrators can only manage SHARED filters and dashboards owned by other users. There's a suggestion that they should be made capable of managing PRIVATE filters and dashboards as well.

      This ticket can be considered a continuation of JRA-9997.

            [JRASERVER-41269] Allow administrators to manage private filters, subscriptions and dashboards owned by other users

            Hey marianne.lee, could you please contact our Support Engineers about this? They'll be more than happy to help.

            From the looks of it, something went wrong during the Jira upgrade. Or, if you are using Jira DC and zero downtime upgrade, maybe database upgrade tasks didn't run yet. Anyhow - those are only my guesses and our Support will be able to give you more guidance.

            Daniel Rauf added a comment - Hey marianne.lee , could you please contact our Support Engineers about this? They'll be more than happy to help. From the looks of it, something went wrong during the Jira upgrade. Or, if you are using Jira DC and zero downtime upgrade, maybe database upgrade tasks didn't run yet. Anyhow - those are only my guesses and our Support will be able to give you more guidance.

            I recently upgraded the Jira server from 8.5.3 to 8.15.0 using .tar.gz archive method. Administration > System > Filters still show "Shared Filters" in the page title, and private filters are not found in the search results.  The same applies to Administration > System > Dashboards.  I have the Jira administration rights.

            Am I missing out something?

            Marianne Lee (Nagarro) added a comment - I recently upgraded the Jira server from 8.5.3 to 8.15.0 using .tar.gz archive method. Administration > System > Filters still show "Shared Filters" in the page title, and private filters are not found in the search results.  The same applies to Administration > System > Dashboards.  I have the Jira administration rights. Am I missing out something?

            If you want to delete all your filters, you can do something like this:

             ```
            curl 'https://example.atlassian.net/rest/api/2/filter' -s -u "$EMAIL:$APITOKEN" | jq '.self' > urls.txt
            cat urls.txt | xargs -L 1 curl -X DELETE -u "$EMAIL:$APITOKEN"
            ```

            John Boxall added a comment - If you want to delete all your filters, you can do something like this:  ``` curl 'https://example.atlassian.net/rest/api/2/filter' -s -u "$EMAIL:$APITOKEN" | jq '.self' > urls.txt cat urls.txt | xargs -L 1 curl -X DELETE -u "$EMAIL:$APITOKEN" ```

            Thanks Daniel.- will re-review in EAP2

            As a note, further testing on EAP1 showed:

            Re: Changing non-shared dashboard owners - turns out you can change the owner, but - only to a sysadmin user, which means the workflow is:

            1. Find the dashboard
            1. Change to sysadmin (yourself)
            1. Share the dashboard
            1. Change the dashboard owner to the user you wanted to originally

            Ideally, steps 3 and 4 can be removed from this process

             

            Craig Castle-Mead added a comment - Thanks Daniel.- will re-review in EAP2 As a note, further testing on EAP1 showed: Re: Changing non-shared dashboard owners - turns out you can change the owner, but - only to a sysadmin user, which means the workflow is: Find the dashboard Change to sysadmin (yourself) Share the dashboard Change the dashboard owner to the user you wanted to originally Ideally, steps 3 and 4 can be removed from this process  

            Hey craig.castlemead1, thank you for the thorough testing!

            It's a bug in the previous EAP, which also contains a few missed edge case scenarios (e.g. an admin is unable to modify gadgets on dashboards that are shared with groups/roles they don't belong to).

            It will be fixed in 8.11.0-EAP02 and 8.11.0. I actually thought the second EAP would have been published when I was adding my comment, but it turns out it got a little delayed. Sorry about that!

            Cheers,
            Daniel

            Daniel Rauf added a comment - Hey craig.castlemead1 , thank you for the thorough testing! It's a bug in the previous EAP, which also contains a few missed edge case scenarios (e.g. an admin is unable to modify gadgets on dashboards that are shared with groups/roles they don't belong to). It will be fixed in 8.11.0-EAP02 and 8.11.0. I actually thought the second EAP would have been published when I was adding my comment, but it turns out it got a little delayed. Sorry about that! Cheers, Daniel

            Daniel added a comment -

            Does this mean customers can reasonably expect a fix for https://jira.atlassian.com/browse/JRACLOUD-41269 in the near-term future as well? 

            Daniel added a comment - Does this mean customers can reasonably expect a fix for  https://jira.atlassian.com/browse/JRACLOUD-41269  in the near-term future as well? 

            Testing 8.11.0 EAP and findings below:

             

            Private Dashboards/Filters - show in the UI, but then when you try and change the owner of a private Dashboard not shared with anyone, it says you can’t change the owner of an unshared dashboard.

            Why would we want to do this?

            1. User X sets up a dashboard with great reporting
            1. Doesn’t share it
            1. Leaves
            1. The business has been relying on reports/metrics from said dashboard that User X was providing
            1. We want to make the Dashboard public, and managed by a current staff member

            The above does not align with the statement "With this feature, admins should get full control over obsolete and incorrect filters and dashboards, and can help their users set things right."

             

            CCM

            Craig Castle-Mead added a comment - Testing 8.11.0 EAP and findings below:   Private Dashboards/Filters - show in the UI, but then when you try and change the owner of a private Dashboard not shared with anyone, it says you can’t change the owner of an unshared dashboard. Why would we want to do this? User X sets up a dashboard with great reporting Doesn’t share it Leaves The business has been relying on reports/metrics from said dashboard that User X was providing We want to make the Dashboard public, and managed by a current staff member The above does not align with the statement "With this feature, admins should get full control over obsolete and incorrect filters and dashboards, and can help their users set things right."   CCM

            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.

            • To view filters, go to Administration > System > Filters.
            • To view dashboards, go to Administration > System > Dashboards.

            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

            Daniel Rauf added a comment - 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. To view filters, go to Administration > System > Filters . To view dashboards, go to Administration > System > Dashboards . 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

            Omid H. added a comment -

            +1

            Omid H. added a comment - +1

            Looking forward to see this function in production. This function is very important for all of us.

            Peter Illig added a comment - Looking forward to see this function in production. This function is very important for all of us.

            Exciting! 

            Anette Lara added a comment - Exciting! 

            yay, thank you Atlassian, hope the implementation goes smooth and trouble free.

            Craig Solinski added a comment - yay, thank you Atlassian, hope the implementation goes smooth and trouble free.

            Finally....the issue moved to "In progress" ........5.5. years after it was created.

            And now we wait.....again

            Marcel Plomp added a comment - Finally....the issue moved to "In progress" ........5.5. years after it was created. And now we wait.....again

            Given the huge layoffs that your Atlassian customers have experienced due to the virus, its critical this feature be implemented sooner. Filter Owners and Dashboard Owners have been laid off gone and Tool Admins have to deal with this situation in high numbers. 

            Karen Rogalski added a comment - Given the huge layoffs that your Atlassian customers have experienced due to the virus, its critical this feature be implemented sooner. Filter Owners and Dashboard Owners have been laid off gone and Tool Admins have to deal with this situation in high numbers. 

            I voted for issue because of the similar reasons mentioned by my colleagues. As an admin at https://www.kidsatvsale.com/ I can't check private filters properly. It takes forever to manage them.  

            MattJohnson added a comment - I voted for issue because of the similar reasons mentioned by my colleagues. As an admin at https://www.kidsatvsale.com/ I can't check private filters properly. It takes forever to manage them.  

            I also strongly vote for this feature to be implemented. My case was as follows:

            The project lead exchanged the filter of a board to a new one. The filter was not shared at all. Result: I couldn't find the filter in the filter search and also got a "Board doesn't exist or no sufficent rights to access it" error when trying to open the board. Which I thought was very unsual as an admin.

            Only by looking into the database tables and audit log and using scriptrunners "switch to other user" I was able to reconstruct what happend.

            As an admin I should be able to see private filters, then it would've cost a minute to track it down instead of an hour.

            Manuel Bähnisch added a comment - I also strongly vote for this feature to be implemented. My case was as follows: The project lead exchanged the filter of a board to a new one. The filter was not shared at all. Result: I couldn't find the filter in the filter search and also got a "Board doesn't exist or no sufficent rights to access it" error when trying to open the board. Which I thought was very unsual as an admin. Only by looking into the database tables and audit log and using scriptrunners "switch to other user" I was able to reconstruct what happend. As an admin I should be able to see private filters, then it would've cost a minute to track it down instead of an hour.

            Atlassian Update – 5 March 2020

            Hi everyone,

            In the last update, we shared that we’ll prioritize this suggestion for our longer-term roadmap.

            After reviewing comments on this suggestion and getting context from the support cases, we have decided to provide an MVP solution. It will let you search through all filters and dashboards (including the private ones) and change their owners. It will also help us validate the longer-term approach to this feature. Please note that this procedure is not part of the Jira’s intended functionality, and the information is provided as-is.

            In Jira Server 8.8, you can enable the dark feature that lets you edit private filters and dashboards:

            1. Enable the dark feature flag com.atlassian.jira.privateEntitiesEditable.enabled by following these instructions.
            2. Go to the ‘Filters‘ or ‘Dashboards‘ administration screen.
            3. Click the cog next to an entity and select the ‘Change Owner‘ link.
            4. After you perform the update, the new owner will be able to edit the entity or share edit rights with others.

            In the roadmapped project, we would like to allow admins to immediately edit private filters and dashboards, removing the intermediate step of changing their owner, improve the filtering abilities on the ‘Filters’ and ‘Dashboards’ screens and enable searching and modifying mail subscriptions.

            Please share your feedback on this solution so that we can make better decisions when solving the underlying problem. You can leave a comment here or reach out to me directly at kderenda(at)atlassian.com.

            You can download the 8.8 EAP version here.

            Preparing for Jira 8.8 will give you an overview of the changes we intend to make in Jira 8.8.

            Katarzyna Derenda
            Product Manager, Jira Server and Data Center

            Kasia Derenda added a comment - Atlassian Update – 5 March 2020 Hi everyone, In the last update, we shared that we’ll prioritize this suggestion for our longer-term roadmap. After reviewing comments on this suggestion and getting context from the support cases, we have decided to provide an MVP solution. It will let you search through all filters and dashboards (including the private ones) and change their owners. It will also help us validate the longer-term approach to this feature. Please note that this procedure is not part of the Jira’s intended functionality, and the information is provided as-is. In Jira Server 8.8, you can enable the dark feature that lets you edit private filters and dashboards: Enable the dark feature flag com.atlassian.jira.privateEntitiesEditable.enabled by following these instructions . Go to the ‘Filters‘ or ‘Dashboards‘ administration screen. Click the cog next to an entity and select the ‘Change Owner‘ link. After you perform the update, the new owner will be able to edit the entity or share edit rights with others. In the roadmapped project, we would like to allow admins to immediately edit private filters and dashboards, removing the intermediate step of changing their owner, improve the filtering abilities on the ‘Filters’ and ‘Dashboards’ screens and enable searching and modifying mail subscriptions. Please share your feedback on this solution so that we can make better decisions when solving the underlying problem. You can leave a comment here or reach out to me directly at kderenda(at) atlassian.com . You can download the 8.8 EAP version here. Preparing for Jira 8.8 will give you an overview of the changes we intend to make in Jira 8.8. Katarzyna Derenda Product Manager, Jira Server and Data Center

            yes, please!

            we have so many people who left the company and left behind many dashboards and filters - 1000s of them.

            as admin, i should not login as each one of these users (also need to enable them to be able to log as them which is a security concern) just to delete an unused filter/dashboard.

            my team is trying now to alter the DB but that can cause different issues.....

            we created a cleanup user and tried to assign all private filters and dashboard to tat user so we can access as this user and delete all the unused filters/dashboard - so far unsuccessfully... if anyone has tried something like that before and willing to share the queries that will be awesome

            Ronen Erlich added a comment - yes, please! we have so many people who left the company and left behind many dashboards and filters - 1000s of them. as admin, i should not login as each one of these users (also need to enable them to be able to log as them which is a security concern) just to delete an unused filter/dashboard. my team is trying now to alter the DB but that can cause different issues..... we created a cleanup user and tried to assign all private filters and dashboard to tat user so we can access as this user and delete all the unused filters/dashboard - so far unsuccessfully... if anyone has tried something like that before and willing to share the queries that will be awesome

            Kevin Mowrey added a comment - - edited

            Please implement. Every deployment, I get false red flags in the integrity checker, because we've got private filters belonging to a deleted user that cannot be managed. I'm worried about missing actual important integrity errors because it is cluttered with false red flags.

             

            I did find a work-around for us (since we use Active Directory) - I was able to create a new user with the same username in AD and somewhat surprisingly to me, when I logged in as that user, I was able to manage all of the other user's filters and either delete them or make them shared filters (for future deleting/re-assignment)

            Kevin Mowrey added a comment - - edited Please implement. Every deployment, I get false red flags in the integrity checker, because we've got private filters belonging to a deleted user that cannot be managed. I'm worried about missing actual important integrity errors because it is cluttered with false red flags.   I did find a work-around for us (since we use Active Directory) - I was able to create a new user with the same username in AD and somewhat surprisingly to me, when I logged in as that user, I was able to manage all of the other user's filters and either delete them or make them shared filters (for future deleting/re-assignment)

            This should be prioritized as old private filters/boards/dashboards are a problem when migrating projects from one Atlassian instance to another plz fix so best practice no longer is the use of third party software. 

            Deleted Account (Inactive) added a comment - This should be prioritized as old private filters/boards/dashboards are a problem when migrating projects from one Atlassian instance to another plz fix so best practice no longer is the use of third party software. 

            I as Admin want to have the option on the admin-GUI to filter for private filters + inactive users and one click delete button.

            M. (no PREM!) added a comment - I as Admin want to have the option on the admin-GUI to filter for private filters + inactive users and one click delete button.

            We use Microsoft AD with CAS WITH TWO FACTOR login that prevents any impersonation solution offered by 3rd party vendors (all that I'm aware of anyway).

            Here at this huge university we have thousands of users (Student and staff) that come and go yearly. We migrate unused projects off the system resulting in thousands of Private entities that point to a NULL pointer.
            Please fix this software so admins can properly admin the data.

            Craig Solinski added a comment - We use Microsoft AD with CAS WITH TWO FACTOR login that prevents any impersonation solution offered by 3rd party vendors (all that I'm aware of anyway). Here at this huge university we have thousands of users (Student and staff) that come and go yearly. We migrate unused projects off the system resulting in thousands of Private entities that point to a NULL pointer. Please fix this software so admins can properly admin the data.

            I highly recommend having the jira systems administrators have the ability to alter private filters, subscriptions, and dashboards. Looking forward to getting this feature.

            Reneesh Kottakkalathil added a comment - I highly recommend having the jira systems administrators have the ability to alter private filters, subscriptions, and dashboards. Looking forward to getting this feature.

            our company also has problems due to this missing feature ...

            after all what could be so secret in a filter syntax that the admin can not see it 

            Bojan Shkordovski added a comment - our company also has problems due to this missing feature ... after all what could be so secret in a filter syntax that the admin can not see it 

            We've got a Jira installation with 300 Projects and 4.100 users. There are thousands of filters and hidden dashboards on our environment and I as admin am not able to see them.

            We had large performance issues recently as a (private) board used a filter to display 17.000 issues at once. The server performance was killed and for us it was super difficult to find the issue as we can not see these creepy filters and boards. Therefore Atlassian, please improve your product and work on that topic. Thanks a lot!!!

            Peter Illig added a comment - We've got a Jira installation with 300 Projects and 4.100 users. There are thousands of filters and hidden dashboards on our environment and I as admin am not able to see them. We had large performance issues recently as a (private) board used a filter to display 17.000 issues at once. The server performance was killed and for us it was super difficult to find the issue as we can not see these creepy filters and boards. Therefore Atlassian, please improve your product and work on that topic. Thanks a lot!!!

            Please act on this issue.

            Scott Raigner added a comment - Please act on this issue.

            April added a comment -

            I cannot agree more that a system admin should be able to see and manage ALL objects, else what is the point of being an admin?

            NOTE: when I say see and manage, I do NOT mean via SQL hacking; I mean the GUI interface.

            And Jason's remark that that old data should be deleted is spot on! Old searches that refer to deleted objects such as components can cause problems, especially when the user created a subscription or set a gadget to autorefresh.

            The support model for Jira has just got to adapt to the concept that basic system hygiene cannot rely on server and DB access.... Customers ought to be able to accomplish these truly basic management tasks using the admin interface.

            April added a comment - I cannot agree more that a system admin should be able to see and manage ALL objects , else what is the point of being an admin? NOTE: when I say see and manage, I do NOT mean via SQL hacking; I mean the GUI interface. And Jason's remark that that old data should be deleted is spot on! Old searches that refer to deleted objects such as components can cause problems, especially when the user created a subscription or set a gadget to autorefresh. The support model for Jira has just got to adapt to the concept that basic system hygiene cannot rely on server and DB access.... Customers ought to be able to accomplish these truly basic management tasks using the admin interface.

            I could not agree more. Please pay attention to this, Atlassian!

            Mark Johnson added a comment - I could not agree more. Please pay attention to this, Atlassian!

            Jason M. added a comment - - edited

            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. 

            Jason M. added a comment - - edited 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. 

            Rich Hale added a comment -

            Jira CLOUD Also needs this.   Critical to keep Jira cleaned up.

            Rich Hale added a comment - Jira CLOUD Also needs this.   Critical to keep Jira cleaned up.

            The Jira admin should be able to manage all kind of filters not only the shared.

            Darío Díez added a comment - The Jira admin should be able to manage all kind of filters not only the shared.

            Thanks Matt & Sten for sharing your advice.

            Marianne Lee (Nagarro) added a comment - Thanks Matt & Sten for sharing your advice.

            It's true that the Shared Filters page won't auto-populate the user field with inactive user names (on 7.6.10, which I'm running), but if you simply fill in the field by hand you can access the filters just fine.

            Sten Sundelin added a comment - It's true that the Shared Filters page won't auto-populate the user field with inactive user names (on 7.6.10, which I'm running), but if you simply fill in the field by hand you can access the filters just fine.

            Matt Doar added a comment -

            Marianne, you are correct. But all those old private filters and dashboards don't seem to have affected us after 15 years and 10,000 users. So I'll clean them up if and when I have to.

            Something more questionable is how all the custom fields' data is not cleaned up from the database table customfieldvalue even after you remove the plugin that created it. We have 100 million rows in that table now

            Matt Doar added a comment - Marianne, you are correct. But all those old private filters and dashboards don't seem to have affected us after 15 years and 10,000 users. So I'll clean them up if and when I have to. Something more questionable is how all the custom fields' data is not cleaned up from the database table customfieldvalue even after you remove the plugin that created it. We have 100 million rows in that table now

            While the new feature «Share edit rights for filters and dashboards» has been released in Jira 7.12.3, I hope that Atlassian will enhance this to include private filters and boards of inactive users. To allow change of owners as well as deletion, in selective & bulk mode.

            Our list of inactive users and their private filters & boards are growing.

            Marianne Lee (Nagarro) added a comment - While the new feature «Share edit rights for filters and dashboards» has been released in Jira 7.12.3, I hope that Atlassian will enhance this to include private filters and boards of inactive users. To allow change of owners as well as deletion, in selective & bulk mode. Our list of inactive users and their private filters & boards are growing.

            Hi Greg, Matt, If the private filters and boards belonging to inactive users are inaccesible by admins, does that mean that they can be left & ignored in the system? Won’t there be a growing list? Will it affect system performance or configuration integrity?

            Marianne Lee (Nagarro) added a comment - Hi Greg, Matt, If the private filters and boards belonging to inactive users are inaccesible by admins, does that mean that they can be left & ignored in the system? Won’t there be a growing list? Will it affect system performance or configuration integrity?

            April added a comment -

            I think this will work: https://marketplace.atlassian.com/apps/1216249/sharedmanager

            And I think you'll like the price

            April added a comment - I think this will work: https://marketplace.atlassian.com/apps/1216249/sharedmanager And I think you'll like the price

            Yeah, just tested and confirmed that you cannot log in as users who are inactive, their name doesn't auto-populate into the list of users. Not surprising. But the workaround for that is to get their account re-activated temporarily.

            Greg Hoggarth added a comment - Yeah, just tested and confirmed that you cannot log in as users who are inactive, their name doesn't auto-populate into the list of users. Not surprising. But the workaround for that is to get their account re-activated temporarily.

            Matt Doar added a comment -

            I'm not sure you can log in using the ScriptRunner built-in script when the user is inactive. I generally reason that if the filter wasn't worth sharing, then nobody but the inactive user cared about it. If boards and filters were used by other people than the inactive user, then you will be able to change them as Greg said

            Matt Doar added a comment - I'm not sure you can log in using the ScriptRunner built-in script when the user is inactive. I generally reason that if the filter wasn't worth sharing, then nobody but the inactive user cared about it. If boards and filters were used by other people than the inactive user, then you will be able to change them as Greg said

            Ah yes, it is explicitly "Shared filters" that you can access.

            If you have script runner, it is possible to log-in as any other user temporarily, so you could log-in as the defunct user, make the filters globally shared, and then via admin you can change ownership to yourself etc.

            Scriptrunner however is no longer free, so this workaround may not be an option for you.

            Greg Hoggarth added a comment - Ah yes, it is explicitly "Shared filters" that you can access. If you have script runner, it is possible to log-in as any other user temporarily, so you could log-in as the defunct user, make the filters globally shared, and then via admin you can change ownership to yourself etc. Scriptrunner however is no longer free, so this workaround may not be an option for you.

            Greg - I cannot see how to do this with private filters of inactive users, even as admin.

            Mark Johnson added a comment - Greg - I cannot see how to do this with private filters of inactive users, even as admin.

            Admins can change the ownership of filters to themselves and then edit from there.

            Greg Hoggarth added a comment - Admins can change the ownership of filters to themselves and then edit from there.

            Mark Johnson added a comment - - edited

            +1 - We are using LDAP sync, so users who leave the company are made inactive.
            I am then not able to switch to their account to share or remove private filters.
            Especially frustrating when people who need to step into the departed person's role cannot use the filters/boards.

            Mark Johnson added a comment - - edited +1 - We are using LDAP sync, so users who leave the company are made inactive. I am then not able to switch to their account to share or remove private filters. Especially frustrating when people who need to step into the departed person's role cannot use the filters/boards.

            Just going to +1 on the other comments here –

            Yes, I can head to https://CUSTOMER.atlassian.net/secure/admin/ViewUserDefaultSettings.jspa as an admin user and change the default.

            This stops the problem from becoming worse (eg. no new public filters will be created accidentally) – but doesn't solve the problem I have (many filters that should not be public are, and there is no way to remove them short of getting the owner of each of the filters to login and delete their filters via https://CUSTOMER.atlassian.net/secure/ManageFilters.jspa)

            To step back a bit – what I'd really like is a simple way to prevent non-logged in users from accessing any Jira page – https://CUSTOMER.atlassian.net/secure/admin/ViewUserDefaultSettings.jspa being just one example.

            John Boxall added a comment - Just going to +1 on the other comments here – Yes, I can head to https://CUSTOMER.atlassian.net/secure/admin/ViewUserDefaultSettings.jspa  as an admin user and change the default. This stops the problem from becoming worse (eg. no new public filters will be created accidentally) – but doesn't solve the problem I have (many filters that should not be public are, and there is no way to remove them short of getting the owner of each of the filters to login and delete their filters via https://CUSTOMER.atlassian.net/secure/ManageFilters.jspa ) To step back a bit – what I'd really like is a simple way to prevent non-logged in users from accessing any Jira page –  https://CUSTOMER.atlassian.net/secure/admin/ViewUserDefaultSettings.jspa  being just one example.

            April added a comment -

            To change all existing filters, I don't know of any bulk interface.

            In our instance, I did this:

            1. I went to our.jira.net/secure/admin/ViewUserDefaultSettings.jspa and changed the default there to Private
            2. I audited the filter shares in SQL to determine which needed to change
            3. I have ScriptRunner, so I can use the built-in script to impersonate users as needed to change filter shares (it does have a bulk change for owner)

            Without ScriptRunner, I don't think this can be managed in Jira. You'd have to try some sort of SQL hack, which probably isn't a good idea.

            Perhaps you can get a trial of ScriptRunner?

            April added a comment - To change all existing filters, I don't know of any bulk interface. In our instance, I did this: I went to our.jira.net/secure/admin/ViewUserDefaultSettings.jspa and changed the default there to Private I audited the filter shares in SQL to determine which needed to change I have ScriptRunner, so I can use the built-in script to impersonate users as needed to change filter shares (it does have a bulk change for owner) Without ScriptRunner, I don't think this can be managed in Jira. You'd have to try some sort of SQL hack, which probably isn't a good idea. Perhaps you can get a trial of ScriptRunner?

            Hi, But still it won't solve the problem. As an admin, I want to change the privacy setting of all  filters/dashboard made by different users from public to private. What is the quick way to do this. 

            Avinash Jain added a comment - Hi, But still it won't solve the problem. As an admin, I want to change the privacy setting of all  filters/dashboard made by different users from public to private. What is the quick way to do this. 

            john248, in Jira Cloud admins can change the default for sharing filters and dashboards in User Default Settings screen. Public and private options are available.

            This suggestion is for Jira Server and in Server users can set their preferences in their profile and admins can do that per instance in User Default Settings. Admin section can be easily accessed using 'gg' keyboard shortcut.

            Katarzyna Derenda
            Product manager, Jira Server

            Kasia Derenda added a comment - john248 , in Jira Cloud admins can change the default for sharing filters and dashboards in User Default Settings screen. Public and private options are available. This suggestion is for Jira Server and in Server users can set their preferences in their profile and admins can do that per instance in User Default Settings. Admin section can be easily accessed using 'gg' keyboard shortcut. Katarzyna Derenda Product manager, Jira Server

            Hey Jira super friends,

            For reasons I do not understand, at some point, filters defaulted to sharing with the public.

            This means I can navigate to https://CUSTOMER.atlassian.net/secure/ManageFilters.jspa and see a list all filters where folks didn't bother changing the default privacy.

            This is a bummer, as I'd assume 99.9% of non-open source projects wouldn't want the names of these exposed.

            There appears to be no easy way to fix or resolve this outside of using the API... so, as an adminstrator, I tried to do it via this API:

            https://docs.atlassian.com/DAC/rest/jira/6.1.html#d2e4277

            And then wham:

            {"errorMessages":["You may only create, modify or delete filters that you own."],"errors":}

            It would be great if ... admins could edit the permissions of these so they wouldn't be exposed.

            Thanks

             

            John Boxall added a comment - Hey Jira super friends, For reasons I do not understand, at some point, filters defaulted to sharing with the public. This means I can navigate to https://CUSTOMER.atlassian.net/secure/ManageFilters.jspa  and see a list all filters where folks didn't bother changing the default privacy. This is a bummer, as I'd assume 99.9% of non-open source projects wouldn't want the names of these exposed. There appears to be no easy way to fix or resolve this outside of using the API... so, as an adminstrator, I tried to do it via this API: https://docs.atlassian.com/DAC/rest/jira/6.1.html#d2e4277 And then wham: { "errorMessages": ["You may only create, modify or delete filters that you own."] ,"errors": } It would be great if ... admins could edit the permissions of these so they wouldn't be exposed. Thanks  

            Stephan Landgraf added a comment - - edited

            Hi guys

            What's the status regarding this 'feature request'. In my eyes this really should have been implemented since long. We really really would appreciate it, if you force this request and please please please get it realized in the next month - may until end of 2018? ..  THX!!

            Stephan Landgraf added a comment - - edited Hi guys What's the status regarding this 'feature request'. In my eyes this really should have been implemented since long. We really really would appreciate it, if you force this request and please please please get it realized in the next month - may until end of 2018? ..  THX!!

            Avinash Jain added a comment - - edited

            Any date Jira team has set to get it done and push to all the users?

            Avinash Jain added a comment - - edited Any date Jira team has set to get it done and push to all the users?

            It should also be possible to edit a broken filter, i.e. one that returns a 500 error if you try to edit it even as the owner.

            Sten Sundelin added a comment - It should also be possible to edit a broken filter, i.e. one that returns a 500 error if you try to edit it even as the owner.

             As long as it's not going to be another 5+ years in the "Under Consideration" state... 

            Radford Software added a comment -  As long as it's not going to be another 5+ years in the "Under Consideration" state... 

            An old request, please proceed. This is needed. It is not a big work to implement this, why not even consider ?

            François B added a comment - An old request, please proceed. This is needed. It is not a big work to implement this, why not even consider ?

            So, no progress on this? I think it is ludicrous to not be able to delete filters for non active users. Stupid beyond words. And no I do not have script runner neither should I need to. And the worst thing .... this is an easy fix. But I assume Atlassian rather have their devs adding new feature so they can get new customers instead of servicing their old customers. 

            Lars Sundstrom added a comment - So, no progress on this? I think it is ludicrous to not be able to delete filters for non active users. Stupid beyond words. And no I do not have script runner neither should I need to. And the worst thing .... this is an easy fix. But I assume Atlassian rather have their devs adding new feature so they can get new customers instead of servicing their old customers. 

              drauf Daniel Rauf
              vdung Andy Nguyen (Inactive)
              Votes:
              744 Vote for this issue
              Watchers:
              431 Start watching this issue

                Created:
                Updated:
                Resolved: