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
-
JRACLOUD-2414 add "project group" feature to ease permissions management
- Closed
[JSWCLOUD-2849] Enable "Teams" as top-level concept
Workflow | Original: JAC Suggestion Workflow JSWCLOUD [ 4100322 ] | New: JAC Suggestion Workflow 3 [ 4372790 ] |
Workflow | Original: JAC Suggestion Workflow 3 [ 3700390 ] | New: JAC Suggestion Workflow JSWCLOUD [ 4100322 ] |
Workflow | Original: JAC Suggestion Workflow [ 3472590 ] | New: JAC Suggestion Workflow 3 [ 3700390 ] |
Workflow | Original: JIRA PM Feature Request Workflow v2 - TEMP [ 2315621 ] | New: JAC Suggestion Workflow [ 3472590 ] |
Status | Original: Open [ 1 ] | New: Gathering Interest [ 11772 ] |
Workflow | Original: JIRA PM Feature Request Workflow v2 [ 2037143 ] | New: JIRA PM Feature Request Workflow v2 - TEMP [ 2315621 ] |
Workflow | Original: JIRA PM Feature Request Workflow v2 - TEMP [ 2025421 ] | New: JIRA PM Feature Request Workflow v2 [ 2037143 ] |
Workflow | Original: JIRA PM Feature Request Workflow v2 [ 1885409 ] | New: JIRA PM Feature Request Workflow v2 - TEMP [ 2025421 ] |
Project Import | New: Sun Apr 02 01:01:23 UTC 2017 [ 1491094883663 ] |
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