automation for jira: minusDays(7) returns no value

[Jeffrey Bistrong]

Trying to figure out why {{issue.customfield_11479.minusDay(2)}} is not returning any values.

As you can see in the first log {{issue.customfield_11479}} returns a value, but adding the minusDays(2) it returns nothing

[Bill Sheboy]

Hi @Jeffrey Bistrong 

Please try using minusDays() instead of minusDay(), as I believe all of the plus/minus ones use a plural name for the units of measure:

https://support.atlassian.com/cloud-automation/docs/jira-smart-values-date-and-time/

Kind regards,
Bill

[Jeffrey Bistrong]

sorry got caught up in trying lots of the possibilities, but still nothing

[Bill Sheboy]

What is the type of that custom field?

If it is not date type, you could add an asDate conversion before making the adjustment.

[Jeffrey Bistrong]

it is a date type, but it is a system field, so not sure if that has anything to do with it

However after multiple rounds of testing I got the following syntax to work. Thank you for pointing me in the right direction

{{issue.customfield_11479.toDate("yyyy-MM-dd").minusDays(7).jiraDate}}

[Bill Sheboy]

Thanks, and I believe Target Start is one of those advanced roadmap fields which has some oddity with automation rules.  Other built-in/system fields like that are indeed text and not date or date/time type, and so the conversion was needed.  (Another example is the Status Category Changed Date, which is text for a date/time value.)