Configuring Lookup Mapping

By default, the mapping matches the base tracker configurations. Your tracker may be configured specifically and differ a lot from the base version.

Start by mapping priorities, task types, and their states.


A mapping between lookups looks like this:

"mapping": [{"submitted":"New"},{"planned":"In progress"},{"resolved":"Resolved"}{"submitted":"*"}]

This is a mapping of Issue states. In each pair of values, on the right are the state names in the tracker, on the left is the code name in ALM.

Code (or reference) names are available in the lookups. For states, for example, turn on this column in the state list settings:

Below are links for getting lookup names in various trackers:

JIRA Redmine
Priority https://jira.atlassian.net/rest/api/latest/priority https://redmine.openpne.jp/enumerations/issue_priority.json
Issue state https://jira.atlassian.net/rest/api/latest/status https://redmine.openpne.jp/projects/op3/issue_categories.json
Issue type https://jira.atlassian.net/rest/api/latest/issuetype https://redmine.openpne.jp/issue_statuses.json


Users are mapped by email. Create the user accounts before synchronization.