Request input from users when a Manual rule is triggered

[Andrea_Lawrence]

"You also have the option of accessing each input as a smart value in other actions and conditions."

What actions and conditions can the prompted input be used in? I've been able to use it with the "Send Email" action in the message body but I've been unable to use the prompt fields in any conditions.

Example - prompt includes dropdown select value

Condition - if dropdown value = A

[Tom Hudgins]

Seems to work for me. I created this prompt for a dropdown value

Then I added an if/then block and tested the value.

And logged the value

and it seemed to work fine.

[Scott Youchah]

I attempted to use this new function to create a ticket in a sperate project and it worked.  I also thought that I would be good to give my users the summary line from the originating issue as the default value to work from. Do I assume that this default value screen does not interact with smart values? Otherwise maybe I've tried to implement it incorrectly. 

[Angela Salunga]

I have an automation rule that would ask for manual input but values should be selected from JQL query. How can this be done?

[Darryl Lee]

@Angela Salunga Because I'm a glutton for punishment, I feel like you could maybe get the values into Smart Values using the Automation for Jira - Send web request using Jira REST API trick, BUT I would bet that User Inputs probably does not support using Smart Values for the options.

OH, and nevermind because you can't have a web request run before the trigger, so ... that kind of removes that possibility.

I guess I'm going to say no then. Cool idea though.

[Andrea_Lawrence]

It is indeed unfortunate that smartvalues cannot be used for default values in user input fields.

[Rosa M Fossi]

Hello Team, Thank you for this addition...  It's a good enhancement, but as some stated, I would've expected access to existing fields (perhaps while configuring the "Prompt for Input" option in the automation, we could select the relevant Field Scheme?).  

Use case: We have a manual trigger to create issues in a Software project from the Service Management project. Right now, despite the automation, the user has to open the ticket and finish filling it out and make a few adjustments. 

Why not simply "create linked ticket" you ask? Because some of the information is being copied between non-matching fields between the two projects, some reporters in SM cannot be reporters in the Software projects, and we additionally summarize some of the content in desc, and automation takes care of adding some labels based on some criteria and adding comments to the trigger ticket.

Another useful input option is an user-picker that could be narrowed down by group. 

This new Prompt for Input option has already been useful, and I look forward to its growth!

[Ankur Patel]

I am still not able to use this feature in my jira instance. I am still using JIRA DC and I can't see the mentioned option.

[Tom Hudgins]

@Ankur Patel this is a Cloud feature. Doubt they are going to be adding things like this to Jira DC.

[Kristján Geir Mathiesen]

Great new feature! Thanks.

[Julian from AF]

Hello! Is it available on Datacenter ? Thank you 

[Paul Collis]

Hi Community,

Am using this function in my automations, users are inputting notes which are being included in an email.  When they are using html tags this is making the email format nicely, however I've also set the flow to capture the notes in the comments section which then has the html tags rendering as text.  Is there any way that I can use something like the below but on these {{userInputs.smartValueName}} variables?

{{issue.summary.remove("<br>")}}

 Thanks for any help.

[Darryl Lee]

Hi @Paul Collis - try this:

{{userInput.notes.text}}

https://support.atlassian.com/cloud-automation/docs/convert-wiki-markup-to-html-or-plain-text-in-jira-automation/#rendering-html 

(This really should be documented here: https://support.atlassian.com/cloud-automation/docs/jira-smart-values-text-fields/)

[Paul Collis]

@Darryl Lee That looked so promising!

The comment then didn't output any of the text from that field.  Will keep playing.

[Darryl Lee]

@Paul Collis Drat. Yeah I should've tested. Trying to "clean" out HTML using replace is tricky.

[Bill Sheboy]

Hi, @Darryl Lee -- Most of the times I see a similar question related to stripping off some form of markup like  HTML, the eventual answer is: call a REST API function which can do that for you, outside of the rule and Jira.

[Darryl Lee]

Hi @Paul Collis - Oh wait. Your users are inputting HTML? You need to tell them to STOP DOING THAT. 

I'm pretty sure putting HTML in any Jira field is going to cause you pain and suffering later.

I just put the following test data in a user input field of type Paragraph:

Here's the notes:

This is a note.

It has paragraphs.

* Bullet
* Points
* Not
* Really

_What about underlines?_

It's not "pretty", but it has line breaks (why are they inserting <br>s??) and the content is there.

But I guess what's more interesting is this is how it looked as a Comment:

This is a note.

It has paragraphs.

• Bullet
• Points
• Not
• Really

What about underlines?

But yes, confirmed sadly that adding .text and .html to the smart values do NOT render plain text or HTML. Bummer. I guess we can file a feature request?

So, what have we learned?

• Paragraph fields will accept wiki markup.
• The paragraph fields will render nicely as comments.
• As email, they render as... markup.

[Paul Collis]

Thanks @Darryl Lee

I'll heed your warning. 

The flow I've got takes user input and the puts that inside an email that is already HTML formatted.  So when they enter into the paragraph box, all the formatting is lost within the email but retained when it also saves it as a comment.

When they add HTML tags in their input, the email is then formatted as expected but the comment has the tags in it.  Lose lose situation really.

Lets see what the future may bring :-)

[Andréas Johansson]

Is it possible to use smart values in the form? I want an automation that creates a new issue that is linked to the current issue (the one the automation is manually triggered on so to say). It would be great if the form the user gets could use smart values in the default values, such as the key/summary of the triggering issue.

Is this possible? I tried adding {{issue.key}} in the default value, but it did not work as I expected.

[JammeTan]

What is the proper way to get the value a checkbox input field in an automation conditional?

Regardless of whether checkbox is checked by the user when triggering the automation, the checkbox smartvalue {{userInputs.checkboxValue}} returns as the name of the field, not whether it is checked or not. 

I tried using {{userINputs.checkboxValue.value}} and that seemed to break the automation as no other conditions were checked after that. 

[Tom Hudgins]

Checkboxes work for me.

Here is my input definition

Here is where I log the value of the checkbox in my rule

Here is the result when I don't check it

Here is the result when I do

Here's an if test of the value.

[sarend]

I'm trying to create an automation that creates a bug on a manual trigger. We require the originated environment field to be filled in when a bug is created so I want to use the user input smart value to fill in that field. I have duplicated all of the possible environment options in the user input field (with the exact text as the main field). I am pretty sure the smart value is the issue because it works when I use text of one of the environment options. Does anyone have suggestions for what I need to change here?

[Bill Sheboy]

Hi @sarend 

You seem to be using the update syntax for a multi-select field.  Is your environment field single or multi-select?  If it is single-select, perhaps try this:

{
  "fields": {
    "customfield_10156": { "value" : "{{userInputs.OrgEnvInput}}" }
  }
}

And also...please confirm that the value in your user input field exactly matches the name, spacing, and case of the value for your custom field.

Kind regards,
Bill

[sarend]

@Bill Sheboy My field was single select. Your change worked, thanks very much for your help!

[Ines B.]

will this be coming to Data Center too?