nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Is it possible to have two or more assignees?

Kiriakos Tzannis

Is it possible to have two or more assignees, if for example you practice pair programming?

We have the problem, that if two work on one card, only one person is the assignee of the issue. And if you look in Jira it seems that the other person is not working on any issue.

Accepted answers

MatthewC

Along the lines of Jobin's answer we have multiple user picker fields, each holds a different person who contributed to the feature at a different point in it's lifecycle.

e.g.

owner
analyst
developer
UAT tester
Systems tester
Regression tester
Sign-off

It also means you can automatically assign issues via the workflow. e.g. if it fails testing, it gets re-assigned to the developer. You could easily have two developer fields. You can also gather the user information via transition screens in your workflow, so you have to name a UAT tester to enter UAT. This value is assigned to UAT Tester and also copied to the assignee field

All comments

Jobin Kuruvilla [Adaptavist]

Not out of the box. But a common workaround is to use a new user picker (or multi user picker) custom field named "Pair programmer(s)" or something and use that also in the reports/gadgets and filters.

You can also include the new field in notifications.

Assignee will still be a single person.

MatthewC

Along the lines of Jobin's answer we have multiple user picker fields, each holds a different person who contributed to the feature at a different point in it's lifecycle.

e.g.

owner
analyst
developer
UAT tester
Systems tester
Regression tester
Sign-off

Kiriakos Tzannis

Thank you for your answers. It makes sense to add an additional developer user picker field. I will discuss this in our team.