• 41
    • 3
    • 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.

      This bug/feature prevents us from properly maintaining JIRA instances.

      This is needed in order to be able to query existing fields and to find out which one of them is broken.

      On any big JIRA deployment administrators need to be able to detect and fix broken JQL filters, any change made to the custom fields can break them and you need to be able to detect the affected ones.

      By providing this functionality you would allow people to implement this maintenance scripts.

      Currently admins are able to browse the filters in the UI, but that kind of maintenance does not allow them to test and doesn't scale for more than very-small jira instances.

            [JRASERVER-36045] Allow retrieval of all saved filters using REST api

            Hubert Kut added a comment -

            Hi,

            We're currently developing a new tool at AppForge.ai that checks the visibility (share/edit rights) and ensures the accuracy of all filter JQLs in Jira. If you're interested in learning more about it or want to see how Doctor Pro For Jira can help streamline your work, just reach out or swing by our site.

            Cheers, Hubert

            Hubert Kut added a comment - Hi, We're currently developing a new tool at AppForge.ai that checks the visibility (share/edit rights) and ensures the accuracy of all filter JQLs in Jira. If you're interested in learning more about it or want to see how Doctor Pro For Jira can help streamline your work, just reach out or swing by our site. Cheers, Hubert

            Phillip.Ponzer added a comment - Power Scripts for Jira has this functionality: https://appfire.atlassian.net/wiki/spaces/PSJ/pages/15489492/admGetAllFilters

            Amazing that such basic functionality is not available in either the cloud or server version of Jira.  Please add this support to both versions of Jira ASAP!

            Donald P Bouchard added a comment - Amazing that such basic functionality is not available in either the cloud or server version of Jira.  Please add this support to both versions of Jira ASAP!

            Would greatly appreciate if this were to be added.

            Roomet Sütt added a comment - Would greatly appreciate if this were to be added.

            This is basic why would you not allow this!

            Tony Camacho added a comment - This is basic why would you not allow this!

            Guys, are you joking? We have the 2022 and we all like to script our infrastructure. So please, allow us to script also the removal or simply the listing of our filters.

            Oliver B. Fischer added a comment - Guys, are you joking? We have the 2022 and we all like to script our infrastructure. So please, allow us to script also the removal or simply the listing of our filters.

            We need this!

            Melvin Mathew added a comment - We need this!

            Ho

            Melvin Mathew added a comment - Ho

            Andreas Krupp added a comment - - edited

            Dear Atlassian Team,

            I am sorry, but I was just shocked reading that this is not possible via REST API. Filters are by far the most volatile objects in Jira - and for large enterprise customers managing accross validated DEV, TST, PRD Environment permissions properly is crucial. And really, building this REST Endpoint is for you most likely not more than 4 hours of work - but it would make a great difference in manageability.

            Use Case: How can I exchange after a system-clone permissions in 200+ Filters? Currently only by hand! What a waste of time.

            Hope you can reconsider adding this basic functionality.

            Best & thx,

            Andreas

            Andreas Krupp added a comment - - edited Dear Atlassian Team, I am sorry, but I was just shocked reading that this is not possible via REST API. Filters are by far the most volatile objects in Jira - and for large enterprise customers managing accross validated DEV, TST, PRD Environment permissions properly is crucial. And really, building this REST Endpoint is for you most likely not more than 4 hours of work - but it would make a great difference in manageability. Use Case: How can I exchange after a system-clone permissions in 200+ Filters? Currently only by hand! What a waste of time. Hope you can reconsider adding this basic functionality. Best & thx, Andreas

            Yassin added a comment -

            Hey there, 

            Try out the "My Filter Manager for Jira" App. It lists all filters and their owner. You can quickly identify which filters belong to inactive users. If you have feature suggestion just contact us (https://flowzess.atlassian.net/servicedesk/customer/portal/4)

             

            https://marketplace.atlassian.com/apps/1224201/my-filter-manager-for-jira?hosting=server&tab=overview

             

            Yassin added a comment - Hey there,  Try out the "My Filter Manager for Jira" App. It lists all filters and their owner. You can quickly identify which filters belong to inactive users. If you have feature suggestion just contact us ( https://flowzess.atlassian.net/servicedesk/customer/portal/4)   https://marketplace.atlassian.com/apps/1224201/my-filter-manager-for-jira?hosting=server&tab=overview  

              Unassigned Unassigned
              73f0b2e75f82 Sorin Sbarnea (Citrix)
              Votes:
              282 Vote for this issue
              Watchers:
              134 Start watching this issue

                Created:
                Updated: