nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Can I use CHANGELOG to show changed values in an automation email?

Mathew Sommers

Have an automation that is triggered when a value is changed (FixVersions) and have an email sent that includes the new changed value, want to also add the previous value ... here is what I go so far .. but doesn't work:

Changed to: {{triggerissue.fixVersions.name}} <-- this works
Changed from: {{changelog.fixVersions.fromString}} <-- this does not work

Have tried a few different combinations of .name.fromstring and others without success. Any help appreciated.

Accepted answers

John Funk

Hi Mathew,

This is what I use for a field change:

{{issue.key}}'s {{fieldChange.field}} field was updated from {{fieldChange.fromString}} to {{fieldChange.toString}} by {{initiator.displayName}}.

It fires when the field is updated so I assume it will work for fixVersions also.

All comments

John Funk

Hi Mathew,

This is what I use for a field change:

{{issue.key}}'s {{fieldChange.field}} field was updated from {{fieldChange.fromString}} to {{fieldChange.toString}} by {{initiator.displayName}}.

It fires when the field is updated so I assume it will work for fixVersions also.

Mathew Sommers

Thanks! This worked (mostly.) Only limitation I found testing it was if I add more than one fixVersion then it returns empty, but in our situation it is generally 1:1 change and not multiple versions, so it should work most of the time.

Thanks!!!

John Funk

Great! Glad it is at least mostly working for you. :-)

Raji

@[deleted], I tried using your suggestion, for a rule triggered by change of Fix Version. It works well for everything, but {{fieldChange.fromString}}. It displays a blank for this. However, it works fine with {{fieldChange.toString}}

I tried the exact same solution where I have the trigger based on change if other fields like 'assignee'; where it works well for both fromString and toString. Any thoughts on why it does not work for FixVersion?

My trigger condition pasted below

FixVersion trigger.jpg

Šarūnas Meižikas

Has anyone been able to solve this scenario?

We usually use multiple fix versions for each task, when you change value completely - no issues, you get alert 'old - xxx, new - yyy'. But when you simply add another value, then instead of getting 'old - xxx, new - xxx, yyy', old value is shown as empty.

John Funk

@Simmo - Any thoughts here?

Simmo_9kntn7

Hey @John Funk ,

Multi value fields and value change is a bit of a tricky one. We've got:

https://codebarrel.atlassian.net/browse/AUT-2013 and https://jira.atlassian.com/browse/JRACLOUD-74953

The issue here is the way that the changelog treats the value change we get two entries I think. One for the old value and one for the new value. So we get the latest entry and have the new value but not the old. Its something like that. Bit of a known issue that requires quite a rework.

Hope that helps!

Cheers,

Simeon.

Mathew Sommers

I was able to solve this issue with a small work around. They way I did it was to create a hidden field that when the FixVersion changes, I copy the changed value into it ... the next time it changes, I pull from that value as the 'old value' and then after reporting, update the value. Screen shot shows the rule and the resultant email screen shots.

Screenshot 2020-09-30 065706.jpg

OlehK

Hi, @Mathew Sommers. I don't know if you found a solution, but I have found one.

We can see the following example in the docs {{#changelog.fixVersion}}{{toString}},

Screenshot from docs

but it isn't correct, because in the changelog the fixVersion field is called 'Fix Version'

Screenshot from Jira Automation log:

So, if you want to get all fixVersion changes from #changelog please use

{{#changelog.Fix Version}}{{toString}} instead of {{#changelog.fixVersion}}{{toString}}

Result of execution:

In your case it should be {{changelog.Fix Version.fromString}} instead of {{changelog.fixVersions.fromString}}

I hope you'll find it useful.

Kalyan Sattaluri_iinm1n

Hey, thanks for digging in and catching the right syntax. Really Helpful!!

Joanne Giammo

Thank you, using {{changelog.Fix Version.fromString}} worked! No more blanks.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

cloud

jira-software

automation