Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Next challenges

Recent achievements

  • Global
  • Personal

Recognition

  • Give kudos
  • Received
  • Given

Leaderboard

  • Global

Trophy case

Kudos (beta program)

Kudos logo

You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.

View group

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Multiple assignees for an issue

For cross functional tasks, we need to add 2/3 assignees to a Software project on JIRA. The issues in which they are Primary/Secondary assignees should be displayed when I click on their user icon in the Kanban board. 

Is this possible?

 

2 answers

1 vote
Joe Pitt Community Leader Jan 24, 2020

The short answer is no.  JIRA only allows one assignee. One workaround is to create a user picker for the additional users. In my experience if more than one person needs to work on an issue it can be divided into subtasks assigned to them works well. That way if they look for tasks assigned to them it shows up. 

Jack Community Leader Jan 24, 2020

And then you can use quick filters for secondary and tertiary assignees but that isn’t very scalable.

A group-picker can also be useful to indicate other people to talk to.

But multiple assignees does not work in real life.  You will always have "I thought someone else was doing it" and makes it impossible to track progress or work.

If we genuinely have multiple assignees, we tend to use sub-tasks for them.

To generally track who has contributed to something, based on historical Assignee activity, we created a multi-user field called Contributors, and used Automation for Jira to automatically add a user to the Contributors field whenever an Assignee is set. We tend to change Assignee on an issue when something is being reviewed (reviewer = Assignee at that stage) and when something is being tested by a QA/engineer (tester = Assignee at the QA status).

At the end of the issue's lifespan we can see who was actively involved from the contributors field.

Suggest an answer

Log in or Sign up to answer
TAGS

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you