Do "all" transitions have a performance impact?

[Steve Zajaczkowski]

Within our organization, we are being told that "all" transitions in workflows have a significant performance impact due to additional background checks that Jira does every time you transition from one status to another.  As such, they are not allowing "all" transitions, which inevitably leads to issues using kanban boards (can't move from one column to another because the workflow doesn't allow that transition).

To meet our need to allow every status to transition to another status, they are manually building every possible transition from each status to every other status. 

Can anybody confirm the performance issues they are concerned about with all transitions?

[Nic Brough -Adaptavist-]

No.

"All" transitions have only a negligible difference in impact than other shared or single transitions.  Technically, there's some overhead, but in some cases, "All" transitions are better in performance terms than other types. 

In real life, the differences are so small, the time for an admin to replace an "all" with a set of single transitions is going to burn more CPU and human time than leaving an "all" in place and living with the performance differences for a decade or so.