Automation for Jira calculated date field isn't working

Jeremy Jedlicka May 25, 2022

I have what should be a simple date calculation automation task that I can't seem to get working.

The fields in question are Date of Review and Expiration Date.

The rule is set to trigger when Date of Review changes and then Expiration Date changes to Date of Review plus 2 years.

The SmartValue I have written that doesn't work is:

{{issue.Date of Review.plusYears(2)}}

When this executes it clears whatever is currently populated in Expiration Date.

I changed it to use the custom value field also to try:

 {{issue.cf[17889].plusYears(2)}}

That does the same thing.  If I change the Reference field it works though. So:

{{issue.Created.plusYears(2)}} 

 Successfully changes the date in Expiration Date to the Created date plus 2 years.

 

Can anyone tell me why the field Date of Review would cause this problem?

 

I would post screenshots, but our Jira server is on a separate network not connected to the wider internet.

2 answers

1 accepted

0 votes
Answer accepted
Jorge Martinez
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
May 25, 2022

Hi @Jeremy Jedlicka 

Please confirm the ID of ypur custom fields and try:

{{issue.customfield_17889.plusYears(2)}}

 
If that doesn't work could you share your audit log please?

0 votes
Jorge Martinez May 25, 2022

Suggest an answer

Log in or Sign up to answer