Hello community,
Is there any way that we can delay the transition 5 to 10 sec, after clicking the transition.
Ex: When i do the transition from Todo to Draft, When i click Draft button it should delay 5 sec and then it should move to draft state.
Or
Do we have any option to delay the jira post function to run. We have postfuntion to run as soon as ticket moved to Draft state.
Either my post function to run after 10 sec of ticket moved to draft state or when i do the transition to draft state it should delay 10 sec.
Thanks
We are using jira cloud
Hi @PLaksh11
Thanks for the question.
As I know, natively, Jira Cloud cannot delay a workflow transition or a post-function.
I think you can instead use an Automation rule, for that purpose.
Also, I found this article in the JMWE app, which provides an example for a delayed post-function.
https://appfire.atlassian.net/wiki/spaces/JMWEC/pages/466322009/Delayed+execution
That post-function delay is provided by the JMWE app, so would need to have that app installed to use the delay.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @PLaksh11
Premium and Enterprise licenses provide a delay action in automations, so if you're on either of those licenses you can do the following:
Add in a new status between ToDo and Draft e.g.:
Make sure that the transition from Initial Review to Draft can only be done by automation
You could then set up an automation for a status update to 'Initial Review' with a delay which then transitions the work item to Draft, e.g.:
Alternatively you can do as @PLaksh11 suggests, and use a manual automation to move the work item to draft, in this case you would not need the extra status, but the transition would have to be run from the automation menu instead, again just make sure that the transition to Draft can only be done by automation:
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @PLaksh11 - The delay option within an automation rule linked to a hidden transition should be a quick solution.
Also, if this is a critical requirement, you may also look into building a custom app using Atlassian Forge framework - to introduce delayed execution logic.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.