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.

[Nic Brough -Adaptavist-]

Check that you have "transition issue" permission in the project's permission scheme

Open up the workflow in edit mode and check the "conditions" on the transition from identifié" to "annulée - do you match all of those?

[Manuel Allamellou]

there is no particular permission scheme on this project and i have the profile administrator on Jira and it works on other issues on the same project.

[RianS]

Sorry, this was a duplicate answer. Removed it.