Make it easier to work with smart values, e.g. for custom fields - suggestions in product, validation / autocomplete (automatically populate) for all fields that support this, add a simple UI to iterate over field values for common use cases

Add a simple UI to iterate over field values

Ability to access smart value variables as their underlying type

https://codebarrel.atlassian.net/browse/AUT-81 is now possible by looping over smart values so you can do {{issue.components}}

It'd be great to build a nicer UI on this for common use cases

• For each version - send a webhook
• For each component - create a sub task
• For each user in custom field - send an sms
• For each checkbox selected - create an issue
• For number field create a sub-task for each
• For each comment, perform an action.
• For each request participant, add as customer

For any given component, provide examples of relevant smart values in the product.

It would be nice to auto fill / suggest smart fields and make finding required fields easier, e.g. showing preview of final email.

Smart value picker

We know the list of issue fields available so we should be able to do a type ahead auto-complete dropdown as soon as the user types something like

{{issue.

.

This take a lot of the guesswork out of smartvalues.

Should also be able to deal with iterations like

{{#issue.fields.components}}{{name}}{{/issue.fields.components}}

***

Issue Description

We currently have multiple documents describing various ways to access a custom field using smart values:
https://support.atlassian.com/jira-software-cloud/docs/find-the-smart-value-for-a-field/
https://support.atlassian.com/jira-software-cloud/docs/use-smart-values-to-access-listed-values/
https://support.atlassian.com/jira-software-cloud/docs/what-are-smart-values/

However, the methods provided in these documents differ, and also do not include all the ways the custom fields can be accessed. This can lead to confusion and make it difficult to figure out the best way to access a custom field's value in a given use case.

For example:

• One documentation says that the following smart value can be used:

  {{issue.My custom field name}}
  

• Another documentation says that the following smart value can be used (assuming that the custom field ID is 11000)

  {{customfield_11000.value}}
  

In fact, there are many ways to access the same custom field:

{{issue.fields.customfield_11000}}
{{customfield_11000}}
{{issue.customfield_11000}}
{{issue.My Custom Field Name}}

Suggestion

Consolidate all the different ways a custom field can be accessed into one single documentation, in order to avoid confusion.

***

Please add the available smart values for the Project property in the Automation public documentation.

ie.
It is possible to access a project property via the following

{{issue.project.properties.MyPropertyName}}

or

{{project.properties.MyPropertyName (for project triggers)}}