Atlassian Team members are employees working across the company in a wide variety of roles.
July 23, 2018 edited
Hello Maurycy,
As covered in the following KB article "JIRA is designed so that issues must be assigned to a single individual", but offers up a method to accomplish this:
But as Portfolio is concerned it is looking at the issues with the intended design, and looks at a single user per sub-task to make a plan for the workload.
From your described workflow I would recommend taking a process shift approach to address this and try to define the Story level as the part that is going to be worked on by multiple people and use the Sub-Tasks as the individual assignments.
As per the link that you have provided to 'How do I assign issues to multiple users' the last option is:
If you have a task managed by different users then you are able to break the combined task into individual subtasks with their own single assignees.
That's exactly what we are doing at JIRA level but Portolio for JIRA doesn't support such approach.
Let's take a real life example:
A Story represents a single unit of work (business requirements + acceptance criteria)
We have people who are able to pick up some of the aspects of the story (let's call it sub-task 1 and sub-task 2) but the other aspects require a different skill set. Currently we create a sub-task 3 which is assigned to a different person
The end result on JIRA
Story is assigned to Person X
Sub-Task 1 and Sub-Task 2 are assigned to Person X
Sub-Task 3 is assigned to Person Y
Portfolio for JIRA shows an error message "Sub-tasks must to assigned to a single person and can't be assigned across teams or people.".
As per KB article I expect that Portfolio for JIRA does allow to plan for sub-tasks assigned to different people. Currently this is not the case.
