nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Automation Manually Triggered-"Variable Name"

Caressa

Hey we're creating a manually triggered automation in JWM and we want to use the "Prompt for input when this rule is triggered" feature so that users are prompted to fill out specific data on the issue that will be created but we're having issues with the the field.

Is this featured meant to create a new field on the issue or is meant to reflect an already existing field on the issue?

We tried to put a test field under field name but that value did not appear anywhere on the issue.

I then tried to use the name of an existing field on the issue type but the automation failed and I'm not able to see an audit log failure.

In the variable name we're using the suggested

{{userInputs.{{userInputs.{{userInputs.smartValueName}}}}}}

What am I doing wrong?

atlassian com.png Screenshot 2024-03-25 120753.png Screenshot 2024-03-25 120718.png

Accepted answers

Joseph Chung Yin

@Caressa -

Welcome to the community. I agreed with @Mikael Sandberg stated, you can just use the same name as the field name in the smartvalue syntax. Take a look at a similar ask in the past - https://community.atlassian.com/t5/Automation-questions/How-to-use-the-new-quot-userInputs-quot-fields-to-set-custom/qaq-p/2390932

Hope this also helps.

Best, Joseph Chung Yin

Jira/JSM Functional Lead, Global Technology Applications Team

Viasat Inc.

All comments

Mikael Sandberg

Hi @Caressa,

Welcome to Atlassian Community!

The input prompt is unrelated to any fields on your issue, but you could use the value that user puts in as a value for a field on it.

Looking at your screenshots it looks like you overcomplicated the manual trigger. Here is an example of a rule I just created:

Screenshot 2024-03-25 at 1.58.10 PM.png

I suspect that it is the variable name that is causing your automation to fail. As you can see in my example I just used the same name as the field/display name, and you can then use that by using {{userInputs.something}} to set a field on the issue if you like.

Joseph Chung Yin

@Caressa -

Hope this also helps.

Best, Joseph Chung Yin

Jira/JSM Functional Lead, Global Technology Applications Team

Viasat Inc.

Caressa

I attempted this but it was unsuccessful. The field value does not populate in the created issue

Mikael Sandberg

How do you populate the field value?

Mikael Sandberg

It should be pretty straightforward, I expanded my test from above so that it will add the input to the description. Here is what it looks like when I run it:

Screenshot 2024-03-25 at 4.22.38 PM.png

And this what it looks like after

Screenshot 2024-03-25 at 4.22.59 PM.png

And this is what the edit issue field looks like:

Screenshot 2024-03-25 at 4.26.05 PM.png

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

jira-service-management-cloud

jira-service-management