-
Suggestion
-
Resolution: Fixed
-
None
Currently only the owner or a jira-admin can do this. I think it would be good to allow this so you can have other team members adjust the settings.
Currently at my company there are multiple producers on a team that all use the same board and they would like to continue to have one board for the whole team.
- details
-
- Closed
- is duplicated by
-
- Closed
-
- Closed
-
- Closed
-
- Closed
-
- Closed
- is related to
-
- Closed
-
- Closed
- relates to
-
- Gathering Interest
[JSWCLOUD-9587] Add the ability to specify multiple board administrators so other users can change the configuration (delegated admin)
Many thanks for your patience and votes on this issue, I am happy to let you know that this is now shipping in JIRA Agile 6.3.2.
Kind regards
Tom Kotecki
Product Manager, JIRA Agile
Dear Tom Kontecki,
you wrote: "we hope that our open approach to feature requests and backlog ordering allows you to see where we are headed."
Question: where can we see this open backlog ordering?
Kind regards – Rainer Mueck
Hans-Jürgen Tappe
added a comment - Hello Tom!
Would you consider to keep the classic boards until this issue is solved?
Thanks,
Hans-Jürgen
Hans-Jürgen Tappe
added a comment - Hello Tom!
Would you consider to keep the classic boards until this issue is solved?
Thanks,
Hans-Jürgen Hi All,
Many thanks for your comments and votes, I wanted to provide an update on the status of this issue: we are now planning to deliver this within the next 12 months.
Just like any Agile team we have ordered the backlog based upon what we believe provides the greatest value to our customers. There are now over 10,000 customers worldwide so we try to find the right balance between the varied needs of this large, and growing, group. It is not an easy task. Thankfully we have many passionate customers that are able to provide feedback to help drive our vision and order the backlog - thank you!
Thanks for your patience, we hope that our open approach to feature requests and backlog ordering allows you to see where we are headed.
Kind regards
Tom Kotecki
Product Manager, GreenHopper
Gil Carranza
added a comment - A permission scheme needs to be instituted to allow for flexibility. 
Michelle Weller
added a comment - Having a single admin for a rapid board is bottle neck when making changes. It reduces productivity especially when the owner is offshore.We view this issue as a high priority. Resolving this "issue" will improve efficiency.. This is a current gap in scrum management.
Michelle Weller
added a comment - Having a single admin for a rapid board is bottle neck when making changes. It reduces productivity especially when the owner is offshore.We view this issue as a high priority. Resolving this "issue" will improve efficiency.. This is a current gap in scrum management. 
Vladimir Berezniker
added a comment - As a commercial license holder +1. We get constant queries from our users to be able for more than one person to administer a board. Having more than one person administering is critical to avoid key man risk.
Vladimir Berezniker
added a comment - As a commercial license holder +1. We get constant queries from our users to be able for more than one person to administer a board. Having more than one person administering is critical to avoid key man risk. 
Nicolas AVERSENG
added a comment - This is definitely a major impediment for using Rapid Board and switching from Classic boards. The current behavior is completely misaligned with the projects roles & permissions in JIRA projects.
It is really too bad that this is not already scheduled for next release.
Nicolas AVERSENG
added a comment - This is definitely a major impediment for using Rapid Board and switching from Classic boards. The current behavior is completely misaligned with the projects roles & permissions in JIRA projects.
It is really too bad that this is not already scheduled for next release.
Great news!