Create an automation rule for due date and start date

[Silvia Fattori]

Is it possible to create an automation rule that assigns to the due date of a story the due date valor most future present among all the present issues of that project?

Then I would like to do the same thing with the start date, taking the most recent date present.

For example

Thank you 

[Bill Sheboy]

Hi @Silvia Fattori  -- Welcome to the Atlassian Community!

You probably can do that using the list and math functions.  It may require the use of a temp variable (create variable or custom field) to retain the value.

And, the techniques would be different if you are using sub-tasks versus the other issue types, as sub-tasks are already a list and you could find the maximum date immediately: {{issue.subtasks.Due date.max}}

What have you tried thus far to do this?

Best regards,

Bill

[Silvia Fattori]

Thank you for your quick response.

My search for two max dates should be done on all types of issues in the project (so not only subtask). I would need to know how to put it in the automations.

[Bill Sheboy]

Hi @Silvia Fattori 

For more details, here is an example to set the Due Date for a specific Epic...

• Trigger: Due Date is changed
• Condition: related issue, check this issue has an Epic
• Branch: on the Epic (Parent) of this issue
  • Condition: if the story Due Date {{triggerIssue.dueDate}} is greater than the parent Epic Due Date {{issue.dueDate}}
    • Action: set the epic's Due Date to the value from the triggerIssue Due Date

If you wanted to check a Due Date spanning all issues in a project you could use a created variable and iterate using a different branch JQL filter...but, you will need to pick an issue to store the maximum value into, such as a specific Epic.

__Bill

[David Ashlock]

Hi @Silvia Fattori , this can be done with the {{lookupissues.Due date.max}} and {{lookupissues.Start date.min}} smart value functions.  See attached.

[Bill Sheboy]

Yes, indeed.  Those fields did not exist in Lookup Issues when this question was first posted, so the solution is now easier to implement.

[David Ashlock]

Haha!  I figured so or you would have suggested it.

@Bill Sheboy i was actually looking for a way to specifically ask you if you can do the following:

{{lookupissues.Due date.max.diff(issue.Start date).businessDays}}

I believe you can, but I'm having an issue getting the max due date to come through (separate issue).

[Bill Sheboy]

Hi @David Ashlock 

Yup, and I believe you just have a couple of smart value capitalization and spacing issues...this worked for me:

{{lookupIssues.duedate.max.diff(issue.Start date).businessDays}}

Kind regards,
Bill

[David Ashlock]

@Bill Sheboy 

Thank you!

One follow-up question -- if your lookupIssues only has a single value, does the .max function still work?  When I removed that, everything worked -- note that there is only one issue blocking my test issue, but there could be more in the future.

[David Ashlock]

@Bill Sheboy 

I think you can ignore this question -- the capitalization and space issues seem to have fixed that problem as well -- never realized it was going to be that picky!

Thanks again!