Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
badges earned

Your Points Tracker
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Is it possible to run automation on the due date based off how long an Issues is blocked?

I would like to create an automation that will extend a due date to allow for the amount of time an Issue was blocked. Is there a way to do this without having to use an add on?

1 answer

1 accepted

2 votes
Answer accepted

Hi @Colin Hunt -- Welcome to the Atlassian Community!

Yes, I expect so using the built-in Automation for Jira (A4J) rules.  How do you:

  • mark issues as "blocked",
  • know their "time blocked" or "start of blocked time", and
  • know the "baseline due date"?

With that information, there are a couple of solution approaches:

  1. Add one automation rule, running on a daily schedule, that finds blocked issues with due dates and increases the due date by one business day each time it runs
  2. Add three automation rules:
    • When the due date is manually set, save the value as the "baseline due date" in a custom field
    • When an issue is marked as blocked (let's assume with Flag), save the value of "start blocked date/time" in a custom field
    • And a third automation rule running on a schedule to calculate blocked time ("start of blocked date/time" versus {{now}} ) and update due date relative to "baseline due date"

Approach (1) is simple, and approach (2) is more complicated and a bit brittle, while preserving the original due date and allowing reporting on "blocked time".

To learn more about A4J, please look here:

Best regards,


@Bill Sheboy option 1 worked perfectly, thank  you!

Like Bill Sheboy likes this

Suggest an answer

Log in or Sign up to answer

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you