How to manage multiple assignees on a ticket?

[Emma Haley]

Hi,

I would like to be able to assign multiple people to a ticket. For example, the developer is assigned in the default Assignee slot, but I would also like to create an assignee slot for the QA which will work on that ticket too.

I am having a few issues with my current setup:

- It doesn't send email notification to the QA assignee when we add them

- It doesn't show the QA assignee's display picture on the card in the sprint board, it only shows the main assignee

Does anyone have any ideas about how to at least solve the first issue?

Thanks!

[Patrik Korovsky · Accepted solution]

Hi @Emma Haley

Before I continue with my proposal, I would like to share my thought regarding the assignee. I assume that QA can work on the problem after the current assignee (DEV) is finished. I believe that having one assignee is best and proper workflow is the way to go.

With that said, here are some options:

New multiselect field

The assignee cannot be removed from the board view.

• Issue view
  
• Board view
  
  
  

Set up:

1. Create a new custom field from the Advanced options: User Picker (multiple users).
2. Add it to your Issue screen (Optional: Remove Assignee) -> The data will still be there.
3. Create an automation that sends notifications as needed.
4. Add your new field to the card layout in the board settings

New single select field

• Issue view
  
• Board view
  

Set up:

1. Create a new custom field from the Standard options: User Picker (single user).
2. Add it to your Issue screen
3. Create an automation that sends notifications as needed.
4. Add your new field to the card layout in the board settings

Automation to send notifications:

For ticket updates:

• Trigger: Field Value changed (select all fields to monitor)
  • Example: "Assignee"/"QA Assignee", Description
• Action: Send email to Assignee"/"QA Assignee
  • Example:
    • Subject: Issue {{issue.key}} was just updated

For comments:

• Trigger: Issue commented
• Action: Send email to Assignee"/"QA Assignee
  • Example:
    • Subject: Issue {{issue.key}} was just updated

[Emma Haley]

Hi, that all works brilliantly for me. Thank you!

I am wondering, do you know if there's a way to display the users picture next to their name on the board settings too?

And yes I agree with you on your first point - but the idea is we assign the QA to the story so they can start writing test cases before the feature is completed by the dev.

[Patrik Korovsky]

Hi,

Good to hear this helped you.

I do not know of a way to also display the icon. Nor of a way to hide the default assignee. If you would like a clearer view of what issue is assigned to whom I recommend tinkering around with swimlanes https://support.atlassian.com/jira-software-cloud/docs/configure-swimlanes/.

Regarding writing test cases. Have you considered creating a QA ticket under the main issue? This can organise your board in a new way.

• Swimlane -> Stories (This shows all issues that have a subtask in a separate swimlane)

[Mayur Jadhav · Accepted solution]

Hello @Emma Haley ,

Welcome to the Atlassian Community!!

out of the box Jira support only one Assignee field and which will trigger the notification.

You have created custom user picker, and which is not triggering the notification that's correct Jira doesn't support the functionality out of the box, however you can leverage the Automation rule so that whenever fields are modified then will get notification.

Hope this information helps.

Regards,
Mayur

[Emma Haley]

That's amazingly helpful. I will give this a go, thank you!