[Jira Cloud] Sum up Start & End date from Stories to EPIC

[Rahul Mittal]

Hi Experts,

Hope you are doing good.

I want to set Epic Start Date & End Date based on below:

Start Date ==> minimum Start date of all the stories linked to that Epic

End Date ==> maximum Start date of all the stories to that Epic

I am using Jira Plans to align Stories in various sprints and, JIRA plans is configured to use the sprint dates and assign them to Stories.

I tried implementing an automation but I keep on getting an error (refer to the screenshot).

Could you please guide on what I am doing wrong?

Jira Plan is using Start Date with field with ID #10800 & End Date with ID#10902.

[Bill Sheboy · Accepted solution]

Hi @Rahul Mittal 

Based upon that image, you are using Jira Data Center.  Is that correct?

If so, the Lookup Issues action in Jira Data Center automation will not work for this scenario because it only supports a limited number of fields at this time.

Please see this post describing how to access the other fields, and perform the edit of the parent, using the REST API: https://community.atlassian.com/t5/Jira-articles/How-Can-I-Sum-Up-Multiple-Issues-into-a-Parent-Number-Field/ba-p/2882712#M16701

Kind regards,
Bill

[Rahul Mittal]

Hi Bill,

I replaced the reference from variable name to custom field ID and it worked

{{lookupIssues.customfield_10800.min}}

Now, I realized that my understanding was wrong that Jira Plans saves the Start & End Dates to Jira issue if the dates are picked based on sprints.

So, I would need to add an automation on Story that will pull Sprint dates and add them as Start & End Date in the Story so that my existing automation can update Epic too.

[Bill Sheboy]

Are you using Jira Cloud or Jira Data Center?  I would not expect that custom field to work with Data Center...unless they have released an update.

[Rahul Mittal]

I am on Jira Cloud.

Hurray! I was able to achieve both the automation.

My Epics are now able to take max & min from stories and show up at Epic level.

Just one call out for any one else having similar ask in future, I used different fields "Planned Start Date" & "Planned End Dates" as I realized that messing up with "Start Date" & "End Date" was impacting JIRA Plans view - as - if the date values are already present in the field (which were coming via automation), then the rule to use sprint dates in JIRA Plan doesn't work - as it requires Start & End date to be empty.

[Rahul Mittal]

Post adding this Query, I did more digging and realized that the "Jira Plans" does not seem to be saving the "Start Date" & "End Date" at the Issue level. Hence, the value can never cascade to the parent Epic as the value is always empty.

So, I would need to add an automation on Story that will pull Sprint dates and add them as Start & End Date in the Story.

Will update this post after doing this second automation.

Also, if there is any other way, then please suggest.,