+1 for allowing more than one owner of a dashboard on Jira Cloud, please.

This is embarrassing tbh....

Multiple editors on Cloud: +1

Multiple editors on Cloud: +1

+1 for multiple editors; this is sad 

+ 1 for Cloud

This is completly rediculous. Please Fix

+1 for allowing more than one owner of a dashboard on Jira Cloud please.

I would also really like this to be in the Cloud version.  It's ridiculous that only one person can edit a dashboard.

Hi Team, kindly advise if this function will be implemented on Jira Cloud in the near future. Thank you. 

 REALLY need this feature in Cloud, please! PLEASE(!?) 

Still waiting for this feature in the Cloud

Why would you not release this into cloud at the same time as Jira Server? When will this be available? We have multiple contributors, yet can only have one person authorised to update the data. 

will this feature be available in the Cloud?

yes, when will the feature be available in Jira Cloud?

Riley Manns if you share a dashboard you have Edit Access to (or your own) then you can add Editors the same way you would add Viewers

No offense, but it would be insanely helpful if you provided actual instructions on how to do this..

When will this feature be available to Jira Cloud ?
Will be very helpful...

Good feature ... thank you!

We have confirmed that adding a group for edit will work (people in that group can edit a dashboards  ) but when we add an individual , that person does not get the edit option . We are running 7.13.5. What am I missing from this great fix?

@jdevenny I cannot see this option in my interface. Is it limited or?

is this available for Jira cloud as of today? to @NataliaWroblewska

Yeah, I am happy with that

Read the version wrong, thanks for pointing that out.

8.2??

7.13 is the latest release at the moment. Jira 8 is still only available in EAP

Ignore previous comment here, read the version wrong.  

Does not appear to yet be available for Jira Cloud:
https://jira.atlassian.com/browse/JRACLOUD-17783

Both

Are you the owner? or admin with privs to change ownership?

Hi @Harold Wong .

I am using a cloud version, is this available on here? If so where do I find the settings for this?

Hi @carmen.jackson 

is your Jira 7.12 yet? 

Thank you for implementing this feature. Is there an article that explains the details of the feature and how to use it? I am not seeing where you can assign permissions for a dashboard.

Thank you

Hi nwroblewska ,

thank you very much for your reply! I could open the JAC issue, but basically what i had i my mind was, to solve JRASERVER-41269 as you mentioned. Because having the default group / admin-group added to each filter would solve the problem of orphan filters from disabled / inactive users (and you would solve 427 votes!  ).

Eitherway i will open the issue and mention this issue and the other one!

Best regards, 

Oliver

Hi oliver.zabel !

Thank you for checking out this feature and providing an early feedback!
"admin-groups added by default, or to have the option to specify a default group" That's an interesting feature proposal, would you be able to create a JAC issue for it, so we can monitor the need for that?

"ATM i can now see, that a user created a personal filter in the audit log, but i can't view nor change it" We are currently taking under consideration this feature, see: https://jira.atlassian.com/browse/JRASERVER-41269, please vote for this ticket and follow it to be updated about the progress.

Cheers,
Natalia

Hi, i looked into the feature in 7.12/8.0 and it would be great, to have the admin-groups added be default, or to have the option to specify a default group. ATM i can now see, that a user created a personal filter in the audit log, but i can't view nor change it. This should be possbile for admins. Please consider adding this feature. Thanks!

This feature is finally included in Jira 7.12!

https://developer.atlassian.com/server/jira/platform/preparing-for-jira-7-12/

Or we could just keep complaining on a daily basis  

In progress but not assigned, maybe you need to go to BCN for summit 18 and press them on it

Guys, seems that we'll have to wait 9 more years 

Happy 9th Birthday to the 5th highest voted open Jira feature request.  Glad its in In Progress as of May 2018.  Is there an expected release timeframe? Thanks.

Did anyone get an ETA on the production release for this? 

Thanks everyone for your comments and feedback,

after 9 years they are starting to work on this issue.

I am very surprised that there are a lot of things that really limit the Admin and users abilities to do the work efficiently.  We are adopting the tool and will spend hug investment in it so we should not have to beg for a changes what we need to get the works done.

