ZOMG please implement this.  Had to open a PS ticket just to find out which filter a user made private and locked out the rest of their team.

I vote for this...

So is there still no way to filter for Kanban/Scrum boards by searching for a user listed as one of the board admins? It's a bit perplexing as to why this type of permission isn't granted to a Jira Administrator. 

Curious on why the search option is available for "shared filters" and "shared dashboards" within Jira's settings to filter for a owner, but not as an option when searching for (either) an owner/admin for the boards? 

Any possible workaround ideas would be greatly appreciated. Thanks.

Simply put, the model that is easiest for Atlassian or works in their mind is not how business works. The risk created by removing control of user names to over-comply for GDPR is not justified. This is apparent here, as well.

The argument that it's a better security model falls flat on its face when you consider that an admin that is responsible for ensuring that a former employee/client/vendor/contractor is removed from access company confidential information. Controlling access to company assets is a valid business reason to have identity access. Non-public boards/filters/projects should have visibility by admins for the administration part.

Atlassian, please fix the cases where admins can't control who has access to these things. To do that, admins need to be able to see and manage access. This does not mean that they need to be able to view content. This part, the filters, are one of the worst offenders of this.

Please fix

Same problem and surprised this has still not been even picked up - it creates a big administrative hole that shouldn't be there in enterprise-level software.

This is a mess and still not fixed after nearly 4 years?

We have boards were we group different projects by meaning and every project lead is board administrator and has to change the filter when new projects are added. Every time the filter is changed, the human does not think about filter share settings (why should he?) and as a result, nobody can see the board except him!
A very simple problem solver would be to add a note in red that when you change the filter, you shall revisit the filter permission. Or why can't the filter belong to the board or the board admin group and not the user?

It is ridiculous that we don't get information since 2 years.

This buggy behavior is totally inconsistent, since usually an Admin (e.g. in Confluence) can see anything

I've just spent 2 hours on the same thing.

We had a Board administered by the same person as the underlying JIRA Project; but one of his team could not see this Board.

Cause: This Board's Filter was changed to a bespoke filter, and the Filter author forgot to share it out; it was only for him, and therefore not even me as JIRA Admin could find this board or Filter.

Now.... imagine that this person then left. This means there's a LOT of hidden (to JIRA Admins) "me only" Filters and therefore Boards.

I had to, almost ridiculously (he laughed when I asked) for him to send me a screen-clip of his Board > Configure > General > Filter so I could see, mechanically, what was going on (the Filter name was obscure).

It shouldn't be like this for a JIRA Admin.... or should it? As JIRA Admin, people come to me as people would go to a system administrator (and we'd log on as root to get the detail we need)

Could you provide, please, in which version it will be implemented ?
In our case it's a very critical issue:
Example:
I'm a administrator and want to create and configure board to the specific team , but I'm not in the group of this team ( we are managing team groups and users in ldap)
Then I can't to share this board to the correct team, because I can't to share the filter, if I'm not a member of the required team group.

With this behavior I'm not feeling that I'm a real administrator !!!!

What is your proposal for this situation ???
thanks

Definitely agree with Will on this. Jira administrators, i.e., the person who set up the account, owns the account, and pays for the account, needs to be able to see and administer everything. If this is a best-practice separation of duties thing, I'm all for that- then delegate permissions to a board admin to do it in a more limited capacity. But this is ridiculous that I cannot see all the boards nor access them if they don't explicitly give me access. What happens if that person leaves the company? I should be able to see and manage everything as the owner/administrator/superuser/whatever you want to call it.

To be clear, as part of this request, I don't think we would add a global permission for all JIRA administrators to be able to be able to administer boards/filters regardless of filter sharing settings.

We would simply allow board owners to opt in to letting someone else administer their board, despite filter sharing settings.

If we can use Global Permissions to allow jira admins to admin all boards, and admins can admin boards regardless of filter settings, then that would help.

However, the missing bit of the puzzle would still remain managing filters (we need to be able to assign private filters to other owners or have shared filter ownership like shared board ownership) - but that might be a separate issue.

If we solved this by allowing "board administrators" to see boards, regardless of filter permissions, would that be sufficient? Therefore we don't allow JIRA administrators blanket access to all boards, but if it is required, the board owner/administrator can permit someone else to see and configure the board?

I don't think you're actually solving our problem here.

This causes us pain in support. Users complain that people can't see their boards, and it is NOT AT ALL OBVIOUS that this is because the underlying filter is private. Phantom rapid boards that administrators cannot see are a headache. Filters that we cannot adjust, manage, or see are also a headache. We need to be able to at least transfer ownership or increase sharing without needing to use Script Runner to become the filter owner.

Further, the mechanism for transferring ownership of filters is as clunky as the old method of managing rapid boards was - which you acknowledged enough to fix - I suggest that filters needs a similar look.

If that's the case, then we would not likely consider adding functionality to enable admins to see private boards.

That page is for Shared Filters.

The problem here is Private Filters (where a user might not even realise that the filter is not shared to anyone) which I believe are the default filter type created.

We are unable to even see those filters, let alone change ownership or change share permissions.

willthames2 in the latest version of JIRA, an administrator is able to access all the saved filters in the system: https://confluence.atlassian.com/display/JIRA/Managing+Shared+Filters

If there's a particular filter you wish to see, you may be able to change the owner of that filter via the Admin UI, and then change the share permissions.

If a filter is private, JIRA Administrators cannot even access boards, let alone administer them (based on a 6.1.5 release - if this is fixed in 6.1.6 or 6.1.7, that would be good).

We would like to allow shared ownership of filters (to go with the recent shared board administration), and JIRA Administrators to be able to see all filters and boards regardless of privacy settings.

Delegated board administration could help, but the board owner could drop jira-administrators from Board Administration. But while trying to verifiy we found out, that with recent JIRA Agile release now JIRA Administators (from Global Permissions) always can admin Boards.

A board's administrator is the only person who can change the configuration of a board along with JIRA administrator users. By default, the administrator of a board includes the person who created it. If you are a board administrator, or a JIRA administrator, you can change the administrators of a board.

Don't know, when this was introduced, but it is fixed now.

Thank you!

Cheers
Holger

Hi holger.schimanski@bayerbbs.com,

With the introduction of the delegated board administration feature, is this feature request still desired?

Thanks,
JIRA Agile Team

mtokar: Yep, they can't see the boards where the filter is not shared with them, they don't even know they exist

sclowes, currently I believe we allow an administrator to configure any board they can see. So is the problem here that administrators do not get visibility just because they are administrators?