Hi david.molloy,

This should be because the filter is not owned by you. You need to change the owner before you can update it. Refer to Managing shared filters for more info

We have a Board Filter owned by an Admin, set as "Shared with logged-in users". However, as an Admin, I do not have the option of updating it. "You can save a copy of this filter but you cannot modify the original."

Hi guys,

It helps you manage users subscriptions - https://marketplace.atlassian.com/plugins/ru.teamlead.jira.plugins.subscriptions-for-jira/server/overview.

@Dave (as mortals are not allowed to use username auto-completion). the new ticket is supposed to fix it. Still, I was arguing that creating a new ticket just in order to keep an old bug closed as resolved is not necessarily the best idea. If someone checks the history of the bug they will find that the original request was covering both private and shared filters, is just the fix that was incomplete. Why I see it as wrong: simply because keeping it as fixed suggests that those ~420 votes were solved, also suggesting that there are only ~40 votes for the part that was not fixed.

The bare truth is the JIRA product management ignored the administration of JIRA instance for too long, probably because this was not a very marketable feature. Instead we how have an product marketed enterprise ready that is very hard to manage and where is something normal to have to fix things directly in the database.

Should I give few additional examples?

• when you click on a user in the admin users, you get an URL with an ATL token, not a permalink. We should never see the ATL token in the URL in the first place.
• when you search a user by name, the search string is sent by POST instead of GET so the URL does not contain the query
• user searcher has 3 fields: username, fullname and email address but if you copy the email address you cannot paste it to perform a search because it would look like: "aaa bbb <aaa.bbb@company.com>" which Jira does not know how to parse (same applies for the user picker and multi-user picker).
• the use-case where people do leave, or being replaced is totally ignored and we all know that IT industry has a turnover of ~15% per year, so any jira instance over 100 users will be hit hard.
• and I would end-up with the introduction of clustered versions which are supposed to bring enterprise reliability and HA to a product that was not designed to scale. In the end the number of things fixed by the clustered version is very small, you are not still able to upgrade one node while the other one is us, which would #1 requirement for a HA solution. It's hilarious how often we do see the maintenance screens on the Atlassian sites and I would be quite reluctant on going for any up-sell for TAM deal when I keep seeing those downtimes.

@Dave - the only thing not covered is the small matter of 380 379 missing votes.

Hi intersol, is there anything that you are requesting that is not covered by JRA-41269?

Dave, I bet that 50% of the votes here not addressed by the current partial fix, the title was more than clear. We have hundreds of broken filters which we cannot address.

Hi everyone,

We understand the challenge here but this issue is not currently on the JIRA roadmap. Since this issue has already been closed for quite some time, there is another issue to track the request to manage filters owned by other users that have not been shared. Please follow JRA-41269. We will provide updates there if we are able to take on this improvement.

Thanks,
Dave Meyer
Product Manager, JIRA Platform

any updates?

+1 for Citrix Devops comment.

after a while the owner leaves the company and you end-up with a filter that cannot be edited by anyone, sometimes even becoming broken.

I think that the mistake on this ticket is of Atlassian failing to see the lifecycle of these filters and to provide a meaningful way to deal with them.

If Atlassian would just allow any filters to be edited or removed by a jira-administrators this problem would be solved for good.

Does this leave us to manipulate database itself for removing filters? Please, reopen this issue and allow jira-admins to remove obsolete filters.