Hi All, I am trying to achieve the following When an Issue transitions from status X to status Y an automation rule kicks in and does the following: * Send a web request * Start a countdown timer for N mins * Once the timer expires * Send a web request * Transition Issue from status Y to status Z I am able to implement steps 1, 4 & 5, looking for advise on how to implement steps 2 & 3 Thank you Vish

Hi @Vish Reddy {Revyz} What problem are you trying to solve by doing this? Specifically what is the purpose of the timer? Knowing that may help the community to offer suggestions. Thanks! Until we know that... There is nothing built into rules to do this. A couple of possible work-arounds could be: * With a timer* split this rule in half, use an external service with a timer provide a webhook that can be listened for to trigger the second rule, and then perform to the second web request and issue transition * Without a timer (event-driven processing)* split the rule, ignoring the timer and using event-driven processing, and have the first web request call back to the Jira REST API functions to update an issue...leading to triggering the second rule with the remaining steps Kind regards, Bill

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; } } }

Jira Automation: Timed Automated Actions

Vish Reddy {Revyz}

Hi All,

I am trying to achieve the following

When an Issue transitions from status X to status Y an automation rule kicks in and does the following:

Send a web request
Start a countdown timer for N mins
Once the timer expires
Send a web request
Transition Issue from status Y to status Z

I am able to implement steps 1, 4 & 5, looking for advise on how to implement steps 2 & 3

Thank you

Vish

Accepted answers

Bill Sheboy

Hi @Vish Reddy {Revyz}

What problem are you trying to solve by doing this? Specifically what is the purpose of the timer? Knowing that may help the community to offer suggestions. Thanks!

Until we know that...

There is nothing built into rules to do this. A couple of possible work-arounds could be:

With a timer
- split this rule in half, use an external service with a timer provide a webhook that can be listened for to trigger the second rule, and then perform to the second web request and issue transition
Without a timer (event-driven processing)
- split the rule, ignoring the timer and using event-driven processing, and have the first web request call back to the Jira REST API functions to update an issue...leading to triggering the second rule with the remaining steps

Kind regards,
Bill

All comments

Bill Sheboy

Hi @Vish Reddy {Revyz}

What problem are you trying to solve by doing this? Specifically what is the purpose of the timer? Knowing that may help the community to offer suggestions. Thanks!

Until we know that...

There is nothing built into rules to do this. A couple of possible work-arounds could be:

With a timer
- split this rule in half, use an external service with a timer provide a webhook that can be listened for to trigger the second rule, and then perform to the second web request and issue transition
Without a timer (event-driven processing)
- split the rule, ignoring the timer and using event-driven processing, and have the first web request call back to the Jira REST API functions to update an issue...leading to triggering the second rule with the remaining steps

Kind regards,
Bill

Vish Reddy {Revyz}

Thank you @Bill Sheboy

Appreciate your quick response.

Here is what I am trying to do:

I am putting together process where in a support engineer on our team gets access to a restricted system for a specific amount of time once his / her access approved via a Jira ticket.

Support engineer creates a ticket requesting access to the restricted system
Approver approves the request and transitions the ticket to approved status
Jira then triggers a web request to the restricted system to provide access
After N minutes Jira then triggers a second web request to the restricted system to remove access

Thank you again for your suggestions!

Bill Sheboy

Ah...in that case perhaps another approach would be to set a custom field (or entity property) to a target timeframe to suspend access, and then use a scheduled trigger rule to poll for when to remove the access, based on that set custom field (or entity property).

Mikael Sandberg

Just to add to Bill's excellent suggestion. You could utilize SLA for it as well that starts when the request is approved and then use the SLA threshold breach trigger to send the web request to remove the access.

Welcome!

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

Quick Links

Find more posts tagged with

jira-cloud

automation