Bottom line: Filter administration is just plain broken.

1. It shouldn't be possible for any user to create something a system admin can't see or manage, but it is.
2. It shouldn't be possible for a team's agile board to be damaged by disabling/removing a single user, but it is (if they owned the board filter).
3. It shouldn't be impossible to manage user-created objects at scale without buying add-ons, but it is. 

We really, really need a fundamental change to permissions for filters AND subscriptions. 

The design must consider team-level and enterprise-level needs, and remove any reliance on user impersonation or DB access. As a system admin, I should be able to delegate this stuff to project leads or group owners and walk away.

I ain't proud.... I'm begging you!

shhhh they are too busy moving summit to Europe from San Francisco to worry about these small details

like FFS over 1000 votes get your head out of your rears guys. 

After many years, this is still an open issue.  This feature is probably one of the big ones that most people will need to be able to do their jobs efficiently.  I hope it will get worked soon.

Having the ability to assign a JIRA/Crowd group of users as an owner of kanban board/dashboard would allow us to have a group of expert business level users to maintain boards and dashboards without the need of an admin. Let's help our users become owners.

Can we get this feature please.

We have the same problem in the company. At the moment when an owner of a board filter or dashboard is not available, the entire team is stuck. 

We need this too!

Here's the link you asked for, to save clicking: https://marketplace.atlassian.com/plugins/com.qotilabs.jira.shared-ownership-for-dashboards-and-filters

@kelly

I do not like to post links but you can easily find them on the "find new add ons"

Shared Ownership for Dashboards/Filters by Qotilabs

Can you provide the link to the plug in?

Better late than never...

Currently we are using a paid add on that adds a button to take ownership so they can make changes when needed which happens frequently because we added an area for notes, kind of like a group post it area... 

When working in a team, information and reports are shared. The current configuration when filters and dashboards can only be edited by one person, makes that person become a constraint on the entire team. It would make much more sense to allow a group of people to edit filters and dashboard, making the work more collaborative.

One of my issues as an administrator is that I am unable to determine easily which filters are used in which gadgets on which dashboards. With over 100 dashboards, as an administrator I have no way to know which filters I can delete when cleaning up the system. I have only found that I have to visit each dashboard that is no longer used, write down the names of the filters used on that dashboard, then return to the filters management area to delete those filters, and hope that they are not used  by someone else or on another dashboard. This is way too time consuming, resulting in filters being retained that may no longer be needed. In the "manage filters" area, I need to be able to see which gadgets and dashboards are using a particular filter. Has anyone else run into this problem? How have you handled it? Am I missing something?

Thanks, that will be a step forward towards using features such as dashboards (largely populated through usage of filters) as a team and not as an individual (as it should be when developing in an agile manner).

Hi everyone,

Thanks for participating in this issue, either by voting, commenting or watching. We value your feedback in all forms and suggestions in Jira.atlassian.com is no different. I know it's been a while since we last commented on this suggestion and we are sorry to have kept you so long without a clear answer.

Your feedback has really helped us better understand the varied challenges you face without an ability to edit shared filters or dashboards. Despite our lack of communication, this problem has actually been an area that we continue to explore. As one of the results of the exploration, we've decided to prioritise this challenge on our roadmap.

Our next steps are to explore options for solving problems associated, validate them with you, our customers, and prioritize the most impactful changes for development.

Thank you again for all your feedback on this suggestion and we look forward to providing you with more updates as we work to improve filters and dashboards configurability.

Thanks,
Jakub Lazinski
Product Manager, Jira Server

As a user, I have been frustrated by the filter management features as well.

I believe there are a number of characteristics of Filters that make things difficult that will need to be addressed if such a change is implemented. I mean that if you approach sharing 'management' of filters, you will need to consider all aspects of the 'filter infrastructure'. Most of these aspects are endemic to the style of coding and UI 'theory' utilized throughout Jira and the Atlassian products.

