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...
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
[JSWSERVER-2849] Enable "Teams" as top-level concept
| Resolution | New: Low Engagement [ 10300 ] | |
| Status | Original: Gathering Interest [ 11772 ] | New: Closed [ 6 ] |
| Labels | Original: hzn planner rapid team triaged | New: cleanup-seos-fy25 hzn planner rapid team triaged |
| UIS | Original: 0 | New: 1 |
| UIS | Original: 1 | New: 0 |
| Remote Link | New: This issue links to "Page (Confluence)" [ 464922 ] |
| Remote Link | New: This issue links to "Page (Confluence)" [ 464864 ] |
| Remote Link | New: This issue links to "Page (Confluence)" [ 462178 ] |
| Remote Link | New: This issue links to "Page (Confluence)" [ 459987 ] |
| Remote Link | New: This issue links to "Page (Confluence)" [ 459680 ] |
| Remote Link | New: This issue links to "Page (Confluence)" [ 459029 ] |
