How to share an issue with multiple users.

[Geylani Özçubukçu]

Hello,

I am trying to prepare utilization reports and be able to assign enough tasks to team members based on their capacity and availability. And currently we standard workflow were when a task is done it goes to review, then to testing and only after the testing is done its moved to complete. 

I have been looking all over the forums and I was unable to find any solution for a team managed jira new gen software project.

I have read suggestions on adding subtasks or linked tasks to the main ones and following them up but it increases the workload of managing jira additional to my other tasks.

Can you anyone offer me a solution or an addon that might work smooth.

Thanks,

[Nataliya Vasyliv_Reliex_]

Hi @Geylani Özçubukçu

Our ActivityTimeline plugin provides a solution in splitting a task into multiple parts. But our plugin in a comprehensive tool for resource management and capacity planning.

Let me know if you have any questions.

Best, Nataliya, ActivityTimeline Team

[Geylani Özçubukçu]

Hello,

I am using Activity Timeline but unfortunately your solution does not work on team managed projects.

[Nic Brough -Adaptavist-]

Are you trying to do the horrible "multiple (current) assignees" thing that simply doesn't work in real life?

Or do you mean you want to split up issues into fragments that can be given to different people (or even teams)?

[Geylani Özçubukçu]

I am looking for a solution where when a developer completes a task and moves it to code review and testing, I want to be able to assign it to the reviewer and tester rather than keeping the task on the same developer. 

[Nic Brough -Adaptavist-]

Ok, that's good practice.  The best thing to do is simply reassign the issue to the person who is going to be responsible for getting the next steps of the task done.

A lot of us will automate this - we'd add custom user-picker fields for reviewer and tester (maybe developer too, depending on your process).  The most common process I've seen is that the issue is unassigned until the developer picks it up out of the queue, and assigns it to themselves.  They enter the reviewer and/or tester when they know who they're going to be.  Then, in the workflow, when the developer hits "done, needs testing", there's an automation or script which reads the tester field and assigns the issue to the person in there.  Similarly, when the tester sends it for review, the assignee is taken from the reviewer field.

[John Funk]

Hi Geylani,

I am confused as to exactly what your need is. Can describe in more detail what you would like to see? 

[Geylani Özçubukçu]

Hello John,

In our current operation we have 5 phases of code development: which is Todo, In Progress, Review, Testing and Done. All the Reviews and Testings are done by different team members because of this we keep the tasks on the Developers until the tasks are put in Done. I am looking for a feature where I can assign multiple team members on a task for utilization purposes.

[John Funk]

You are not going to be able to assign a task to multiple people. You will need to create a custom field (probably a single user picker field) to capture the additional person.