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; } } }

Copy old value of fix version field using project automation

Vikrant Yadav

Hi Guys,

Need your help in automation.

I want to capture old value of Fix version in another field.

Rule is running for edit issue trigger >> When new value added/remove from Fix version field, older value will update in Single line text field. I am using below smart value but it's not updating the field.Kindly suggest :-

{{issue.changelog.fixVersions.toString}}

Note :- Using Automation for JIRA DC

Accepted answers

Samuel Gatica _ServiceRocket_

Hi @Vikrant Yadav

Unfortunately, there is no workaround currently.

Here is a linked defect: https://jira.atlassian.com/browse/JSWCLOUD-22815

Best regards

Sam

Trudy P Claspill

Hello @Vikrant Yadav

I was looking at the documentation for Smart Values and specifically for {{changelog}} for DC here:

https://confluence.atlassian.com/automation/jira-smart-values-issues-993924860.html

I think that your syntax is not correct. The examples in the document look like this:

{{#changelog.summary}}
  {{toString}}
{{/}}
{{#changelog.issuetype}}
  {{fromString}}
{{/}}
// Previous status name
{{#changelog.status}}{{fromString}}{{/}}
// Previous status id (for using in another Edit action
{{#changelog.status}}{{from}}{{/}}

Additionally the document says it is not available with all triggers, so there may not be changelog information when using the Field Value Changed trigger.

I did some experimenting in my Jira Cloud instance with Field Value Changed and Issue Updated triggers and the format shown above, and was not able to get any output from the changelog for the fixVersions field. For Jira Cloud the documentation also says that the fields available in the change log are limited. I don't know if that might be the case in Automation for Jira DC also.

All comments

Samuel Gatica _ServiceRocket_

Hi @Vikrant Yadav

Unfortunately, there is no workaround currently.

Here is a linked defect: https://jira.atlassian.com/browse/JSWCLOUD-22815

Best regards

Sam

Trudy P Claspill

Hello @Vikrant Yadav

I was looking at the documentation for Smart Values and specifically for {{changelog}} for DC here:

https://confluence.atlassian.com/automation/jira-smart-values-issues-993924860.html

I think that your syntax is not correct. The examples in the document look like this:

{{#changelog.summary}}
  {{toString}}
{{/}}
{{#changelog.issuetype}}
  {{fromString}}
{{/}}
// Previous status name
{{#changelog.status}}{{fromString}}{{/}}
// Previous status id (for using in another Edit action
{{#changelog.status}}{{from}}{{/}}

Additionally the document says it is not available with all triggers, so there may not be changelog information when using the Field Value Changed trigger.

Bill Sheboy

Yes, and...

Here is the related defect for automation, which covers both Jira Cloud and Server/Data Center versions of the symptom: https://jira.atlassian.com/browse/JIRAAUTOSERVER-207

Please note, you may observe changelog intermittently working for fixVersion. I found through testing there are very specific paths by which it still works and it randomly fails for others. IMHO: this one is quite broken :^)

Kind regards,
Bill

Vikrant Yadav

Hi @Trudy P Claspill ,

Thanks for your response!

I tested this as well :- {{#changelog.fixVersion}}{{toString}}{{/}} but it won't give any response and not update the field.

I tried this as well {{fieldChange.fromString}} , it works sometime and sometime it doesn't work. When i remove a single fix version sometime it works but when multiple fix version it breaks.

Vikrant Yadav

Thanks @Bill Sheboy and @Samuel Gatica _ServiceRocket_
yep, there is no workaround for this right now.

Any alternate solution, you would like to suggest. I have Scriptrunner and JMWE

What is the result of this value :- {{triggerissue.fixVersions.name}} ?

Trudy P Claspill

Trying to think of other options...

It is not pretty, but you could use two custom fields.

Each time Fix Version changes, write the contents of field #1 to field #2. Then write the contents of Fix Versions to Field #1. Field #2 would always have the value before the last change to the field.

Vikrant Yadav

@Trudy P Claspill How do I copy the value? If I use post function or automation it copy the current value to Field 2. Can you please share the trigger and action which I need to setup for this? 🙏

Welcome!

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

Quick Links

Find more posts tagged with

server

jira

jira-server

jira-data-center