How to use a cascade select configuration to provide a value map

Description

Substitution variables are great to set fields in your issue to various things. What if you want to set a field to a value based on 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 a non-typical way. CSOT-103 has more details on the configuration access capability used in this example.

Value Map - Example

Key

Value

Key

Value

joe

joe@xxx.com

sally

sally@xxx.com

Configure Cascade Select

Step

Example

Step

Example

1

Create a cascade select custom field

  • Field is not intended for use

  • It is just for saving configuration values

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

Using Substitution Values

Suppose your cascade select custom field is called: myMap

Example

Result

Example

Result

%values_myMap(joe)%

joe@xxx.com

%values_myMap(sally)%

sally@xxx.com

%values_myMap(%entry%)%

  • when using multiple issue creation

  • processing the sally entry

sally@xxx.com