Thank you @Luke Ellery I am now able to see the "edit setting" option on the top right under General Configurations. I kept looking on the side panel only.
@Luke ElleryIn Workflows, would it be possible to connect the 'Create' node to multiple statuses instead of just one? We would like to allow users to immediately transition issues to some statuses, like 'Refining' instead of 'Backlog' (our initial status). However, after it has gone into Progress we wouldn't want it to always be possible to transition it back to 'Refining'. Therefore the solution of adding an 'All' transition to 'Refining' is not workable. If we would be able to add a separate 'Create' transition for 'Refining' it would correctly model the desired workflow.
Atlassian Team members are employees working across the company in a wide variety of roles.
March 17, 2024 edited
@Matthias BlomTo clarify, are you asking if you are able to have multiple initial statuses, or is it about linking the initial status to multiple other statuses?
Hello @Luke Ellery , we are currently evaluating a trial of Jira Cloud for our organization, and I'm trying to keep it inherently simple for my teams. It seems like the only way to make this functionality useful is to allow every transition in the workflow to go to every status, and then set conditions on each of those transitions to identify specifically when we would want to show those statuses, correct?
We're trying to basically say: On Create, you can submit the Task to either Backlog, or Open. but once it is in the workflow, I do not want the Task to be able to go to those statuses. So I have to set a condition for the "All Statuses to Open" transition, which in the new workflow editor I must do one at a time (whereas in previous versions of Jira you could set condition which included multiple statuses)
I'm wondering why is the process to effectively use this feature to:
Enable ALL transitions to go to the singular (1) status I want to offer in addition to the default Create one (Backlog)
Restrict when that transition will show, one by one for each and every status in the workflow (for us it will always be ~4+)
I have to add (+) a new condition for every status where I don't want that to be seen, as the ability to add a condition against multiple statuses no longer exists in Jira Cloud.
The Status field shows on Create no matter what, even if it is rendered (what I would call) useless to the user - they can't change it, but they CAN interact with it. The message "There are no other statuses for you to use" is not helpful, or configurable.
My suggestion, if I could make one, would be to simply enable Workflows to have 2 Create transitions. I'd rather configure 2 separate create transitions that will drive value than configure several to reduce confusion.
Of course, most workflows would not want to allow transitioning back to one of the initial statuses from _any_ status! Multiple people are saying this here. So why not make the feature work as described in the actual post, e.g. display the initial status _and_ any other status that can be transitioned to from that initial status without restriction? And, why not additionally allow having multiple Create transitions? Either of these things would solve the problem that me and many other people are having, while also complementing each other: we would be able to pick from any of the now multiple available initial statuses, as well as from any status that can be transitioned to from those initial statuses without restriction (which makes sense, because if there's no restriction then it just saves a click, which is exactly what this feature is about).
60 comments