Automation to roll up Target start and Target end from child issues

[Steve Teiv]

Hi community!

I am new here and I am struggling with an automation to roll up min target start and max target end dates from child issues to their parent epic.

I followed these pages for reference:

• https://community.atlassian<.com/t5/Jira-questions/Automation-to-Roll-up-dates-for-target-start-and-target-end/qaq-p/2477285 

• https://community.atlassian.com/t5/Jira-questions/Is-it-possible-to-copy-value-from-quot-Target-End-date-quot-to/qaq-p/922787
• https://community.atlassian.com/t5/Jira-discussions/Set-Epic-Start-and-Due-Date-to-earliest-latest-Child-Dates/td-p/2353100#U2473939

My automation looks like this:

And my JSON for setting the field value (eg. target end) is like this:

{ "fields": { "customfield_121": "{{lookupIssues.customfield_121.toDate.max.jiraDate}}" } }

However the automation ends to an error and audit log gives this error: "

 (Error parsing date string: (customfield_121))"

Any ideas on how to proceed or what could be the problem?

Thank you already in advance!

[Bill Sheboy]

Hi @Steve Teiv -- Welcome to the Atlassian Community!

For Jira Data Center, the Lookup Issues action does not support custom fields yet.  As you want to set another field based upon the values in the child issues of the Epic, the REST API will need to be used.

Please see this post I made in another question for more details: https://community.atlassian.com/t5/Jira-questions/Re-How-to-sum-story-custom-filed-values-to-an-epic/qaq-p/2787339/comment-id/1043853#M1043853

Kind regards,
Bill

[Tuncay Senturk]

Hi @Steve Teiv 

Is your Target End (customfield_121) a Date field? If it's not, the Automation will fail to parse. 

Null or empty values will also cause the toDate function to fail.

[Steve Teiv]

Hi @Tuncay Senturk , no the Target end date is a locked custom field that is created and required by Portfolio for Jira and the type is "Target end".  So does this mean it is not supported?

[Steve Teiv]

I also tried changing the JSON:

{
"fields": {
"customfield_121": "{{lookupIssues.customfield_121.toDate.max.("yyyy-MM-dd")}}"
}
}

But now it ends in error: " Failed to get value for lookupIssues.customfield_121.toDate.max.("yyyy-MM-dd")"

[Tuncay Senturk]

What type is this custom field? You can find the type on the custom fields page. If it is a date field, it should work properly, but you must include a check for null or empty values.

[Steve Teiv]

The type column in the custom fields page says "Target end". So it is not a date field. 

[Tuncay Senturk]

I am not sure but it might expect the format to be YYYY-MM-DD, YYYY/MM/DD, DD-MM-YYYY

[Steve Teiv]

Thank you @Tuncay Senturk , but this doesn't help either. I tired all of those syntaxs. Any other ideas on how to get this work?