Is there a way to delay actions after issue creation as Jira works slower than the rule runs...?

[Renata Klimiato]

Do you know how much time the delay takes due to "re-fetch action" ? I was also using it when tried to automate creation of two related issues in a row WHEN issue is created, however it feels like the system skips half of my automation because initial ticket creation is not finished. It just skips those steps in red.. Is there some action with possibility to delay other steps by 5-10sec?

[Bill Sheboy]

Hi @Renata Klimiato -- Welcome to the Atlassian Community!

Although there are timing / racetrack processing concerns in automation rules, I recommend only introducing intentional delays when necessary.  Let's look at the specifics of your rule to understand those...

The Issue Created trigger often fires before an issue is fully ready for use by a rule.  This can cause errors and unusual rule behavior.  The mitigation for that is to always add the Re-fetch Issue action after the Issue Created trigger.  For this scenario, that will slow the rule down by about one second, reloading the trigger issue data before the rule proceeds.

Next, your rule is creating issues and apparently trying to link them to the trigger issue.  To do that, add the issue linking when the issue is created in the Create Issue action, selecting the trigger issue.

Finally, you also appear to be trying to link the newly created issues to each other.  For example, to link to the previous, most recently created issue.  There are several ways to do that, including when the issue is created, add the link at the same time by selecting "Most recently created work item".

Kind regards,
Bill

[Renata Klimiato]

Hello, Bill! Thank you for your reply!

To be honest, I think I did everything you wrote... I have re-fetch added after Console project ticket creation, but it's linking to trigger issue did not happen. And I even see in backlog, that this issue creation is slower than others and while Console ticket is created - UX ticket is already in the board. Automation does not wait until console ticket is created and just skips actions (like linking) related to that slow ticket... and re-fetch action does not help. I even had it added 5 times after Trigger issue and Console issue creations, however - it still does not help. 

[Bill Sheboy]

As written, your rule is creating issues and linking them in two different operations.  Did you try linking the issue when it was created, rather than linking afterwards?

What are the types of product and project for each project involved:

• product: Jira, JSM, etc.
• project: Work Management, Software, JPD, etc.
• type: company-managed or team-managed

Please post an image of the audit log details for a rule execution showing the symptoms you describe.  Remember to expand all of the areas at the right side of the log so the details are shown.

[Stephen_Lugton]

Hi @Renata Klimiato 

There is a 'Delay' action that you can use to achieve this:

[Renata Klimiato]

Hello, Stephen, thanks for reply. 

Unfortunately seems like Delay action is not available in all Jira versions. We have standart cloud plan (not premium one) and this is not here . Could you share what Jira plan are you using?