The Team field mapping can be configured per Jira project.
To use a different team field mapping, you have to create a separate field mapping for a Jira project. Even if the only discrepancy between the general configuration and a project configuration is just one field.
Switch to the "Custom mapping" tab to configure mapping per Jira project. Settings are created per Jira project (not per box).
Either add a new project and create a configuration or modify the existing one.
The App does not support assigning multiple Teams to a task. In the case of multiple labels, the App will assign the task to the first team in alphabetical order.
When a task with multiple team labels is reassigned using the App, all other team labels will be removed.
Supported Field Types
You can sync team assignments with any custom field of the following types:
- "Select list (single choice)"
Example of fields with values:
When using labels, the App can automatically generate a Team label when a Team is assigned to a task. You can assign a Team manually by adding a label that must include the 'team#' prefix before the Team code.
Even though labels are convenient, they are prone to human error, such as typos. We recommend using the dedicated "Labels" type field, as the native Jira "Labels" field might be used for other purposes.
Select list field
In the case of select list fields, you must predefine the select options using the Team codes. This can be done by Jira admin only in Jira administration (settings) > Issues > Custom fields > (Your Team field) > Configure:
Field Data Migration
When a field that's different from the one currently used is selected, the option to migrate data will appear below the filed picker:
Data migration of a particular issue can fail in the following cases:
- When migrating from a single select field to a labels field: team code contains whitespaces.
- When migrating to a single select field: a field does not contain the team code in the list of select options (the app does not create the select options during the migration process).
Data migration happens in the background, so the user might not be aware of that process. Depending on the number of issues that call for an update, it might be time-consuming. We recommend performing such migration during a Jira maintenance session.