nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

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

Aurélie Pilette_1tqqnx

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

Accepted answers

All comments

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_1tqqnx

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_1tqqnx

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 ?

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

cloud

jira-cloud

workflow

editor