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

Next challenges

Recent achievements

  • Global
  • Personal


  • Give kudos
  • Received
  • Given


  • Global

Trophy case

Kudos (beta program)

Kudos logo

You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.

View group

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

How i can copy Select List (cascading) field from parent to sub task in cloud version

Hi there! 

As usual, I ran into an incomprehensible situation, I can not figure out whether it is possible to copy "Select List (cascading)" field through automation, because these fields are simply not available? I use Jira Cloud version.

Any idea why this is so?

Thank you! :)


2 answers

1 accepted

0 votes
Answer accepted

Hi @Petr 

Cascading select list is probably not yet supported directly.

There is indeed a documentation, you can read about smart values here. I am am also making videos on this covering this topic.



Also if you want to set the cascading select list value you can use this JSON in the additional fields.

"fields": {
"Cascading Select List": {
"value": "{{issue.Cascading Select List.value}}",
"child": {
"value": "{{issue.Cascading Select List.child.value}}"

This will also set the sub task cascading select list value from parent.


Like Petr likes this

@Ravi Sagar _Adaptavist_ 
Thanks for the links, yes, I looked in this documentation, but I never met about the child field.
I saved your blog, see more details!!)

If you saw my question, do you think is it possible to get a comment from satisfaction, or an rating in a similar way, for lookup issues, as you indicated above, otherwise I have not figured it out? 
Angelica helped me with it, but maybe it possible to write it using JSON, idk?


And there is 1 more thing. 
I can't send email with this field's information:
I've tried this:

1 {{issue.fields.test_cascad.value}}
2 {{issue.fields.test cascad}}
3 {{issue.fields.test_cascad}}
4 {{issue.fields.test_cascad.values}}

In the first option i get only the first part of this field
in the second and third option I get this

{self=, value=test, id=10999, child={self=, value=test11, id=10888}}

When I try to get the value from the IDs obtained above, nothing comes out.
1.1 {{issue.customfield_10999.value}}
1.2 {{issue.customfield_10888.value}}

What do you think about that?

Hi @Petr 

Do this.

Parent value: {{issue.fields.test_cascad.value}}

Child value: {{issue.fields.test_cascad.child.value}}

You are indeed getting a JSON where you can access both parent and child values separately.

I hope it helps.


Like Petr likes this

Hi @Ravi Sagar _Adaptavist_ 

It works great!!
Thanks you for the help!!

Do you know why this field is not in automation in the field list?)
Can you tell me, did you learn about this function from personal experience, or is there documentation? Maybe I am missing some page that could help me with such unusual requests.



Suggest an answer

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

Why upgrade to Jira Service Management Premium?

We often have questions from folks using Jira Service Management about the benefits to using Premium. Check out this video to learn how you can unlock even more value in our Premium plan.  &nb...

189 views 1 6
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