Learn how to map options of the fields with defined values, such as Select Lists, Radio Buttons and User Pickers.
Deviniti’s Rovo Assistant provides access to a virtual assistant that helps you with configuration, installation, and troubleshooting, enabling quicker and faster navigation through documentation. See Deviniti’s Rovo Assistant documentation or find it on the Atlassian Marketplace for more information.
By default, field options are being synchronized only when they match its other values exactly (the value of each synchronized field is the same).
This behavior may be overwritten by setting exceptions to this particular rule.
Keep in mind, that setting exceptions to field options is supported in fields of types listed below:
Fields of single choice type can be synchronized with each other, regardless of their type. For example, fields of Select list (single choice) type can be synchronized with Radio button fields
When creating a new mapping:
Field options are configured and mapping is created. Now selecting a particular option in project A will result in substituting selected option in project B.
When editing an already existing mapping:
Field options are configured and changes are saved.
For Select list (single choice), User picker (single user), Group picker (single group), Customer Request Type Custom Field and Priority fields, you can map the Any value option:
Any value is treated as any option entered by user, or a field with a predefined value.
It behaves based on the direction of the synchronization:
During mapping configuration, you can map “Any value” in the Priority field option. This will lead to synchronization of any value of the Priority field on the left side, to a particular value provided on the right side.
In that case, creating an issue on your Jira with any value in Priority field will result in creating an issue on your partner Jira with the Highest priority
If you can’t find the answer you need in our documentation, raise a support request.