-
Suggestion
-
Resolution: Unresolved
-
27
-
12
-
Update 8 March 2024
This is now possible using the experimental parameter overrideSharePermissions=True on the search for filters REST endpoint. As the param is still experimental, we will keep this ticket open.
Original subscription
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.
Note
As a site admin, I can access private filters owned by other users in the UI (by going to https://<site name>.atlassian.net/secure/admin/filters/ViewSharedFilters.jspa) and update them so that I become the owner:
- duplicates
-
JRASERVER-35518 As an Atlassian Connect developer, I would like to query all the filters through the REST API
- Closed
- is duplicated by
-
JRACLOUD-38599 Provide access to public filter through REST API
- Closed
- is related to
-
JRACLOUD-36046 Provide REST API for running SQL queries directly on the database
- Closed
-
JRACLOUD-82149 [Tracking in Issue Links] support contact regarding private filters
- Closed
-
JRASERVER-36045 Allow retrieval of all saved filters using REST api
- Gathering Interest
- relates to
-
JRACLOUD-35518 As an Atlassian Connect developer, I would like to query all the filters through the REST API
- Closed
-
JRACLOUD-37968 Allow to access visible filters throught REST API
- Closed
-
JRACLOUD-38599 Provide access to public filter through REST API
- Closed
-
JRACLOUD-30382 Ability to export and import Filters individually / group
- Gathering Interest