is there any way to change due dates automatically in several task with different due dates ????

[MURUGESH S]

hi everyone

i have epic ticket under the epic ticket there are many task tickets linked

so my question is is there any possible way if we enter duedate in epic ticket automatically update task tickets  with deferent due dates (  for each task need saparate due dates while changing te due date in epic ticket)

please someone help me

[Mark Segall]

Hi @MURUGESH S - This is definitely possible, but it would help if you provide a little more context. Is your expectation that the due date will be dynamically determined based upon some type of business logic?  If so, what is that business logic?

[MURUGESH S]

It’s not a one time thing or dependent on user input so i need automation for if we enter duedate in epic ticket automatically update task tickets  with deferent due dates (  for each task need saparate due dates while changing te due date in epic ticket)

[MURUGESH S]

Requirement example 
i have one EPIC under that 4 task issues are linked

 EPIC due date =1-8-2023   if i enter this dude date in epic .the  due dates of tasks wil be automatically updated like this 

task1=1-2-2023

task2= 1-3-2023

task3= 1-1-2023

task4=1-4-2023


Is this possible ????

[Mark Segall]

Yes it's possible, but need to make sure the business logic is repeatable.  For example, will task 3 always be 7 days before, task 1 always be 6 days before, task 2, 5 days before, etc?

Automation needs repeatable parameters:

• How does it know what date to set the child issues?
• How does it know the sequence (e.g. How to identify what should be task 1, 2, 3 etc)?

[MURUGESH S]

The requirement we needed all tasks underneath the Epic to have their due dates set based on a formula of

(Epic Due Date) - (Months Prior field)

[Mark Segall]

Thanks for the clarification.  One more question.  The months prior field.  Is this just a simple numeric field indicating how many months prior?  For example:

• Epic Due Date: 31/Dec/23
• Task Months Prior: 5
• Task Due Date: 31/July/23

Is this the expected outcome?

[MURUGESH S]

yes exactly this is the requirement

[MURUGESH S]

we have lot of tasks under epic 

for each task we have different month prior

[Mark Segall]

Thanks for clearing things up.  Here's how the rule could look:

• TRIGGER: Field Value Changed (Due Date)
• CONDITION: Issue Type = Epic
• BRANCH: Stories (or Other Issues in Epic)
  • ACTION: Edit Issue (Due Date)

    • {{triggerIssue.dueDate.minusMonths(issue.Months Prior)}}

[MURUGESH S]

custom feild =month prior ( number field ) is this rule works for this ???

[Mark Segall]

Yes - If it's a numeric field, this should work.

[MURUGESH S]

i have created same rule but it is not working 

[Mark Segall]

Can you please share a screenshot of the rule audit log?  This will help us understand what's failing.

[MURUGESH S]

audit log shows it success but in task issue the due date shows empty

[Mark Segall]

Hmm... Can you share a screenshot of the rule itself?

[MURUGESH S]

[MURUGESH S]

Like this i need result

[MURUGESH S]

here is the audit log its show success but it was not edit the due date in tasks

[Mark Segall]

Hmm... Everything looks good.  Perhaps there's something amiss with the smart value.  Can you add a Log Action to your rule just below the Edit Issue Fields with this:

Epic DueDate: {{triggerIssue.dueDate}} ** Months Prior: {{issue.Months Prior}} ** Task DueDate: {{triggerIssue.dueDate.minusMonths(issue.Months Prior)}}

Then run it again and let's look at the log.  This will give us a sense of what it's picking up/processing.

[MURUGESH S]

Awesome its working

you are Marvelous, Thank ,Thank so much for your help

[MURUGESH S]

and i have forget to one more thing same requirement need for weeks prior also 

is this possible ???

[Mark Segall]

I'm not sure what changed for you that it's suddenly working.  The Log Action was only intended to help provide visibility into what was going on and help us troubleshoot the issue further.

As for Weeks Prior... I need a little more info.  Is the intent that the months/weeks prior are to be combined in the calculation?  For example...

• Epic Due Date = 31/Dec/23
• Task Months Prior = 1
• Task Weeks Prior = 2

Is the expectation that it would return something like 16/Nov/23?  Or is there an expectation that the Weeks prior would be calculated against a different field?

[MURUGESH S]

can i use like this ???

        Log Action :Epic DueDate: {{triggerIssue.dueDate}} ** Weeks Prior: {{issue.Weeks Prior}} ** Task DueDate: {{triggerIssue.dueDate.minusWeeks(issue.Weeks Prior)}}

• ACTION: Edit Issue (Due Date)

  • {{triggerIssue.dueDate.minusWeeks(issue.Weeks Prior)}}

[MURUGESH S]

if we enter in weeks prior then we ignore month prior feild 

[Mark Segall]

Ahh ok - So I would change up your rule to look like this:

• TRIGGER: Field Value Changed (Due Date)
• CONDITION: Issue Type = Epic
• BRANCH: Stories (or Other Issues in Epic)
  • CONDITION: Weeks Prior IS NOT EMPTY 
  • ACTION: Edit Issue (Due Date)

    • {{triggerIssue.dueDate.minusWeeks(issue.Weeks Prior)}}

• BRANCH: Stories (or Other Issues in Epic)
  • CONDITION: Weeks Prior IS EMPTY 
  • CONDITION: Months Prior IS NOT EMPTY
  • ACTION: Edit Issue (Due Date)

    • {{triggerIssue.dueDate.minusMonths(issue.Months Prior)}}

[MURUGESH S]

these conditions are not successful weeks prior not working 

BRANCH: Stories (or Other Issues in Epic)

• CONDITION: Weeks Prior IS EMPTY 
• CONDITION: Months Prior IS NOT EMPTY
• ACTION: Edit Issue (Due Date)

  • {{triggerIssue.dueDate.minusMonths(issue.Months Prior)}}

[Mark Segall]

Can you please share screenshots of your updated rule and audit log?

[MURUGESH S]

i have remove this condition 

• CONDITION: Months Prior IS NOT EMPTY

now its working  

Thank you very so much @Mark Segall 

[MURUGESH S]

[Mark Segall]

The condition assures that it doesn't trip over itself, but if it's working for you that's good for me.  🙂

[MURUGESH S]

Thank you very so much to you