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

[Mark McCormack (Adaptavist)]

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?

[bkoatz]

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

[Randall Fisher]

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