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

How can i add multiple users to one issue

Can i assign two people to one issue?

3 answers

1 accepted

2 votes
Answer accepted

No.  The assignee must be a single person, otherwise you run into the unmitigated disaster that in real life, someone will say "I thought someone else was responsible.  Don't ever allow that to happen

There is however, no harm in indicating secondary people who are involved, can take over if the assignee needs to change, have an interest, etc.  You can use other fields for this - some people use the built-in watchers, the rest tend to add custom fields - a single or multiple user picker, or a group-picker if you want to name an associated team.

0 votes
branco I'm New Here Jan 26, 2021

You can't.

I've checked with my manager and the best and easy way is assign to a person and the make a comment and select the other ones you want to watch it and relate to the story/issue.

@Nic Broughwasn't there an effort to use a custom user field to have a co-developer setup where two people were working on the same project at the same time? I think it may have fallen out of favor perhaps for the same reason.

I agree with Nic though on the potential pitfall. Why not use a subtask to add people to the issue that they are both working on? I've done that where I have three technicians building different parts of the same main assembly. One of them is responsible for the main final assembly and the subtasks (or linked tasks) are farmed out to others and block the main task from completing. It gives the main task owner some incentive to ask for help on his roadblocks or to negotiate a solution with the roadblock.

You can do that, but the other custom field won't have the same attributes as the assignee field, so it really remains a second class  thing.  It is something I meant by "indicating secondary people who are involved"

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Published in Agile

Applying Trello magic to Jira projects

Applying Trello magic to Jira projects Introduction Lately, I have been writing a lot about Release Management (e.g. a few of my previous articles-   One,   Two   and   Three). ...

217 views 6 8
Read article

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