How to read First & Last Name of the Onboarding User to spawn the Onboarding Issues?

suneel babu January 6, 2025

Dear Community,

First of all, I would like to wish you Belated Happy Christmas & New Year too. 

Then Coming to my Query, Initially , I had a Automation rule in which reads the Jira forms to read the variables in the forms ,I've used this "

{{issue.properties."proforma.forms.i1".state.answers.1.text}}"

But now, I suspect that, It has been changed to some other way to read the  variables in the forms, The automation has not been working as expected, earlier its worked fine & did create the onboarding issues as well,

Can any body help in this regard, that would be much appreciated.

thanks in advance, 
Regards,
Suneel Babu

2 answers

1 accepted

6 votes
Answer accepted
Jovin
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
January 6, 2025

Hey @suneel babu 

I find the best thing to do when working with forms is to link the fields to Jira fields in the back end. Depending on how you have your first/last name setup you can then do 1 of two things to access this.

Option 1 - Two fields

On the form create a "First Name" and "Last Name" field, link these to Jira fields (you can name them whatever you wish), for ease I'll call them the same thing. Then to access that information you can just go:

{{issue.First Name}} {{issue.Last Name}} or use their field IDs, {{issue.customfield_10xxx}} etc.

Option 2 - One field with Split

On the form create a single "Name" field, then link that to a Jira field (I'll assume the same name). You can then use the Split() function on it to get the first and last names.

{{issue.Name.Split(" ").first()}} and {{issue.Name.Split(" ").last()}}

Note the above example only accesses the first "word" before a space and the last one, if they input multiple spaces (e.g. John Robert Jones) you'll only get John and Jones, ignoring the Robert. You can find out more about working with lists and split here:

Split: https://support.atlassian.com/cloud-automation/docs/jira-smart-values-text-fields/#split-String-separator- 

Lists: https://support.atlassian.com/cloud-automation/docs/jira-smart-values-lists/ 

suneel babu January 6, 2025

Hi @Jovin ,

Thanks for your Suggestions,

I've Tried Option  1 and its working  fine. But the automation rule did not follow the condition which it worked earlier, FYI

image.png

Here , If Type of hire does not equal to Offsore (Option4).. It should not creates some of the tickets . Assign computer equipment & Assign Phone Number Like that .

But it does not follow the condition & Spawning the tickets as well
I've checked the logs . FYI
image.png

Can you please guide me in this case ??

Regards,
Suneel Babu

Jovin
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
January 6, 2025

Hey @suneel babu 

Rather than using Smart Value condition, try using "Issue field condition" and choosing "Type Of Hire", then you can specify "is not" and choose "Offshore".

1 vote
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.
January 6, 2025

Hi Suneel,

You can now use direct access to the fields in the forms in automation rules. Here is an article that will help guide you. 

https://community.atlassian.com/t5/Jira-articles/Forms-Automation-Access-form-fields-with-smart-values/ba-p/2862665

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events