Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

In Jira automation, how to 'inherit' fix version in Advanced?



I want to create an Jira automation rule that will propagate down fix version information from parent to child, for example from Story to Subtasks. At the same time, I want to copy down labels from parent to child as well. 

In my example, I have these definitions in the Story:

"Fix versions" = ["8.2", "8.x"] (two strings)

"Labels" = ["hello", "goodbye"] (two strings)

I have read several posts which looks very similar to my case, like

Unfortunately, there where not enough for me to understand how I should solve my problem, however similar it looked :(

I know how to set up the rule trigger I want, I can branch out over the subtasks correctly, but I'm having difficulties how to to do the assignment of the field/array. (I believe this perhaps has to do with fix versions being a multi-value field)


1. Why is there no 'copy from trigger issue' option in Edit issue, like there already exists for labels field? (this helped my propagate down Labels information, half the task solved).
Skärmbild 2023-03-30 195916.png

2. Since the easy assignment was not enaugh, I had to go to Advanced. Here, should "update" + "add" be used, or "fields"?

3. Since the target field is an array, can it be addressed by the name "Fix versions" anyway? (I found no other allowed syntax, but ...)

4. Since the source field is also an array (the parents information in field 'Fix versions'), how should it be referred to? 

5. I've seen several different ways to access an array and also to transform the content, asJsonString, asJsonStringArray etc. Do I need to transform the content of the source data at all, when I really just want to copy (or add) the whole source field (whole array content) into the target array? 


What I currently have tested (which fails with JSON error, as shown in audit log for automation) is this code snippet:

Skärmbild 2023-03-30 200919.png

I hope someone here can help me understand what I'm doing wrong.

Thanks in advance

1 answer

1 accepted

1 vote
Answer accepted
Bill Sheboy
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
Mar 30, 2023

Hi @Niklas Malmberg 

First thing, there is a copy for fields like Fix is just a bit tricky to find it.  This can be done without the advanced edit JSON when you want to replace the value.

  • add your Issue Edit action
  • select your Fix Version field
  • select Copy at the right side under the ...
  • then select the field to change the option to Copy from Trigger Issue

If you want to add values from the Story to the Subtask's existing values, this is a more complicated solution which does require using the advanced edit JSON for fields like Fix Version to add values using update.


Next, this scenario often requires multiple rules, with different triggers.  And so the edits (in the copy-from) may be different.  Please consider at least:

  • a new subtask is added to an existing issue
  • a subtask changes to a new parent issue
  • the fix version for an issue changes (and any other fields you want to cascaded to children)

Kind regards,

Thanks Bill, that 'hidden' way to use the more simple way to copy Fix versions from trigger issue worked like a charm!

Skärmbild 2023-03-31 091706.png
Funny that Atlassian has implemented the UI so differently for these two fields, but at least now I've found a new way to search for built-in functionality. 

Much appreciated ! 

Just out of curiosity, how could I have implemented the same 'copy Fix version from trigger issue' in JSON code?

Bill Sheboy
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
Mar 31, 2023

I am glad to learn that helped.

In that link I provided, documentation walks through the specifics for updating fields with JSON.  The technique you use depends on if you want to replace or add to the existing values.  Let's assume you want to replace the values in the Subtasks with those from the Story.

The simplest syntax for this is to use the fields shortcut , as shown below.  Again, let's assume the trigger issue is the Story and you want to edit a Subtask...which you have branched to.  Let's also assume there is only one value for the fixVersion.

In the rule's Issue Edit action, you would select More options to add JSON.  When using this method, do not select the field from the dropdown at the top of the action, as you will change it with JSON.

"fields": {
"fixVersions" : [ { "name": "{{"} ]

The fixVersions field is a list and can contain multiple values.  So we add the first function to specifically select that item as we are assuming there is only one.

When you have multiple values to copy/edit, the JSON needs to be a bit more dynamic.  Atlassian has added some other functions to help with that, and you can learn more about them here:

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events