Looptijd van een bovenliggend item

[Bert Van Humbeek]

Hallo,

hoe kan ik maken dat de looptijd van een bovenliggend item (epic/task) automatisch wordt aangepast aan de looptijden van de onderliggende items (task/subtask)?

bvb: binnen de epic loopt task 1 van 1/1 tot 5/1, task 2 van 8/1 tot 15/1 - hoe maak ik dat de epic automatisch gepland wordt van 1/1 tot 15/1?

NB: deze regel werkt niet "Set Parent Start and Due Dates Based on Subtasks" (When an issue is updated, set the parent issue's start date to the earliest start date of its subtasks and the due date to the latest due date of its subtasks.) 

[Trudy Claspill]

Hello @Bert Van Humbeek 

Welcome to the Atlassian community.

I recommend a rule structure like this:

TRIGGER:Field value changed
  Field:specify your start date field here

CONDITION: Work item fields condition
  Field: Issue type
  Condition: is not one of
  Values: Epic, Sub-task

FOR EACH: Related issues/Parent

    ACTION: Lookup work items
       JQL: parent={{issue.key}} and "Start date" is not empty

     CONDITION: smart values condition
        First value: {{lookupIssues.size|0}}
        Condition:greater than
        Second value:0

       ACTION: Edit work item
         Field:Start date
         Value: {{lookupIssues.Start date.min}}

In the above you need to specify the appropriate field that you use for "Start date"

You would create a similar rule for your end date field, using the max function instead of min.

This rule does not change the date fields in the parent if all the child items' fields are empty.

[Enric Font]

Dear @Bert Van Humbeek 

You should configure an automation rule:

When

• subtask added or dates on the subtask are updated

Then

• for each subtask of the parent
  • get the min start date
  • get the max end date
• update parent dates

With BigPicture you can set this behaviour autommaticaly with the schedulling mode AUTO BOTOM UP

[Bert Van Humbeek]

Thank you, I'll try this rule :-)