Automation: Changelog for Status Change

[Christa Wyler]

Hi All

I have the following action in the automation but smart values are not taken.

action in automation: Comment on Issue

"Status has changed from status "{{#changelog.status}}{{fromString}}{{/}}" to "{{#changelog.status}}{{toString}}{{/}}"

Result in issue comment

Status has changed from status "" to ""

Initial situation

The Trigger at the moment is manually - and I did a Status Change on the issue before running the automation

Any ideas?

When I check the documentation the smart value "changelog.status" should work. Anyone already had this issue and was able to solve it? Otherwise I will ask Atlassian.

Thank you 

[Pavol Gočal · Accepted solution]

Hello @Christa Wyler

try this syntax:

Status changed from:
{{changelog.status.fromString}}
to:
{{changelog.status.toString}}

This way, you will see the status in the comment:

[Christa Wyler]

Hi @Pavol Gočal 

Thanx for your answer! Still not working

Automation (really no logic in it):

History (just changed the Status again before running the automation)

I think I have to ask Support...

[Pavol Gočal]

Not sure, but might be because of the manual trigger? 

Try the automation like this: 

1. Trigger - Field value changed
   1. Field to monitor for changed - Status
   2. Change type - Any changed to the field value
   3. For - All issue operations
   4. 
2. Action - Comment on issue
   1. Comment - Status changed from: {{changelog.status.fromString}} to: {{changelog.status.toString}}
   2. Consider uncheck the "Prevent duplicates by only adding this comment once to a particular issue."
   3. 
3. Check the Rule details to see if there is maybe some wrong configuration (e.g. you test if on issue that is in different project, that the Rule Scope). For example, I have it configured only for 1 project:
   1. 

With this configuration, when I change the status for the issue, the comment is added:

[Christa Wyler]

@Pavol Gočal 

Yes, with a different Trigger it works. Thanx a lot for your inputs!

The idea was to have a scheduled trigger which also doesn't work (manual was only to test it out).

Interesting, I just thought with {{changelog.status...}} it might take the last status change - no matter when it happened.

And: we wanted to use "scheduled" because it will be a global automation. So, it will be triggered for every status change but only a few (linked issues) the automation will do anything.

That's why we tried to find another solution than the status change trigger.

Thanx!

[Bill Sheboy]

Hi @Christa Wyler 

The changelog and fieldchange smart values only have values when a field has changed and triggered the rule.  Rule triggers which do not detect field changes will not work.

And...some field changes do not appear (or appear incorrectly) in those smart values.  For example, some list fields like Sprint and Fix Version do not accurately update the changelog for automation rules.

What problem are you trying to solve by looking at the status change log?  That is, "why do this?"  Knowing that may help the community to offer additional suggestions.

Kind regards,
Bill