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

Question

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 · Answer

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.

Renata Klimiato · Answer

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?

Renata Klimiato · Answer

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.