Automation: Create Complete Project plan - Flexible Date picken, depending on required phases

[Jörn]

Hi Guys,

actually I´m working on an automation to prepare a project and its tasks based on the actual dates. I hope you guys are able to help. I could not find any solution yet by search. 

Boundry condition

The project is devided in different phases (we use Epics, Tasks, Sub Task). Depending on the customer selected Moduls some Phase and its tasks are not relevant (if else rule). Accordingly the final start and end dates of each phase shall be aligned. The GANT shall look clean and one Phase date is connected to the next.

My actual solution do not provide the fleixibilty that the start and End dates of all phase are adjusting/setting it self depending on the previous created End Date of an issue. 

Actual unflexibel solution in the automation 

Kick Off Phase - Smart Value - Start Date: {{now.plusBusinessDays(0)}}, End Date:  {{now.plusBusinessDays(20)}}

NEXT Tasks A Start Date:: {{now.plusBusinessDays(21)}}, End Date:  {{now.plusBusinessDays(25)}}

NEXT Tasks B Start Date:: {{now.plusBusinessDays(26)}}, End Date:  {{now.plusBusinessDays(27)}}

Problem

If A project does not contain a modul and the TASK A is not required accordingly. I do have a gap inbetween the timing of Kick of Phase and Task B. (END Date Kick Off = 20days, Start Task B = 26days)

Question: 

Is there a solution, maybe smartvalue, to pick the End Date from previous created Task in the automation and add time in days accordingly. 

I thought to use {{[Date].plusDays(14)}}. What would be the correct field to use for the [Date]? Or is there are totally differnt solution?

Note: As we have 20 different moduls (qty. growing) it is to tough to create an automation for each type of combination additionally. 

Looking forward to you guys, if you could support me in this case. I assume that the solution what be interessting for many others as well. 

[Maroof Ahmed Malik]

Did you find the solution to this? I'm exactly in the same problem

[Bill Sheboy]

Hi @Maroof Ahmed Malik -- Welcome to the Atlassian Community!

Depending on the structure of the automation rule, it may be possible to refer to the last created issue, and reference its dates.

I do not recall if the {{createdIssue}} smart value works correctly outside of an if/else condition when the issue was created inside the condition, as for the case the original poster suggests.  Perhaps try it to confirm the behavior.

Kind regards,
Bill