Why limit Dashboards to single ownership? No doubt this comes from traditional project management practice of control and needing one person in charge or control.
Best agile teams self organize so nothing better then providing them with tools to allow this. Currently Dashboards in Jira just don't do this. They work for "a person in control" not the team. Team dashboards are best owned by a team.
Doing so will make it more likely that the team will use the dashboard and care for the data that shows up or doesn't.
This will also solve the problem of "Dashboard proliferation" and managing them for a group or a team, as current limitation of ownership imposes. When the owner leaves the team or the company the teams are often orphaned with respect to their Dashboard, if gadgets don't work or need to be updated then they can't.
Please fix this, as its a real pain in the you know where ....
Community moderators have prevented the ability to post new answers.
Still an on going issue. It can be tracked against https://jira.atlassian.com/browse/JRASERVER-17783
Recommended Learning For You
Level up your skills with Atlassian learning
Learning Path
Apply agile practices
Transform how you manage your work with agile practices, including kanban and scrum frameworks.
Learning Path
Configure agile boards for Jira projects
Learn how to create and configure agile Jira boards so you can plan, prioritize, and estimate upcoming work.
Jira Essentials with Agile Mindset
Suitable for beginners, this live instructor-led full-day course will set up your whole team to understand how to use Jira with an agile methodology.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.