Where to find the field variable name

[ali]

Hi everyone,

I am looking for setting up some Automation for issue creation.
The Automation will create a new child JIRA request (not a sub-task) when a parent JIRA request was created, and in the Child request, I am looking to fill some fields based on the corresponding fields in the Parent request,
Such as Summary, which is listed in the automation as {{issue.summary}},

However, something that doesn't listed in the list, where I can find their name? such as a custom file, Personal Email Address, I tried {{issue.personalemailaddress}} which doesn't work.

Just would like to see where I can find all the variable names, so that we can do more with the Automation.

Thanks a lot,

[Kalyan Sattaluri · Accepted solution]

Hello @ali 

Basically there are 2 types of fields.

There are out of the box fields and there are custom fields which your Jira admin has provisioned for your project.

You can reference a field by using exactly how the field is called on the screen. 

So if field is called "Personal Email Address", then to reference it, you use {{issue.Personal Email Address}}

Notice that I included the spaces. If you remove spaces, the smart value will not resolve. So you have to be particular in specifying the name exactly how you see it on the screen.

This should get you most of the way. But some times, for custom fields, referencing screen name will not work, especially when doing advanced edits or if there are multiple fields with same name, just couple of examples.. then you need to reference them by their customfield names. But this depends on use case and fields in question.

To know more about smart values and custom fields, Please read through below article:

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

Hope it helps.

[ali]

Thank you @Kalyan Sattaluri for the documentation link,
It seems exactly what I was looking for.

However, When I tried to follow the instruction and test it, it seems still not working.

Here is what I got.
In the Parent request JSON I found,

In the Automation setup,

Also tried

And

Tested, and got some error.
Here is the Error I got.

Might be I still missing something.
By the way, the Parent and Child Requests are not in the same Project, Parent request is in Project A, and Child request is in Project B.
They use the same Custom Field, so, the field itself shouldn't blocking it.

But I still couldn't find why the value didn't pass down.

Any more suggestion?

Thanks a lot again,

[Kalyan Sattaluri]

Hello @ali 

You need to have this field mapped to the "Create Issue" screen. .

This is part of the set up when customizing new fields.

If you are not the admin, you need to work with one / whoever has access to finish setting up the field correctly.

Please see below article:

https://confluence.atlassian.com/jirakb/unknown-fields-set-during-create-they-may-be-unavailable-for-the-project-type-error-on-create-issue-or-edit-issue-action-in-automation-rule-1116275263.html

[ali]

Hi @Kalyan Sattaluri

When you/the documentation said "You need to have this field mapped to the "Create Issue" screen. ."

Which "Create Issue" screen? in the Parent Project or the Child Project?

Thanks a lot,

[Kalyan Sattaluri]

Child Project.

This is where I am guessing the new issue is being created. Cause this field, though configured, is not available as part of creating the issue.

You can confirm this by trying to create an issue in the child project and see if you can see the field to update manually.

[ali]

Thank you @Kalyan Sattaluri

This solved my issue.

Thanks a lot for your help.

Have a great day,.

[Jack Brickey]

hi @ali , welcome to the Community. Please share a screenshot of your automation, highlighting the areas that are not working. This will allow me to zero in on an answer.

[ali]

Hi Jack,
Thanks for your fast respond.

Here is the screenshot.

Thanks a lot,