-
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
[AUTO-1630] {{changelog}} smartvalue not updating Assets custom field in automation with issue created trigger.
Hi 139904013ba4,
the docs at [Automation smart values - issues | Cloud automation Cloud | Atlassian Support|https://support.atlassian.com/cloud-automation/docs/jira-smart-values-issues/#--changelog--] show the following (or are there other docs I am missing?):
Available properties
- changelog.summary - Changelog information for the Summary field.
- changelog.issuetype - Changelog information for the Issue type field.
- changelog.status - Changelog information for the Status field.
Does this really imply that "changelog" officially only supports "summary", "issuetype" and "status" and all other field changes currently also shown within the changelog should be considered "unsupported". This distinction is important for us because we then would have to ensure that we do not base any automations on any other (undocumented) "changelog" properties.
| Was this caused by a recent change? | New: No [ 19032 ] | |
| Status | Original: Needs Triage [ 10030 ] | New: Gathering Impact [ 12072 ] |
Currently could be said is more of an inconsistency rather than a bug since it is following the docs from Automation for the changelog smart value.
Since this also happens with trigger "Field value changed" for smart value "changelog" the workaround there has to be the use smart value "fieldChange". This limits the number of fields tracked in the trigger to one since only the first changed field is tracked there.
| Labels | New: jsw-s13 |
Hey 2cbb1de06b99,
We currently don't plan to support extra properties in the changelog smartvalue at the moment. It will have the current payload of what you see in issue created. Unfortunately yes, changelog only officially supports what we provide in our docs at the moment but we don't plan to redact any existing functionality that changelog provides already.