Why can't you add more than one assignee to an issue?


2 answers

Because Atlassian coded JIRA that way and more than one owner would not be Agile!

JIRA was designed that way. You can configure JIRA in a number of ways using groups combined with setting notifications to ensure a group of people are emailed at any stage in an issue's workflow.

However, JIRA (and any workflow or process engine) works best when you have one person assigned an issue so that you know who is ultimately responsible for it until it goes to the next step in the process.

Perhaps you can explain a little more about what you're trying to achieve?

I was just trying to use the Issues feature to do some big-picture planning. We have two backend engineers and me and the other were going to get together to transition our project to Django 1.8, since we've both had toruble doing it along. I wanted to mark this down but couldn't, and it's not really something that can be broken down into more Agile parts, so I just wanted to know why I couldn't assign a list of ppl to do something

Suggest an answer

Log in or Join to answer
Community showcase
Piotr Plewa
Published Dec 27, 2017 in Bitbucket

Recipe: Deploying AWS Lambda functions with Bitbucket Pipelines

Bitbucket Pipelines helps me manage and automate a number of serverless deployments to AWS Lambda and this is how I do it. I'm building Node.js Lambda functions using node-lambda&nbsp...

681 views 0 4
Read article

Atlassian User Groups

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

Find a group

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

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you
Atlassian Team Tour

Join us on the Team Tour

We're bringing product updates and pro tips on teamwork to ten cities around the world.

Save your spot