-
Suggestion
-
Resolution: Unresolved
Suggested improvements
- Ability to pull default or custom fields from Jira issue as the options displayed for user input when manually triggered automation rule is run - "I wanted to add a user input field, with a default value populated with values from the actual issue. Couldn't find how."
- Sync values of Jira system and custom fields in automation rule. The idea is to allow user when prompted for input ,user can select option from existing custom field during manual automation.
- Allow usage of Smart Values inside Input Fields' Default Values
- Ability to add multiple options to the checkbox field in the user input
Also when there's is a need to have a default values, allow the smart values.
- Currently Automation for Jira provides capabilities to have user input when executing manually triggered automation rule. When the rule is executed, there is a pop-up to provide values for requested fields. Fields, type of fields and values are defined within the Automation rule, however, there is no option to dynamically provide value options, e.g. via Smart Values. For example, we want to have Affects versions automatically fetched and displayed when running the rule. We configure user input, add Affects Version and set value to issue.versions. But since it is not supported, no values will be fetched and displayed.
- Support for user picker field type, e.g. to select assignee - "If possible I would like to have the possibility to ask the user triggering the rule to select for example the assignee and based on the value entered, the rule would set the assignee, enter a comment and progress the ticket to a specific status. This would be a perfect solution that could be used by a support team to a "First Reply" situation"
- Ability to use the new "userInputs" fields to set custom field value in clone automation - "I have set a single choice droplist question in the manual automation trigger and have it create a smart value - userInputs.Asset.RequestType. Later on in the automation, I have an action to clone the ticket to a different Jira project and would like to use the smart value that I collected at the start of the automation to set a value on a customfield (which is a single select droplist) with the same options as I set in the manual automation trigger. The custom field is a required field so it needs to be filled in as part of the clone action and is not present in the ticket that we are cloning. I was hoping to use this new userInput smart value to set the required customfield curing the clone action. There is no option to choose the custom field and select the userInput smart value"
- is duplicated by
-
- Closed
-
- Closed
-
- Closed
-
- Closed
-
- Closed
- is related to
-
- Gathering Interest
- mentioned in
-
Page Loading...
[AUTO-744] Improve "Manual trigger from issue" to support more ways to capture user input - custom issue fields, user picker field type, ability to access fields via smart values, multi-select fields, date/time fields
I concur with those that already commented on this. This would be a huge benefit for us.
Our team would benefit hugely from being able to pre-populate the manual issue trigger user input fields with data from the issue (via Smart Values). As others have already mentioned here, we need to validate and sometimes modify issue data before sending it to a webhook.
Right now our workaround is to either force the user to copy/paste from the ticket (or manually enter the data), or to use a dropdown or checkbox selection telling them to confirm they reviewed the fields in the ticket and they are all correct. If we could just populate the fields they would be able to see them all in the user input form and correct them as needed. With all the tickets we use this on, this functionality would save us a ton of time. It would also make it much easier for us to prevent data quality issues from perpetuating from Jira issues into other systems.
One of our biggest use cases for this is onboarding automation. We use a manual issue trigger for the IT team to initiate our account creation workflow from an onboarding ticket; the data is sent via webhook. The time it takes for the team to enter data in each user input field adds up quickly when we have a high onboarding volume.
Please implement this functionality as it is a pretty obvious gap in the otherwise very useful manual issue trigger tooling.
We have a need for getting the information from the issues for user inputs, e.g. user can select as user input from the list of customers available on the issues.
Seems like a pretty obvious need for us to be able to capture user input to populate a picklist value when creating an issue via automation
Running into this again and again as our primary use-case is allowing the validation and modification of issue data before sending it to a webhook (i.e. its summary, end date, participant list).
We don't want to modify the issue itself, just use the on-issue data as field defaults to save the user from having to cut and paste it.
Would be a huge win to have smart values in these input fields.
Adding my support for this improvement.