I believe that GH should implement a top-level team concept. Having multiple teams pull from a single project right now is cumbersome. (See: http://jaibeermalik.wordpress.com/2010/07/22/using-greenhopper-to-manage-multiple-teams-in-agile/) This should not require custom setup to achieve. And it is frustrating our adoption.
Having separate project per team does not work either, as then there would have to be a separate "bug project" where issues could be reported but not associated with a team. Howver, then the coordination between what bug is in which project would be a nightmare. Enabling multiple teams within a single project, just like VersionOne and Rally is the right way to go.
- relates to
-
JRASERVER-2414 add "project group" feature to ease permissions management
- Closed
-
- Closed
- mentioned in
-
Page Failed to load
-
Page Failed to load
-
Page Failed to load
-
Page Loading...
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
| Form Name | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
[JSWSERVER-2849] Enable "Teams" as top-level concept
Dear Jira Team,
I also about to report a suggestion related to it. There MUST be a concept of Teams with designation and expertise in Jira so that we can better management the users and teams. Also, there should be a permission type, "Team Members". If someone selected this option in Permission Schemes, anyone in the team can access that functionality.
We have 9 projects and if we do not want the team to see each other project, we have to create 9 Permission Schemes. If you implement Team Members and a permission type then one can manage multiple projects with one Permission Scheme.
Best Regards,
Rizwan Akbar
+1 to this. We have multiple teams working on a single project and it's really hard to manage without very cumbersome UI. Having "Teams" along side versions and epics would give a nice Drag and Drop option for a planning board; then each team could filter by Team for their own rapid view.
Hi kevinshine, could you explain how GH 6 makes this worse than before?
Teams as a concept have more of a home in JIRA than in GreenHopper. Implementing them in GreenHopper would probably be a problem in the future if we end up with teams in JIRA.
Kevin Shine
added a comment - In GH6 this is a HUGE problem. 
Hello,
Thank you for submitting this suggestion. We appreciate you taking the time to share your ideas for improving our products, as many features and functions come from valued customers such as yourself.
Atlassian is committed to enhancing the security and compliance of our Data Center products, with an emphasis on sustainable scalability and improving the product experience for both administrators and end-users. We periodically review older suggestions to ensure we're focusing on the most relevant feedback. This suggestion is being closed due to a lack of engagement in the last four years, including no new watchers, votes, or comments. This inactivity suggests a low impact. Therefore, this suggestion is not in consideration for our future roadmap.
Please note the comments on this thread are not being monitored.
You can read more about our approach to highly voted suggestions here and how we prioritize what to implement here.
To learn more about our recent investments in Jira Data Center, please check our public roadmap and our dashboards, which contain recently resolved issues, current work, and future plans.
Kind regards,
Jira Data Center