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

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

Avatar

1 badge earned

Collect

Participate in fun challenges

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

Challenges
Coins

Gift kudos to your peers

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

Recognition
Ribbon

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!

Leaderboard

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
4,556,392
Community Members
 
Community Events
184
Community Groups

Unable to recognize the custom field(person)

Unable to recognize the custom field(person) when creating a child ticket

Automation to create child ticket
Screenshot 2023-05-26 141156.png

 

Auto created for child ticket was successful but the custom field does not recognize for person.
other custom field like text was ok.
Screenshot 2023-05-26 141206.png

2 answers

0 votes
Alex Koxaras _Relational_
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
May 25, 2023

Hi @Rodriguez_ Jhon Ronald 

What do you mean that it's unable to recognise it? You mean when you create a child issue that field doesn't get populated with the value from it's parent? Or that it displays the whole JSON string, instead of the display name?

0 votes
John Funk
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
May 25, 2023

Hi Rodriguez,

Check the context for the custom field to see if there is anything restricting it. 

Next, check the name to be sure you typed the name of the field EXACTLY has it is created (it is case sensitive).

Finally, try using the ID for the custom field instead of the name. It would look like:

{{issue.customfield_10456}} where 10456 is the ID of the custom field. You can find that while you are looking at the context for the field by looking at the URL address - it will be at the very end. 

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
PREMIUM
TAGS
AUG Leaders

Atlassian Community Events