-
Suggestion
-
Resolution: Unresolved
-
None
-
6
-
4
-
NOTE: This suggestion is for JIRA Portfolio Server. Using JIRA Portfolio Cloud? See the corresponding suggestion.
Problem Definition
At the moment, Epic can only be assigned to a single team. The same rule applied to team assignment in initiative as well. For each epic (broken down from initiative) or story (broken down from epic), only one team can be assigned to it.
Suggested Solution
It would be great to have the option to allow epic / initiative assignment to multiple teams and resources.
- is duplicated by
-
- Closed
- relates to
-
- Gathering Interest
- links to
| Form Name | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
[JSWSERVER-25177] Allow epic assignment to multiple teams and resources
Dear all,
I would like to inform you that this issue in the project JPOSERVER is being migrated to the new project JSWSERVER. Your votes and comments will remain unchanged.
Our team at Atlassian will continue to monitor this issue for further updates, so please feel free to share your thoughts or feedback in the comments.
Sincerely,
Aakrity Tibrewal
Jira DC
I completely second this!
Atlassian, I think it is completely false assumption that an Epic can only be related to one team only but just the opposite. An Epic is perfectly suited to make sure that teams work together on several topics. The world is just too complex. I would not perceive this field as a replacement for the current team field but an addition for different purposes (the current one would be the main responsible team, the new one would be the collaboration of the teams). I see many customers abuse the label field for that purpose.
Unfortunately custom fields do not allow, AFAIK, to add entries from the Jira set of teams.
Also critical for us!
Without this, we have to use a separate custom field, which is clunky and not helpful.
I'm also interested. Currently I want to add one team (ie. more than 1 person). Thanks.
Is this feature coming soon? We need to be able to assign an epic to multiple teams.
We have multiple Epics going across team and need to be able to plan accordingly. We NEED to be able to assign more than 1 team to an EPIC.
Need this feature because the higher you go up the Jira Portfolio issue hierarchy, the more likely that an issue's children will be assigned to various teams. It is not uncommon for a single Epic to have child stories spread across multiple teams. For Initiatives, it even more likely that its child Epics belong to multiple teams.
Leaving the Team field empty is not a suitable work-around. Although scrum board filters and Portfolio plan issue source filters can account for Team = XXXX OR Team is EMPTY, there are difficulties in Jira Software (Server) 8.3.1 and Portfolio for Jira 3.8 whenever Team is empty:
- Portfolio's improved experience UI shows Initiatives without a Team value as "Unassigned", and these Initiatives cannot be expanded.
- Scrum boards in Jira may not show Epic Labels on Stories properly when the associated Epic lacks a Team value.
It may be a requirement of scrum that a story only be permitted to be assigned to a single team. But there's no need to force that kind of restriction. My suggestion: allow any number of teams to be assigned to any issue, and see where that leads.
We really need this issue fixed as soon as possible.
We are using Portfolio for Jira v2.18.0
We are facing this issue:
I have an EPIC, and I have 2 User Stories for that Epic.
I have 2 different teams assigned for the 2 different User Stories.
In Portfolio, it shows there are 2 teams assigned for the EPIC. ( It is calculated by the Portfolio plugin automatically)
We made Portfolio's Team custom field visible in JIRA also.
The problem is that when I open the Epic in JIRA, I can't see that 2 teams, only 1 or none of them.
+1, this is a very important feature for us as well. I spending more time finding hacks instead of having this functionality built in, the implementation shouldn't be that hard as this behavior exists already.