How can I reusing the "Create" transition in my workflow?

[Mary Norris]

Goal = to allow my developers to create issues with a status of "Backlog" or "Alpha" 

Note: Alpha is the first In Progress status of the workflow

Currently, when I or my team members create a new issue, it can only be created with a status of Backlog. When I try to reuse the Create transition for the Alpha status (see workflow diagram) Jira does not allow it to be attached to more than one status. I know you can have "allow all statuses to transition to this one" but that contradicts the workflow I am trying to instill. 

Does anyone have any suggestions for how I can select a status of Backlog OR Alpha (see workflow diagram) at issue creation? 

Thank you!

[Alex Ortiz]

@Mary Norris - Welcome to the Atlassian Community!!!!!!

The create transition can only go to one status. Jira wont allow us to make it go to two different statuses right out of the gate.

With that said, my recommendation would be to create an automation rule with the following configuration:

Trigger: Issue Created

OPTIONALLY: -Add a condition IF when you want an issue to actually go to Alpha status

Action: Transition Issue

[Kian Stack Mumo Systems]

@Mary Norris

You can't do that without a global transition.

If you'd like, you could set up an automation to automatically transition the issue to Alpha based on specific criteria.

Thanks,

Kian

[Trudy Claspill]

Adding a clarifying note:

When you are in the Create Issue dialog, where it shows the pull down field for Status and you currently see Backlog, that field will list all status in the workflow (for that issue type) that have an incoming Global Transition. An incoming Global Transition means that an issue in any status in that workflow can be transitioned to the destination status. A Global Transition looks like this:

Note that the transition also cannot have any Conditions or Validators as part of its configuration.

On a side note I see that you have defined your "Ready for Beta" status as part of the "Done" Status Category. It is a bit unusual to have an issue transition from an "In Progess" type of status to a "Done" type of status, then back to an "In Progress" type of status, and then again to a "Done" type of status. Is there a reason you made "Ready for Beta" a "done" type of status?