/
Create a value map using the cascade select configuration
Create a value map using the cascade select configuration
Description
Substitution variables are of great help when it comes to configuring field values for issues. Want to use a field value using a value map? For instance, you want the Jira user to see one value on the screen, but internally, you need a different value to be set in a custom field. How can this be done easily? This shows how to do this using a cascade select configuration in an non-typical way. CSOT-103 has more details on the configuration access capability use in this example.
Example of a value map
Key | Value |
---|---|
joe | joe@xxx.com |
sally | sally@xxx.com |
Steps
The following steps demonstrate how to configure Create on Transition, regex inspection of the project using a built-in function:
Step | Example | |
---|---|---|
1 | Create a cascade select custom field
| |
2 | Add a parent entry with the key value of your map | |
3 | Create a child entry with the value part of your map | |
4 | Repeat for each key and value pair |
Use substitution values
Suppose your cascade select custom field is called: myMap
Example | Result |
---|---|
%values_myMap(joe)% | joe@xxx.com |
%values_myMap(sally)% | sally@xxx.com |
%values_myMap(%entry%)%
| sally@xxx.com |
, multiple selections available,
Related content
Field values
More like this
Define field values for new linked issues
Define field values for new linked issues
More like this
Context transformations
Context transformations
More like this
Using Autocomplete
Using Autocomplete
More like this
Use autocomplete
Use autocomplete
More like this