Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,455,922
Community Members
 
Community Events
176
Community Groups

Can we add a time interval - that we want the next step to happen after a certain no. of days?

As shown in the screen shot example below, want I want is, I want to add a time interval to the automation rule, wherein I want a certain step to happen after (lets say 5 days or 7 days (a week later)).

So, in this rule, I filter out a list of issues my my criteria and issue type is equal to 'Story' and then send an email that these stories will be deleted, but then I want that there should a time gap when the next step happens (in this case, those user stories will get deleted)

JIRA AUTOMATION TIME INTERVAL.png

1 answer

0 votes

Hi @ANISH TANEJA -- Welcome to the Atlassian Community!

Automation rules do not work that way, with the ability to pause execution for an indefinite period of time.

Instead consider having two rules:

  1. One rule detects the pending action, sends a notification for the pending action
  2. Another rule which detects the condition (including that the time period has expired) and then perform the action

A variation of this approach is to have rule #1 mark issues somehow (e.g. some field change) so that they are not picked up to send more notifications and can be later picked up by rule #2, as needed.

Kind regards,
Bill

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events