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

How to set up parent task to have the same due date as child task

Leslie_Hernandez

Hello everyone,

I am new to Jira and I'm having some issues setting up automations.

I have a project with many task, and those tasks have child tasks, I noticed that the parent task has the last due date of the child tasks, is there is way I can set up the parent to have the earlies child task' due date?

and if possible, once the first task is completed have the next due date show?

Thank you!

Accepted answers

Bill Sheboy

Hi @Leslie_Hernandez -- Welcome to the Atlassian Community!

It seems your project has an existing automation rule, or script addon, running which is making the change to the parent Due Date.

Please post images of your current rule and the audit log details, as that will provide context for the community to offer suggestions on rule changes. Thanks!

Kind regards,
Bill

All comments

Bill Sheboy

Hi @Leslie_Hernandez -- Welcome to the Atlassian Community!

It seems your project has an existing automation rule, or script addon, running which is making the change to the parent Due Date.

Please post images of your current rule and the audit log details, as that will provide context for the community to offer suggestions on rule changes. Thanks!

Kind regards,
Bill

Leslie_Hernandez

My apologies @Bill Sheboy , It looks like we do not have any automation rules. I believe due dates were entered manually.

Would i still be able to create a rule so the parent task can pick up the earliest due date from the child tasks? child task.PNG

These are my current child tasks with due dates, but i want the parent to pick up the first task's due date since its due first.

Bill Sheboy

Hi!

Yes, that is possible with an automation rule. Basically you decide the trigger (e.g. adding subtask, editing the due date, etc.), gather the sibling subtasks, and grab the smallest date to use.

Perhaps something like this:

trigger: issue created
action: re-fetch (this will slow down the rule and reload the data...which is often needed with this trigger type)
condition: issue type is subtask
branch: to the parent of the subtask
- action: lookup issues with JQL to gather all of the sibling subtasks. You may want to qualify this to ignore done issues.
- action: edit the issue (parent) to see the due date to

{{lookupIssues.duedate.min}}

To get you started on creating your rule, please review this documentation and examples:

Leslie_Hernandez

This is what i have,

I have not been able to figure out how to properly do the "Then: look up" step (second to last)

Thank you!

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

jira-software-cloud