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

Automation - finding a date and editing it

Rhys Hill_newcov

I would like to create an automation that is triggered when a date is edited (that but is easy) then take the date of the trigger and applies a formula to it. For instance

Due date set

find child issues

set due date of child issues to “trigger due date - 3 days”

obviously I can copy a date or create a date but it’s the copy date and amend it that I’m looking for

Accepted answers

Bill Sheboy

Hi @Rhys Hill

Yes, that sounds possible. Maybe try this:

Trigger is due date change
Probable should add a condition to ensure the source was an edit, and to confirm your issue type
Add a branch to iterate over the children, either as sub-tasks or using JQL
Set the due date as you note

Please see this reference for date manipulation: https://support.atlassian.com/jira-software-cloud/docs/use-smart-values-to-manipulate-and-format-dates/

Best regards,

Bill

All comments

Bill Sheboy

Hi @Rhys Hill

Yes, that sounds possible. Maybe try this:

Trigger is due date change
Probable should add a condition to ensure the source was an edit, and to confirm your issue type
Add a branch to iterate over the children, either as sub-tasks or using JQL
Set the due date as you note

Please see this reference for date manipulation: https://support.atlassian.com/jira-software-cloud/docs/use-smart-values-to-manipulate-and-format-dates/

Best regards,

Bill

Rhys Hill_newcov

I have managed this now with some perseverance but there may be a more efferent way.

I had a hard time getting sub tasks to Update I could easily get the child issues of an epic to update but it would stop there so I changed the automation for the creation of tasks and sub tasks to also link each one to the epic (sounds odd as by being children of the epic and then tasks they should be defined as linked but oh well)

now that ALL issues for that epic are “linked” this simple automation is working but I would welcome a more efficient approach perhaps with a JQL if you have one?

Rhys Hill_newcov

Oh and this is now working for me to solve the other part of my question

Bill Sheboy

Hi @Rhys Hill

I am glad that you got this working. Unfortunately, you cannot nest branches in automation rules or store temporary variables, so your approach of cascading the Epic Link works...

The other approach I have used is multiple rules to update the different levels, using a common triggering event (such as a specific comment or custom field value change).

If you wish, please remember to mark this as answered so others can find the solution.

Thanks!

Welcome!

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

Quick Links

Find more posts tagged with

cloud

jira-software

automation