How can I select from multiple statuses when creating issue?

[Chris O_Donnell]

I have a company managed Jira project and when creating an issue, I would like to be able to set the status to "Backlog" or "Open".

I am aware that this can be achieved by setting "Allow all statuses to transition to this one" on one of those statuses and have the Create transition point to other. However this creates the problem of all other statuses being able to transition to the all one and I don't want this.

I thought it might be possible to set a Condition on the All transition to prevent issues in other statuses from using it, however it seems that any condition that I set on that transition prevents it from appearing in the create issue status list, regardless of what that condition is. Here is a screenshot of the relevant part of my workflow:

With this condition set on the All transition:

Note: this is just a dummy condition to show the effect of a condition on the create issue screen.

This allows me to transition the status of an existing issue:

But does not add Backlog to the status list of the create issue screen:

Deleting that condition does add Backlog to the status list of the create issue screen:

I feel like this must be a bug but perhaps is as designed? Any help would be greatly appreciated, thanks.

[Trudy Claspill · Accepted solution]

Hello @Chris O_Donnell 

Welcome to the Atlassian community.

As per the article that announced the change...

https://community.atlassian.com/t5/Jira-Software-articles/Set-the-status-of-an-issue-while-creating-it/ba-p/2206634

...it is by design that a Global transition that has Conditions will block the status from being available in the Create Issue dialog.

An alternative implementation would be to set another field (perhaps a special Labels value) that would work with an Automation Rule to automatically transition the issue from the Open status to the Backlog status.

Note that there are usage limits on Automation Rules. For a Free subscription you can have only 100 automation rule executions per month. For details on what constitutes an "execution" and how usage is calculated, refer to this page and the additional pages it references.

https://www.atlassian.com/blog/announcements/cloud-automation-packaging-update