When using JIRA, an Issue is assigned to one person.
When using Portfolio, an Issue is assigned to a team.
Using JIRA, we would add sub-tasks under a Task or User Story (Parent Issue) with each sub-task addressing a particular skill. For example, if the Parent Issue required a Front End skill and a Back End skill only ( no database involvement ) two sub-tasks would be generated. These sub-tasks would be shown on both the Scrum Board for backlog management and also the Kanban board to monitor the progression of the Parent Issue and its sub-tasks as the status changed.
However, with Portfolio, it appears that an Issue must be assigned to a team even though the Issue may not require all of the skills that the team has to offer. This will skew the team productivity figures, I believe.
How can the Scope be configured so that resources are assigned to the Issue according to need only ?
