Have automation rule run specific transition

[Benjamin Peikes]

Trying to migrate one of our old legacy automation rules to the new automation system. One of our old rules has a "Then do this..." which is to transition the issue. The problem is in the old automation, you got to specify the actual transition name, but in the new automation, the only thing I can see is the ability to set the new status.

What does automation do if there are multiple transition types for the same resulting state?
Here is a concrete example:
ServiceDesk has a workflow which will take a resolved issue, and switch it to "Waiting for support". This transition is called, "Reopen By Customer", and causes a couple of other things to happen. The final state though is "Waiting for Support".

In the old rules the "then" is
Transition issue: "Reopen By Customer"

but in the new automation, you only have the ability to:
Transition issue:  Destination status: "Waiting for Support"

Is there any way to run a specific transition? for instance what if there are 3 different workflow paths from status A -> status B. If you have your Automation rule set the status to B, which transition gets run?

[John Wilson]

We've created many standardized schemes as well. To keep them safe, we have disallowed anyone except jira admins from creating next-gen projects. We might open them up to teams that are truly independent, but in general, we need to keep any team for which we need standard reporting metrics in our standard schemes.

[Jeanne Howe]

We have also disallowed the creation of next-gen projects, for those same reasons.

Leaves me curious to understand when, and why a next-gen project would be used.