Hey 4101b48837ca
Thanks for sharing your workaround.
To be specific, this is not an exact duplicate of JRASERVER-17783 (change of ownership vs shared ownership), but I agree with you it addressed the same need and solves the problem.

gonchik
Thanks for the notification, I will mark the current ticket is superseded by JRASERVER-17783.

Yes, it's included.
ayakovlev@atlassian.com Can we close that issue, please?
as feature from 7.12 works well

Actually, is this a dup of JRASERVER-17783 which was fixed in 7.12? Maybe the latest version already has this?

Going from JIRA 7.8.1 to 8.6.1 soon I think we will get rid of that problem.
Yes. Thanks @Ben Spiller - since JIRA 7.12 there is group ownership of a filter.

This seems like an intuitive feature since it follows the way schemes are throughout the app. Really the whole board system lacks global configuration options, when comparing to the other features in the app, like screens, fields, workflows, permissions, notifications. Why are boards and the tools they use some of the hardest things to have a universal configuration on. 

Not to distract from the issue, but this has been a feature request for 5 years, on one of the main tools this app is good for, and seems to be more than intuitive to add. I'd hope we'd see more movement on things like this, over "Jira Mobile" (Released this month) which still has tons of problems and bugs. 

It's like a person who's doing an add-on on their house when they have a termite infestation. Fix the main house first, before you go building that add on. 

Here's to another 5 years without the feature! 

Hi!
I hope that feature already delivered in 7.12.x release.
https://confluence.atlassian.com/jirasoftware/jira-software-7-12-x-release-notes-953676636.html

Because to me, it's enough to share edit rights and admins already have functionality to transfer ownership public filters and dashboards

Cheers,
Gonchik Tsymzhitov

++ on this.

Lacking this feature:

Group ownership of filters to allow more than one user to be able to modify a filter.

forces us to create dummy user accounts and share credentials. 

Security and audit suffers because of the lack of this feature. 

How many votes does it take to get some action?

Is it possible to own a filter by a user group? Ideally, it should be the same as a filesystem: read, write access handling one group and individual level.

This feature request is essential

Wow, four and a half years without any progress...

We also need this feature

This would be a great feature!

This is a problem with us trying to maintain filters for staff no longer with the company or filter owners who are not available to make edits. Allowing the owner to be an individual or a group would allow us to maintain our Jira project without going to the main Jira administrators for support when they are busy with many tasks keeping the system running.

Same problem for us. Filter owner on vacation... Try to find someone who can change the ownership.

Filters are extremely important to a number of shared, cooperative functionalities within Jira:

• Team Dashboards
• Agile Boards
• Issue sources in Portfolio for Jira

If a change needs to be made to any of these and the filter owner is unavailable, a request would have to be put in to a Jira Admin. In larger organizations, however, the Jira admin(s) would likely not have the context or bandwidth to make the changes in a timely manner. Without approval from the filter owner, the Jira admin(s) could also choose to not complete the request at all.

Due to JQL limitations, many filters need to be updated regularly to accommodate data model changes (new values added to fields, etc).

Allowing for shared (or group) ownership of filters would solve these problems. 

Same problem as others: multiple admins for an agile board but the filter is unnecessarily locked down to one.

In our workflow, multiple people can be responsible for a scrum board (say we have two people leading a meeting).  Single ownership seems to run counter to the fundamental ideas of scrum.

Single owners of dashboards is an issue for our teams. These are a great way to share information and status, but when only 1 person can update the filters and settings it bottlenecks real-time agile status and collaboration.

Please add, this would be a reallllllllly helpful feature for our enterprise.

Making a group a owner of a filter would also extremely helpful. 

Same problem as others- two admins for an agile board but the filter is unnecessarily locked down to one.

With the feature of having multiple administrators for an agile board (which is a great feature) it is strange that only one person can update the filter associated with the board. Although it is possible to create a new filter and use that instead, in the end there might be a lot of filters created with some uncertainty from the owners as to which one is actually used.

We're facing problems with this too. When a shared filter owner is absent (for whatever reason) and our project is developing into new versions, we need to change some of the shared filters, but just can't and have to make our own copy of it.

This is very impactful and creates single point of failures within a company. If someone, who is the owner of a filter, leaves the company it is very time consuming to have the new "owner" of the board to take over.

This would also be extremely helpful, we have Agile boards built on a filter, and it's hard to track down the one and only person in the company that created the filter that the board uses to make changes.

The only other alternative is to create a new filter which will result in the same issue again.

I have this exact same problem, although I'm a project admin, not a sys admin, so I find I have to "save as" a filter, make amendments, and then (in my particular case) set the scrum board to now use my filter.

Biggest pitful is that the filters are set to private by default = board disappears for everybody! I have to go into the filter's properties and rather awkwardly share with the project.