Is there an reason why only the owner of the filter can edit the filter?
From a security standpoint it adds an additional 3 steps per filter to edit in the event that an user accidentally share a filter with the Global ("Everyone") setting. An admin cannot just edit the filter to change it to a compliant share setting, without changing the owner, then find the dashboard, edit the permission, then change the owner back to the original owner. Filters are prone to being accidentally shared externally because the first share option is "Everyone" which is the Global setting. We are able to setup monitoring via unauthenticated queries against the vulnerable manage filter endpoint https://site.atlassian.net/secure/ManageFilters.jspa?filterView=search
Using the API as a proof of concept on a filter that I own it's possible to do a
GET /rest/api/2/filter/{id}/permission
If JSON.parse(response.body)[0]['type'] == 'Global'
DELETE /rest/api/2/filter/{id}/permission/JSON.parse(respones.body)[0]['id']
POST /rest/api/2/filter/{id}/permission request.body={type: 'group', groupname: 'jira-administrators'}.to_json
end
However when the owner of the filter is not an admin this does not work. I'm trying to get over 100 filters corrected on a weekly basis since the users do not understand that sharing the filter with everyone results in the filters being exposed to the world.