Jira segregates the complete set of functionality for managing a 'domain of activity' into forms that funnel the user into UI contexts where the available functions only enable them to perform only the operations allowed by their permissions. This eliminates overall infrastructure development concerns such as granular permission-gated user controls and visibility management of controls and features by permission.

The filter permissions domain reveals this as the four levels of filters that show up under 'Manage Filters' on the Issues Menu: Favorite, My, Popular, and Search. The management capabilities (operations) provided in each of these sub-forms are distinctly different. Only 'My' allows editing and deleting. And the 'editing' consist only of assigning 'shared visibility scopes': allowing the filter to be 'shown to' others according to group, all groups, administrators, or projects.

However, changing those visibility settings 'by user' is the real bottleneck. Each user can enable filters under their control to be viewed and applied by other users, but the 'editable options' within Filter Management a limited to this one function: sharing filters. Editing the actual 'filter statement' does not happen within the context provided by Filter Management. Again, this is a design decision that favors the interests of the platform developers interests rather than the users' interests.

When 'editing' filters, you are allowed to place the filter statement on the JQL editing repl in the Search screen. However, the Save, Save As, and Discard options in that repl do not enable a smooth 'edit/update cycle' with the Filter Management. I frequently find conflicts on the JQL repl which prevent me from 'editing' a filter, but require me to delete a filter and then use the repl to re-create one in my desired formulation. And that again is limited by the 'who created it' problem. This single hiccup will play havoc with the plan to solve the 'editable by a single user' problem with a 'simple' solution.

This concern is primarily the result of the primitive behavior of the 'save as' operation. What is missing is an 'overwrite' operation. And that again requires attention to the relationship between the filter permission scopes and the JQL repl operations. Again this is a design decision that favors implementation resources over user resources. 

The primary problem with Jira usability is their heavy-handed decisions to segregate functionality across forms to simplify the maintenance of the feature set. In nearly every operation, a user must visit several far-flung areas of the application, traversing a number of UI paradigms to find switches and configurations, each of which have little contextual relationship with the user's focus on, for example, 'filter management'. 

So to manage a single filter, a user will likely have to visit each of the four filter management scopes to determine (remember) where the editable operations are exposed, attempt to discover whether the filter can be edited by them using the JQL repl, try to imagine how these permissions are logically related, visit the 'applications area' to see which widget on the system dashboard is using which filter, return to view the dashboard to remind themselves of their goal, return to the repl to test the result of the filter, go to their profile to change the semi-global setting to expose all their filters as 'public/shared', la-de-da-de-da...

And then they must return and repeat in a variety of sequences that depend on several consequences of how things were initially established before the users ever discovered the full scope of the infrastructure features they have to deal with. Most of which was certainly done before they understand how each of those features provides only a very strange sub-selection of the entire range of operations necessary to perform any of the functions of the many overlapping features this filter infrastructure touches.

The primary characteristic we should be asking Atlassian for is that they stop this crazy splattering of functionality across the wild terrain of their application and immediately pledge to consolidate all aspects of each of their features into a single, closely related component/module/feature where users can see and manage functionality in a single feature context that makes sense and provides enough flexibility to support a small but sufficient range of workflows and user goals.

They obviously just started developing in several places at once, and have grown their application into a system that communicates between the several infrastructure elements that grew up around each of those starting points. In many ways, this has contributed to the ease of use, but in each of those areas, what is missing is the refinement of the UI that results from exposing those disparate functional areas in organized contexts suitable for logical and reasonable user operations performed in a single 'place and time'.

Among these, my favorite peeve is that sprints are an attribute of a board, and not a first class citizen that can be managed in a fully operational crud manner like every other primary development domain. The board interface is another similarly disjointed and dispersed, context-less experience!

Thanks Greg!

JIRA admins can already change ownership of a filter. Only the owner can edit it though, so as a JIRA admin if you're asked to fix a filter that someone else owns ('cause they're sick/on leave/can't do it themselves) then you have to do an annoying ownership dance of transferring to you and then back again, but at least you can do it.

One of the top google results, should have instructions for you: https://community.atlassian.com/t5/Jira-questions/Unable-to-change-the-owner-of-a-filter/qaq-p/187087

