When in projects and creating a list of tasks, how do I assign more than one assignee to each task?
Hi @Robert Rudolph ,
As per my knowledge, Out of the box, Jira doesn't support multiple assignee concept. At any point of time, any task can be assigned to single user.
If you want to assign an task to multiple users, you can split it in to subtask and assign them to different users.
As @Sreenivasaraju P said you can't. Another option if you want to assign it to a group is to create a distribution list in email, create a user with that email, and assign that user. The user will then need to be in the assignable user list in the project.
You do not. The assignee field in Jira is intended to show you who the person currently responsible for getting the issue done is. That should only ever be a single person - in real life, you will find your projects fail if you have more than one assignee. Half of my contracts as a Jira admin started with "we need to tidy up our Jira to make it usable", and every single one had, as a part of it "get rid of our botched multiple assignee process/fields".
But, there is nothing wrong with logging many people for secondary responsibilty - if the assignee is not around (leaves, takes a holiday, changes teams etc), and you have a lot of options around it.
There are other options and you can get clever with the ones above and others. What you need to do next is look at how your people are working, specifically how they are handling "who is doing this", so you can map it on to one of the options.
You cannot add multiple assignees to a ticket. Instead you can create new User picker(single user) or User picker(multiple user) field and name like Developers, QA team etc add them to the project screens.
Also if you want to assign ticket to team/groups, follow below steps.
create a group picker(single group) custom field.
1. Identify users for each group and create groups for them. (Example: IT Hardware group for Hardware related issues and add users who deal with those tickets)Go to Admin -->User Management --> groups --> Create groups
2. Create group picker(single group) custom field and name like "Assignee group".3. Add the custom field for related project issue type screens where required.4. Create queues based on the "Assignee group" JQL condition and share the queue/filter link with respective teams.Example: Assignee group = "IT Hardware group" and status != ResolvedEven you can create automation rules to auto-update assignee group field based on the text link the summary/description fields. Example: summary ~hardware
If you create a burndown chart for stories will the assignee group show up in the burndown or will it still be listing the single assignee? Ideally for my scenario, id like to be able to produce a burndown for the assignee group.
Burndown is not done for individuals, it is done for the team executing the sprint.
HI, @Robert Rudolph !
As an alternative, you can check out 2 add-ons, developed by my team.
Jira only supports one assignee per issue by default, but if you need multiple people working on the same task, you can try this app: GPT Multiple Assignees for Jira. It lets you assign several users at once and helps cross-functional teams avoid bottlenecks.
"That should only ever be a single person - in real life, you will find your projects fail if you have more than one assignee."You are painting with a broad brush. Certain industries like design have many collaborative efforts where two or more people can tackle the same file at once in realtime. Now with development I can understand your point.
This should be up to the company to decide.
.
@Mary from Planyway
This topic is now closed as the discussion has become outdated. If you have more questions or want to continue the conversation, feel free to start a new topic. For more details on why we close older threads, check out our Rules of engagement - Atlassian Community .
Thank you for your understanding!
It looks like you're new here. Sign in or register to get started.
