Target Date change- Automation

[Anuradha Yadav]

Hi Team,

We are unable to see the changed target end in the comment section after the automation rule is successful.

Could you please help. I am sharing the Automation details below:

The Target End has been changed by: {{initiator.displayName}} to a new Target End of: {{issue. Target End}}

[Kalyan Sattaluri · Accepted solution]

Hello @Anuradha Yadav 

Please share more details so community can help. Especially, put some log statements inside your rule to capture {{Target end}} field and share audit log screen shot.

Cause we cannot tell if rule is putting a comment but Target End date is empty, or rule is not even putting a comment..  But at a high level your rule looks good so please add log statement and share audit log. Thanks.

[Manoj Gangwar · Accepted solution]

Hi @Anuradha Yadav ,

Welcome to the Atlassian Community!

Please try to use a custom field ID instead of a name.

Please refer to the below doc for the smart values.

https://support.atlassian.com/cloud-automation/docs/examples-of-using-smart-values-with-dates/

[Anuradha Yadav]

Hi @Manoj Gangwar ,

Thanks I will check if I can get customfield ID.. Because I do not have Admin access. 
but Meanwhile is there any other way?

[Manoj Gangwar]

Using the Advanced JQL view

Using a combination of the ListView and advanced JQL, we can identify the ID of a custom field that's listed on the results.

(info) This option does not require Jira Admin rights.

Create a simple JQL to return an issue that had the field that you want.

After running this query, switch to the "List View" if not already.

Add the field you want as a column in the results.

Click on the name of the field in the column to order the results by this custom field.

Now switch the JQL type to Advanced if not already.

The ID of the field will be listed in the ORDER BY clause.

[Anuradha Yadav]

@Manoj Gangwar with the customfield ID it is still not working.

[Kalyan Sattaluri]

hello @Anuradha Yadav 

its just customfield_11629 not customfieldID_11629

so please change it to {{issue.customfield_11629}} in your email template and try..