Parallel workflow

Aron Felberbaum January 6, 2015

Any suggestion on how to do a Parallel workflow (e.g. two developers working on same issue)

1 answer

1 accepted

Comments for this post are closed

Community moderators have prevented the ability to post new answers.

Post a new question

1 vote
Answer accepted
Nic Brough -Adaptavist-
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
January 6, 2015

Not sure there's a great way to do this, it depends a lot on how you work.  The main aim of the "assignee" field really is to prevent any of those fights about "I thought someone else was doing it".  Everywhere I've worked that uses multiple assignees or group assignees has had that problem, it's human nature, and I've actively solved productivity and responsibility issues by making it clear that there is only ever one individual responsible for something at any one time.

That said, three quick ideas

While keeping the assignee as the single point of contact for an issue, you could have a user picker field for "other developer(s)".  

If you have defined named pairs or even groups, you could define a dummy user for that set of people as well (but you're drifting into "I thought someone else" territory with that one)

Have a look at the nature of the work - if your two developers are working on the same issue, they probably are not working on the same part of it.  Break it down into bits and use a subtask for the second developer to work on it.  Or even a subtask per developer, only moving the parent on when they agree that all the subtasks are done

TAGS
AUG Leaders

Atlassian Community Events