-
Suggestion
-
Resolution: Unresolved
-
7
-
2
-
Is there a way to assign more than one shared team on an issue. I only see the opportunity to add just a single team.
On many of our global initiatives we have a team set to execute this, but in cases we need central teams from supporting departments from within our organization to participate to execute work for this initiative.
These are more ad-hoc or small pieces of work that they have to execute. So these teams or members of these teams are not allocated within the roadmap of these initiatives.
Because all related work might not yet been set in Epics, Stories, etc..., to be able to assign this to a team.
From management perspective we want to see which supporting teams are requested to participate on initiatives.
But we want these teams to know that they need to participate. So we have setup shared teams for this matter, but we want to be able to set more than one team to an initiative.
Off-course we could use custom fields or components (per project, very administrative work) for this. But the teams option from advanced roadmap would be preferred as we want to start to use the capacity of the team option as well in the near future.
| Form Name | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
[JRACLOUD-87760] Is there a way to assign more than one shared team on an issue?
Added my vote. This is another one of those "I can't believe this isn't a feature already" things that keeps my love/hate relationship with Jira alive.
This would be incredibly useful. I think others have expressed how it could be used but I will state the value that I see. Most mature software organizations have their inflight feature work but they also maintain a roadmap that sets lose plans for their releases and can go out years. The further out the release the more scope that isn't understood. Meaning, we don't have the stories identified. However we still need to manage our roadmap and tend to use head count/staff weeks for ROM (rough order of magnitude) estimates. Some of our features (Epics) span multiple teams and this is figured out at the time of requirements gathering and high level design. At this point we still don't have stories nor are we ready to invest in creating stories and sprint plans around the features. So, having the ability to say an epic impacts Team A, Team B, and Team C would be great. I think it would also require some way to quantify the amount of impact (Team A requires 12 staff weeks, Team B requires 6 staff weeks, and Team C requires 10 staff weeks).
Definitely voting for this feature.
Would love this, especially helpful when support teams will need to be involved in an epic. Would love to see something along the lines of how Atlas handles teams assigned to projects.
Is it really so, that EPIC is automatically assigned to multiple teams in case tasks or stories in EPIC are assigned to different teams? For me, it does not work like that. I have boards created for each TEAM and epic does not appear on the boards.
Initially, I also voted for this issue. But then I found out that in Advanced Roadmaps, it is possible for us to assign Stories to each one team and then the corresponding Epic (comprising the separate Stories) automatically is assigned to multiple teams and will be shown accordingly.
That for us resolved the need to assign a single issue to multiple teams.
Voting for this! It would be extremely helpful when portfolio planning for us to be able to add multiple teams to an issue to see how much capacity we have to execute projects.
Yes, please! We need this functionality in Data Center as well.
Same story here. We'd like to assign multiple Advanced Roadmaps teams to initiatives.
Voting for this feature
it will be very useful - especially when multiple teams are involved in resolving a story (which is quite often)