One of our work management projects has a custom field "Change Date/Time" that, when changed, should trigger an automation to change the Due Date field.
The automation I have set up to do this copies the "Change Date/Time" field value to the Due Date field, but always seems to increment it by a day.
I tried changing this to set the Due Date by referencing the custom field directly, like this:
{{issue.getCustomFieldValue(customfield_"Change Date/Time")}}
The automation runs without error, but the Due Date gets set to null, rather than the date from "Change Date/Time".
How do I set Due Date to the correct date?
The due date field is a date type and your custom field is a date/time field, so instead try setting the field with this, using the jiraDate formatting to drop the time:
{{issue."Change Date/Time".jiraDate}}
And also, smart values are name, spacing, and case-sensitive. Let's confirm you have the correct smart value for your field using this how-to article: https://support.atlassian.com/cloud-automation/docs/find-the-smart-value-for-a-field/
Essentially you identify and issue with your field, call the REST API using a browser, search for your field on the page, and you will find your smart value and the custom field id, if you want to use that instead. Most importantly, if you do not find your field in the results, it is not supported by automation rules. (This can be the case for some built-in and marketplace app fields.)
If neither of those things help, please post images of your complete rule, showing your issue edit action details, and of the audit log details showing the rule execution. Those will provide context for the community to offer suggestions.
Kind regards,
Bill
This is exactly what I was looking for, Bill! Thank you! It worked like a charm!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Awesome; I am glad to learn that helped!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.