New issue status in Next-gen project

[Brian Silva]

Hello!

I created a new to-do status called "Needs Evaluation", which has a transition from the built-in "To Do" status.

I'd still like the initial creation status to be "To Do". However, after returning to the workflow editor, it has decided to set my "Needs Evaluation" status as the initial status. If I try to change it back to the built-in "To Do" status, I get an error that "A newly created issue must start in the To-do status category."

Is there a way to make this happen? It seems like a bug.

[Jack Brickey]

The workflow editor is still WIP. I played w/ this and found you cannot move the create transition. I even tried changing the current initial status from To Do category to In Progress to see if I could then move the transition to a new To Do status but no luck.

There are a number of limitations where you can get into trouble like you have found. Here are a couple of open issues I found in JAC that are being worked - JSWCLOUD-17434 , JSWCLOUD-17497 . You might wish to review/watch/vote. You may also reach out to Support to see if there is any workaround/recovery. Finally, I would recommend creating a test NG project so you can play w/ changes in workflow prior to pushing to production.

[Brian Silva]

Thanks for checking it out, Jack, and thanks for the issue links! I've voted and am watching now -- looking forward to the next rollouts!

[Greg Walsh]

Hey Jack, I don't see any tickets relating to this specific bug so it's hard to know if the Atlassian dev team is aware of the issue