Hi @Brian and all,

We are developing solution to check visibility (share/edit rights) and correctness of all filter JQLs.
If you would like to learn more just reach out to us appforge.ai and try Doctor Pro For Jira.

Best,
Hubert

Hello! It seems that this is now possible using the experimental parameter overrideSharePermissions=True on the search for filters REST endpoint.

On the suggestion of a colleague, I have reopened this ticket as the options I previously provided only return filters to which the user has access. Apologies for any confusion caused by the previous closure!

+1

As per this comment could the watchers of this issue let me know if they feel the requirements of this feature request have been met?

If so I believe this ticket can be closed, but I will wait a week before doing so in case anyone thinks it should be kept open. Thanks!

+1 please ..

Posible duplicates JRA-38599, JRA-37968, JRA-35518

+1

We'd like to perform a regular, specific security audit of our filters– something that would likely benefit many organizations that use JIRA. If an internal user inadvertently creates a filter with 'Shared with everyone' permissions, this could expose sensitive information simply by revealing the filter title (and the owner name), regardless of the permissions of the issues resulting from the filter.

We would like to be able to query for all filters in our instance, and have the response include, at a minimum, the permission and owner for each. This would allow us to create a job that would constantly check for new shared-with-everyone filters created by internal users, and notify our team and/or the owner. We could then easily verify whether the public permissions were intentional. We've found that in practice users often set this accidentally, possibly because of a misunderstanding of the scope of sharing with 'everyone.'

Without the feature requested in this ticket, automating our relatively simple auditing task is much more difficult than it should be.

+10 to this issue, our installation of JIRA has so many users and is so large that our IT group does not allow us to extend JIRA using plugins. Instead we are forced to extend JIRA using the rest API. An api that allows us to see all filters which are visible to the user would allow us to create better desktop applications that can be used by the associates to generate the individual, department, and even organization reports which JIRA is not capable of generating.

This needs to be fixed! We use filters to generate reports using the timesheet gadget, and the lack of functionality here means that I have to make filters that I'll never call manually a favourite just so we can link them to the gadget. Ref: https://bitbucket.org/azhdanov/timereports/issues/775/filters-selectable-only-if-favorited.

Similar to Kyle Cordes comment: I am writing an application that lists the summaries of issues in filters. Right now, to configure a new list of issues in my application, you need to log in to JIRA, browse to the filter, and copy+paste the filter id from the url into my configuration form. Instead, I would like a select field in my form with filter names, and I'll keep track of the ids behind the scenes. Unless it becomes possible to retrieve a list of saved filters with the REST api, I may have to guess and check for filters: I know the starting number of custom filters, try to retrieve it. If it is accessible, add it to my list of filters and increment the filter id. Repeat until I get some number of not found filter ids in a row (my best guess that I've reached the end of the list of filters). With that approach, I could probably make my own list of all filters with the current API.... please don't make me do that.

This seems like a very strange omission, when you can GET /rest/api/2/dashboard to return a list of dashboards, but not GET /rest/api/2/filter to return a list of filters.

Please add

This feature improvement would make it more possible to build third-party add-ons with greater integration, like the Atlassian-provided add-ons. For example, I can use JIRA Agile, formerly "greenhopper" to create agile boards. When I do so, I can pick from any saved filter. But if I want to build my own add-on to create my own way of viewing data (a more complex kind of data visualization, very vaguely similar to a "board"), I can only offer the user a list of their favorite filters, not all of their saved filters. Reading the tea leaves, and I think listening to some official statements, Atlassian would like external developers to make add-on products that feel as native and Atlassian-like as possible. Fixing this missing API would improve that situation (slightly).

Need to be able to retrieve the list of all filters.

6.3.6 API does not return all filters for filter/favourite, nor even all "my" filters for filter/favourite. Changing the favorite flag (via Web UI) does cause them to be returned.

Please implement 'my', 'all', and 'search' for filters so that we can properly maintain and perform bulk operations on our filters.

Here's another case: a custom filter needs to be renamed

We have some big projects, with about 30 dashboards. Each dashboard displays results from aprox 10 filters, so we have about 300 filters.
Lets imagine a case, that a issue type (which is mentioned in about 90% of the filters) has to be renamed...

Being able to search and look up filters by name and by user via the rest api would be very useful to maintain uptodate filters. big vote for me.

Today I have to write code that keeps the id's for the filter around to do updates. very tedious.

@Mauricio Leyzaola
For me it only returns the favourite filters.
Is there any API method or JQL query to get all the filters in the system?

/rest/api/latest/filter/favourite gets all the filters for the current user, doesn't matter if they are favourites or not.

This works for me.

Jason, does saved filters differ from favorite filters??? Here is what the doc says:

getSavedFilters(java.lang.String token) Deprecated. since v3.13. Please use getFavouriteFilters(String)

My testing indicates they return the same info.

We are trying to migrate from the JIRA SOAP API over to the JIRA REST API. With the SOAP API, we relied on the getSavedFilters call to get all saved filters for a user. This call is no longer possible with the REST API, so we are now stuck from being able to completely migrate over to REST. I've added my vote for this feature request, but please let me know if there is anything else I can do to raise the priority of this request.

Hi intersol,

Thanks for letting us know about this. I have moved this to a feature request is it's not really in any existing endpoint in the API.

Regards,

Oswaldo Hernández.
JIRA Bugmaster.
[Atlassian].