With the new editor of worklow, there is no condition by field

[Aurélie Pilette]

Hello,

With the old workflow, we had some rules like : 

- We can't transite from one status to another one if one field is empty

- We can't transite from one status to another one if all sub task are not closed

- We have a trigger ==> create a PR

it worked fine.

With the new workflow editor, this rule won't work and it is blocker for us. is there an issue to have this condition with the new workflow editor ?

Thanks

[John Funk]

Hi Aurélie,

You should be able to switch to the Old Editor when editing the Workflow if it is a Company-managed project. If it is a Team-managed project, can you provide more information on what is not working. And please share some screenshots of your rule. 

[Aurélie Pilette]

Hello,

I can switch to the old editor. But I suppose that the old editor will be disappear ?

Below, you will see examples that rules which doesn't work with the new editor

[John Funk]

Granted it will go away at some point, but Atlassian knows that they can't lose functionality in that process. So the new will have to be able to do everything the old does before it is completely cut off. 

[Aurélie Pilette]

Exactly, but for the moment, this functionality is not present even if you can say to me how.

That's why I open this question, how to be sure that it will be present and when ?

[John Funk]

I don't know the answer to that. Just that there is another option to accomplish what you want right now. 

[Aurélie Pilette]

What is the option to make what Iwant ?

Automation rule ?

if that, how to configure an automation rule who blocks the transition if one field has not the good value ?

[John Funk]

You use the old workflow editor.

[Aurélie Pilette]

yes, but it is not a good issue because when it disappear, i will loose all  my rules

[John Funk]

No you will not lose your rules - not sure who has told you that, but it is not true.