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

Jira automation edit field fix version based on custom field value

Meytal BM_tgpmuh

Hi all, this is what i am trying to do:
When an issue is created and the customer field "Planned version" is not empty (meaning it was filled in with the selected Version), then update the same issue's FixVersion field with the value of the "Planned version" field. Both of these fields are taking the value from "Releases", so it should not be an issue.
I don't get any errors, but it is NOT updating the "Fix version" field upon creating a new issue, in which i selected a "Planned version".
What am i doing wrong?
Thanks

Screenshot (2).png

Accepted answers

Callum Carlile _Automation Consultants_

Hi @Meytal BM

You can use the smart value {{issue.Planned version}} or {{issue.customfield_11878}} to set the Fix version field - and for the rule to run successfully, there will need to be a Fix Version with the exact same matching text as the Planned version.

Hope this helps!

Nic Brough -Adaptavist-

What type of field is "planned version"?

Meytal BM_tgpmuh

@Nic Brough -Adaptavist- @Callum Carlile _Automation Consultants_ it worked! THANK YOU BOTH!

I did a refresh on the page and I saw that the automation worked. I guess once the issue is created, the automation runs and there is probably a few seconds glitch.

Here is what i have done. Screenshot (10).png Screenshot (9).png

All comments

Callum Carlile _Automation Consultants_

Hi @Meytal BM

Hope this helps!

Meytal BM_tgpmuh

Thanks @Callum Carlile _Automation Consultants_ for the quick response.

I updated the automation and it still doesn't work.

Please see the images and let me know if these are correct.

Is the condition and action correct?

Are the values correct?

You can see the result of the issue view that also i added the Planned version, it did not add Fix version. And yes, their values come from Version, so there should not be an issue regarding values.

thanks

Screenshot (3).png Screenshot (4).png

Nic Brough -Adaptavist-

What type of field is "planned version"?

Meytal BM_tgpmuh

@Nic Brough -Adaptavist- Version Picker (single version)

Callum Carlile _Automation Consultants_

@Meytal BM If you click into your Audit log, what does it say? Does the rule run successfully or are there any failures?

Callum Carlile _Automation Consultants_

@Meytal BM Another thing to try:

On the action for editing the Fix Version, click on the 3 dots to the right of the field, then click Copy From. In the fields available, you should be able to select under the 'Field to copy value from' your Planned Version field.

Also, you won't need the JSON in the Additional Fields section as well as the above config

Nic Brough -Adaptavist-

Ok, that might be the problem - most automations can only copy between fields that hold the same content. Fix version holds a list of version objects, but I think the version picker holds just a version object, with no containing list. I don't know how (or if) you can convert from a single version to the list.

Meytal BM_tgpmuh

Thanks @Nic Brough -Adaptavist- .

In the case, i created a new custom field as Version Picker (multiple version).

It still doesnt update. wdyt?

Screenshot (6).png Screenshot (5).png

Meytal BM_tgpmuh

@Nic Brough -Adaptavist- @Callum Carlile _Automation Consultants_ it worked! THANK YOU BOTH!

I did a refresh on the page and I saw that the automation worked. I guess once the issue is created, the automation runs and there is probably a few seconds glitch.

Here is what i have done. Screenshot (10).png Screenshot (9).png

Nic Brough -Adaptavist-

Ah, yes, Automation is asynchrnous - it usually happens after a change, so you often need a refresh to get the updated view!

Well spotted! I always forget that!

Bill Sheboy

Hi @Meytal BM

When the Issue Created trigger is used, there is a chance of a timing problem where all of the data is not yet available to the rule. The symptom you will see is conditions after the trigger fail to find what you expect. This is a known REST API defect that Atlassian is working on. (We have an open support ticket for it.)

The work-around I use is to *always* put a Re-fetch action immediately after the Created Issue trigger. That will slow down the rule and reload the data before proceeding.

Best regards,

Bill

Meytal BM_tgpmuh

Thanks @Bill Sheboy . What is a Re-fetch. how do i do that?

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

jira-software-cloud