Using smart values in the delay action

[Andrey Kiyanovskiy]

Hi team,

it would be good to have support for smart values in the Delay action.

My use case. In a FOR loop, I'm creating and linking child tickets. But because all branches are run in parallel, the order of the child tickets is mixed up. I'd like to add a delay 1,2,3... seconds in each branch what should resolve this issue. Thus, the next branch will take +1 second and child issues will be created in the original order.

Best,
Andrey.

[Toalha.Tosrif]

Hi,

I was also having the same thoughts only to find out we cant use smart value in Delay. Could have probably solved my issue with the order.

[Andrey Kiyanovskiy]

I don't really need a solution, I can copy actions as a workaround. And I'm pretty sure this approach will work. If not with 1 second distance, but with 2 or more it will.

[Bill Sheboy]

Hi @Andrey Kiyanovskiy 

Having a parameter for the Delay() action may not help with your described scenario.  With the parallel and asynchronous nature of branches which could be on more than one thing, I suggest there is no way to accurately forecast how long the branch will run.

If you describe the problem you are trying to solve (i.e., the "why") and show your current rule, the community may be able to suggest alternatives to meet the need.

Until we see that information, the only current method with Jira Automation to add issues in a specific order is one-by-one (sequentially without branching).

Kind regards,
Bill