Automation rule for different issues due date

[Allah-asra_ Yankal]

Hello!

Newbie here! I would like to create an automation rule that will calculate the due date of different issues (we should therefore have multiple different due dates) based on a due date initially entered at the Epic level. 

[Bill Sheboy]

Hi @Allah-asra_ Yankal -- Welcome to the Atlassian Community!

Do you have a rule you have started writing?

If so, context is important for the community to help.  Please post the following:

• what type of project is this: company-managed, team-managed, JPD, etc.
• an image of your complete automation rule in a single image for continuity
• images of any relevant actions / conditions / branches
• an image of the audit log details showing the rule execution
• explain what is not working as expected and why you believe that to be the case

Until we see those...

How do you decide which Due Dates to use for the different work items?  Knowing that will help understand what the rule needs to be successful.

Kind regards,
Bill

[Allah-asra_ Yankal]

@Bill Sheboy  thanks for pointing out what is missing from my post. 

The project is team-managed, it will be tracking different fulfillment activities. The different activities have been defined and linked to the Epic which serves as template. Every time an event triggers assessment, a team member should be able to create an epic by cloning the template. 

The assessment takes 180 days in total. Each task has a fix SLO. Picture 1 is a screenshot of the first 3 tasks ( there are about 16 tasks)

Looking Picture 1 , the first task RC2 - Report IS has a max SLO of 90 days. If the assessment due date is Feb 15,2026 - I would like to Due Date for RC2 to auto-populate to  November 17, 2025 as soon as the Feb 15 date is entered.

The RC1-Report IS task has a max SLO of 100 days - so its due date should auto-populate to November 27, 2025

The RC4- IMA with a max SLO of 120 days , should have a due date of December 17,2025.

I have a rule I started writing, but honestly I am not sure of what I am doing. I tried to leverage information I could find out there, but I haven't gotten to far. 

The second screenshot is what I have started

TY

[Bill Sheboy]

Thanks for that information, as it seems to confirm this scenario is solvable...(as oppose to scenarios with cascading dependencies :^)

The key is using the date / time functions to increment the dates in the child work items, and where the SLO values are stored.

If they are stored with each child work item, and the values are numbers, the rule could be something like this, assuming the trigger issue is the Epic:

• trigger: field value changes for Due Date
• condition: work item type equals Epic
• branch related work items: to children
  • smart values condition: SLO does not equal empty
  • action: edit work item, using the date time functions to increment the trigger values date, such as:
    • {{triggerIssue.duedate.plusDays(issue.SLO)}}

Please review that documentation for the date / time functions to learn what is possible.

Then, use this how-to article to confirm you have the correct smart value for your SLO field: https://support.atlassian.com/cloud-automation/docs/find-the-smart-value-for-a-field/

[Allah-asra_ Yankal]

@Bill Sheboy  thank you! Here's what I have come up with based on the info you have provided but it the rule does not seem to be running (after checking the audit log).

Here's the reasoning I am trying to establish: when the Epic due date value change, look for  work item that has 'RC2 - Report IS' as summary , and apply the following {{issue.parent.duedate.minusDays(90)}}

[Bill Sheboy]

Thanks for that information, @Allah-asra_ Yankal 

Please post an image of the audit log details showing the rule execution.  That will help identify why the update did not happen as expected.

[Allah-asra_ Yankal]

There is it

[Bill Sheboy]

@Allah-asra_ Yankal  -- For the log you show, the branch found no child work items.  Was that expected for that trigger work item?

And...are the child work items in the same project as the Epic?

When they are in different projects, the rule scope (in the details at the top) needs to change for the rule to access them.  Your Jira Site / Product Admin will need to help make that change in the global automation settings area.

[Allah-asra_ Yankal]

Yes the child work items are in the same project as the Epic. 

The expectation is for the rule to be executed for the child work items when the date field is entered at the epic level

[Bill Sheboy]

For the audit log you showed when the rule ran, please expand all of the areas with the > indicators to show which work item triggered the rule.

There is also another possibility: the feature to add conditions to triggers is quite new, and there have been several reported defects.  You could remove the condition from the trigger and add it as a separate condition immediately after the trigger.  That will help confirm my above hypothesis: the rule is running for a different work item than you expected.

[Allah-asra_ Yankal]

@Bill Sheboy  thank you! Here's what I have come up with based on the info you have provided but it the rule does not seem to be running (after checking the audit log).

Here's the reasoning I am trying to establish: when the Epic due date value change, look for  work item that has 'RC2 - Report IS' as summary , and apply the following {{issue.parent.duedate.minusDays(90)}}