Why can't we have multiple assignees on a ticket?

[Mick C]

I'm asking this as a question and not a discussion because I want an answer.

Jira is a big complicated app and sometimes in a big corporation with many stakeholders it can be a tough sell.

What doesn't help is when there are arbitrary decisions made like "a task can only have one assignee". I've worked in multiple software companies and EVERYWHERE that I have used Jira the same problem is always floated.

"Why can't I assign two people to this ticket?"

When I explain that you just can't, and I don't know why then the eye-rolling ensues.

The amount of discussion around this one particular feature on this forum and on the internet as a whole is very indicative of the the fact that this is a hot topic.

So here's my own personal question:

Why is this arbitrarily locked down when the number of labels a ticket can have isn't? The number of child tasks that can be assigned isn't etc etc. Why does Atlassian force the law on this one particular feature but give maximum flexibility everywhere else?

Surely if in my organisation I see fit to assign a ticket to two people (or three or four) then I should be able to do that.

If you're one of the militant "one assignee per ticket" people then that's fine. You do you. Everyone else should have the choice.

[somethingblue · Accepted solution]

Hi Carlos,

I found a bug ticket which describes this situation at JSWSERVER-12880: Version's date is shown one day off on agile board>versions:

1. Go to project Overview>Versions (or project Administration>Versions) and observe a release date for certain version (in my example on the screenshot1.jpg it will be 22/Jan/15)
2. Go to appropriate Agile board where this release will be represented, expand versions from the left, and observe the date of the same release
—
Release date will be shown one day back (in my example on the second screenshot2.jpg it will be Release Date: 21/Jan/15)

At the present the workaround is as follows:

Ensure that both "Default user time zone" and JVM timezone match

If you agree this is in fact the same issue please vote on JSWSERVER-12880 to add impact and be notified of any changes. 

Cheers,

Branden

[Carlos Henriques]

Thank you Branden.

I believe it is the same problem and already voted for the fix.

Thank you.

[somethingblue]

Thanks for letting us know Carlos and keep watching JSWSERVER-12880 for any updates!