Allowing a group to own a filter would ideal. At the very least, please allow JIRA Administrators to change the owner of a filter and/or edit any filter.

Why should I have to pay $400 and then $200 annually for something that should be part of core Jira? Atlassian already put their prices up by 10% precisely so they could do "more support".

Never, go get a marketplace add on.

There is one I am using called shared ownership by quotilabs

@azad3

Can we have an ETA for this feature? This is a much needed thing. 

+1 to allow shared Dashboard in a group to be available for editing by users within same group.

@Robert @Gianni how is it relevant to talk about that on this ticket?

@Robert, FYI, we are currently workarounding the same issue JRASERVER-3821 by using the [Extended Schemes Plugin |https://marketplace.atlassian.com/plugins/com.develocenter.jira.links-scheme/server/overview.]

I think Atlassian's product are the best in the business, that is why we use them.    This would be a nice fix but there are many more that I would prefer first, such as 

Just my two cents.

What's stopping Atlassian is that they don't care about their customers. They've now put their prices up for the second time in about 2 years, ostensibly so they can afford to put more resources into improving Jira. Which is funny, because when we purchased JIRA 4 years ago initially, there was never any suggestion that we wouldn't be receiving on-going feature improvements as part of our maintenance contract. I can count on 1 hand the number of actual useful feature improvements they've delivered over that time (Agile is a different story - that's been worth its maintenance contract), meanwhile there's been dozens of other 'improvements' that mostly boil down to UI enhancements that confuse my users and 'fix' what isn't broken.

But hey, you don't get to buy $70M dollar mansions in New South Wales without some business savvy, so maybe I just don't understand Atlassian's strategy.

We have also found out that we require this feature. Teams here share dashboards among all members and is quite silly that only one person can edit it, whoever created it initially. We tend to end up with multiples copies of the same dashboards because of the lack of editing capabilities, defeating the purpose of having a "shared" dashboard to start with.

To be honest I don't understand what is the problem here. It should be relatively easy to implement, and the feature has almost a thousand votes, what is stopping Atlassian here? I would appreciate some comment.

Absolutely need this! I created (and shared) a dashboard with a group of people who have it bookmarked/in documentation and now I am the only person who can update it! This is foolish!

I stopped watching this issue still I am getting notifications for this. 

Can someone have a look ?

yea join the club

this was open since 2015

maybe in JIRA 8.0 they will add commonly requested features, until then an add on / gadget solving your problem is the status quo (because it is developed by someone else)

I require this functionality.

the defacto answer to all your problems is to look for a 3rd party addon/plugin

[arewold1111142294] Not as surprised as I am after waiting 8 years for a fix

Frankly surprised that this functionality is missing.

We need this ! Working in a big company with many developers, this is very painful when one guy of the team is sharing a dashboard or a filter and we cannot  modify. So currently, we duplicate a huge amount of these.

Is there already a Suggestion that tracks the ability to pass ownership a dashboard to someone else without being a JIRA admin?
surely I'm not the only one who desperately need this?

only problem is if someone makes that plugin and then they incorp it into a new feature release... 

Would be funny if someone started making JIRA Bug fix / update packs and charge for it as a marketplace add ons

Let see.

1- Spend  money to fix usability issues that do not break the application and which won't make a user quick for another product.

2- Do nothing, wait until someone create a plug-in as a workaround and cash on market place royalties.

As a JIRA administrator for our company, the huge number of administrative issues that make administrating JIRA a burden make me believe Atlassian prefer option 2

+1 (corporation)

Opened 8 years ago, not uncommon

@Atlassian why do you not listen to your users? Why not do even 1 long requested feature every release? Hire someone specifically to do that, then you will burn through them before you know it and keep us happy!

This issue is voted #9 in the list of issues open 5 years or more with more than 500 votes. The top issue is open 13 years and has 2381 votes.

project = JRASERVER AND issuetype = Suggestion AND status != closed AND votes > 500 AND created < StartOfYear(-5) ORDER BY votes

The requested feature is so helpful. Please implement this.