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

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.

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"