Fields Data Value Mapping

Owned by Jeff Gleeson
Last updated: Jan 09, 2024
3 min read

Data values mapping

TFS4JIRA offers the capacity to map data values, extending the customization options for synchronization even further. For example, Jira and Azure work items with a Priority field can have a value attached to set the level of importance of implementing a feature or fix.

Jira sets priority values as Highest, High, Medium, Low, and Lowest; Highest usually indicates the most critical work item.

Azure DevOps sets field priority values numerically, 1 being the highest priority and 4 being the lowest.

For fields that require priority, you can map the Jira priority value to Azure to preserve the priority level for those fields during synchronization.

When you select a field value with a priority component, the Mapping method field appears beside the In Jira and In Azure fields.

  1. Click Add values map to open the Configure values map page.

Automated values mapping

When this option is selected, TFS4JIRA automatically copies a modified value and attempts to convert the value to a different type if needed (for example, when a numerical field is mapped to a string field).

When Automated values mapping is selected, you cannot manually assign values to the field.

Manual values mapping

  1. Click the In Jira field and select a value from the list. Click the In Azure field and select the Azure value from the list.

  2. Click Add mapping.

  3. Continue until you have finished mapping all the values.

To change a mapped item, locate the item in the Mapped Values types list, click on the Jira or Azure value, and select another value from the dropdown list.

To remove a mapped item, locate the item in the Mapped item types list and click the Remove mapping icon.

Default values

Set how TFS4JIRA responds during synchronization when it encounters an unmapped value.

  • Skip - When TFS4JIRA encounters an unmapped value, it skips over it and continues to the next value.

  • Raise Error - When TFS4JIRA encounters an unmapped value, it is recognized as an error. You can review the error in the sync log.

  • Set Value - When TFS4JIRA encounters an unmapped value, it maps it to a specific value. For example, if Medium is selected for Jira, all unmapped Jira values are mapped as medium priority.

  1. Click the Jira field and select Skip, Raise Error, or Set Value from the list of options. If you select Set Item, click the field below the Jira field and select a value.

  2. Click the Azure field and select Skip, Raise Error, or Set Value from the list of options. If you select Set Value, click the field below the Azure field and select a value.

  3. Click Save settings to return to the main Fields page.

Click Save and continue to move to Users.