Atlassian uses cookies to improve your browsing experience, perform analytics and research, and conduct advertising. Accept all cookies to indicate that you agree to our use of cookies on your device. Atlassian cookies and tracking notice, (opens new window)
Teams
, (opens new window)

Create on Transition for Jira
Results will update as you type.
  • Cloud
  • Data Center
    • Overview - Data Center
    • Installation - Data Center
    • Getting started - Data Center
    • Use cases - Data Center
      • Copy a custom field value to another field - Data Center
      • Determine where COT functions are in use
      • Create a value map using the cascade select configuration
      • Pattern match condition
      • Prevent creating duplicate issues
      • Pattern substitutions for string manipulation
      • Set third party app custom fields while creating multiple issues
      • How are error messages generated during workflow transitions
      • Copy epic and its issues using the Create Issue post function
      • Create a linked issue in another project only if one doesn't already exist - Data Center
      • Create sub-tasks for specific issue types
      • Debug condition configurations
      • Copy attachments to a newly created issue
      • Create and link issue on exact summary match
      • Create issue if transitioned by specific user - Data Center
      • Create multiple issues - Data Center
      • Create multiple issues for each fix version - Data Center
      • Create subtasks on initial issue create
      • Add condition to a blank or an empty field
      • Retrieve problem determination information
      • Define condition based issue creation
      • Link newly created issues on transition
    • Features - Data Center
  • Migration
  • Release notes
  • Upcoming releases
  • Help and support
  • Appendix
    You‘re viewing this with anonymous access, so some content might be blocked.
    /
    Create a value map using the cascade select configuration
    Updated Jun 27

    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.

    Example of a value map

    Key

    Value

    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

     

    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

    Use 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

     

    Need support? Create a request with our support team.

    Copyright © 2005 - 2025 Appfire | All rights reserved.

    {"serverDuration": 16, "requestCorrelationId": "c7bb919e1ef9482f8ef84f07994af2a9"}