-
Bug
-
Resolution: Unresolved
-
Low
-
Minor
-
Jira Service Management
Issue Summary
In the context of a Jira Automation the {{changelog}} smart value https://support.atlassian.com/cloud-automation/docs/jira-smart-values-issues/#--changelog-- is not reflecting the changes in an Assets custom field when using an Issue created trigger.
Steps to Reproduce
- Create an Assets custom field.
- Make sure it's added to the Create issue screen so that you make sure that a value is assigned during the issue creation.
- Create an automation consisting of an Issue created trigger and a Log action pointing to the {{changelog}} smart value
- Create an issue making sure that the Assets custom field is filled out.
Expected Results
When you use a log action the {{changelog}} smart value reflects that the Assets custom field.
Actual Results
When you use a log action the {{changelog}} smart value reflects changes in the fields related on then issue except the Assets custom field.
Workaround
- Get access to the value of the Assets custom field by using other smart value (e.g. issue.[Assets custom field name].label after adding a label to the Assets attribute in the assets field you're interested in getting the information from)
- Change the Automation's rule trigger from Issue created to Field value changed and get the changed value in the Assets field using the {{fieldChange}} smart value
Form Name |
---|