Sub Task Automation Custom Fields Blank

Question

Hey all,

I'm racking my brain and I've scoured the help here to no avail - I cannot determine how to get fields from a parent to a sub-task as part of automation.

I have an "On Issue Created" automation that I want to create a number of sub-tasks. This issue type I have limited for the automation has a number of custom fields associated with it.  As an example, one of these is "Employee Full Name".

I've tried *ALL* of the following to try to get that field as a variable into the sub-task generator, and all of them show up blank. What am I doing wrong??

# {{Employee Full Name}}
# {{Employee Full Name.value}}
# {{"Employee Full Name"}}
# {{"Employee Full Name".value}}

*fields.*

# {{fields.Employee Full Name}}
# {{fields.Employee Full Name.value}}
# {{fields."Employee Full Name"}}
# {{fields."Employee Full Name".value}}

*issue.*

# {{issue.Employee Full Name}}
# {{issue.Employee Full Name.value}}
# {{issue."Employee Full Name"}}
# {{issue."Employee Full Name".value}}

*issue.fields.*

# {{issue.fields.Employee Full Name}}
# {{issue.fields.Employee Full Name.value}}
# {{issue.fields."Employee Full Name"}}
# {{issue.fields."Employee Full Name".value}}

*issue.parent.*

# {{issue.parent.Employee Full Name}}
# {{issue.parent.Employee Full Name.value}}
# {{issue.parent."Employee Full Name"}}
# {{issue.parent."Employee Full Name".value}}

*issue.parent.fields.*

# {{issue.parent.fields.Employee Full Name}}
# {{issue.parent.fields.Employee Full Name.value}}
# {{issue.parent.fields."Employee Full Name"}}
# {{issue.parent.fields."Employee Full Name".value}}

*parent.*

# {{parent.Employee Full Name}}
# {{parent.Employee Full Name.value}}
# {{parent."Employee Full Name"}}
# {{parent."Employee Full Name".value}}

*parent.fields.*

# {{parent.fields.Employee Full Name}}
# {{parent.fields.Employee Full Name.value}}
# {{parent.fields."Employee Full Name"}}
# {{parent.fields."Employee Full Name".value}}

Andrew Vaughan_n5qryl · Answer

Thanks, Bill - I expected those to work, too, and they did not.  I've double and triple checked the case; unfortunately, no dice.

I'll double-check the API in the morning, but the characters I posted was basically an example of me banging my head against the wall as I tried everything I could think of (including looking up the smart values). Will accept the answer or write back in the morning - thanks!

Bill Sheboy · Answer

Hi @Andrew Vaughan

I am unclear about some of the extra characters in what you posted, and...

* If you have a custom field named Employee Full Name which is available within an issue's scope...
* Usually one of these will work:* {{issue.Employee Full Name}}
* {{issue."Employee Full Name"}}

Smart values are case-sensitive, so I suggest finding an example issue with your field filled in, and then try the instructions in this how-to article to confirm the smart value name.  Basically, you call the REST API from a browser and then search for your field name and the data contents to confirm the name.

https://support.atlassian.com/jira-software-cloud/docs/find-the-smart-value-for-a-field/

For some automation syntax, you will still need to use the custom field ID rather than the name, so this technique will also find that information.

Best regards,
Bill