Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
badges earned

Your Points Tracker
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Jira automation edit field fix version based on custom field value

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?

Screenshot (2).png

3 answers

3 accepted

1 vote
Answer accepted

@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).pngScreenshot (9).png

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!

Like # people like this

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,


Like Meytal BM likes this

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


A re-fetch is an action which reloads the latest state of the issue/issues selected by the trigger.

  • Immediately after your trigger, there should be space to select Add Component
  • Then select New Action
  • And select Re-fetch Issue Data

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!

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.



Screenshot (3).pngScreenshot (4).png

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

@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

@Callum Carlile _Automation Consultants_  I did that, but still doesn't copy that value over.

Note that i created a new Planned version custom field that is multi-versions, which is the same as Fix versions.

Have a look at the screenshot.

Screenshot (8).png

0 votes
Answer accepted

What type of field is "planned version"? 

@Nic Brough _Adaptavist_ Version Picker (single version) 

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.

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).pngScreenshot (5).png

I can't see any reason why that would fail.  I'm sorry, I'm stuck now, we'll need to ask someone who knows field handling in Automation better than me.

Like Meytal BM likes this

@Nic Brough _Adaptavist_  i appreciate it. I am also mind boggled by this. Look at the changes I have made that @Callum Carlile _Automation Consultants_  ( see above) suggested and yet it is still not working.

Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Jira Service Management

JSM June ask me anything (AMA)

Hello Community members! We’re wrapping up the end of JSM June with an Ask Me Anything (AMA) with the Jira Service Management product team. This is your chance to ask all your ITSM questions to o...

120 views 7 10
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you