Assignees (users) mapping
Mapping users across different IDs is crucial for synchronizing Assignee fields accurately. For instance, in Jira Cloud, a user might be identified by an account ID hash, while in Jira Server, it could be a username. Similarly, in Asana, users may have different IDs. To properly synchronize these fields, we manually identify which user represents the same person. For example, James Farrell might be named James in Jira and James F in Asana. Without proper mapping, Getint cannot automatically interpret that these are the same user.
How to map assignees
Go to your integration and open your type mapping.
Click on + Add Field Mapping and select the corresponding option for Assignees in every app.
Click on your new Assignees mapping, and scroll down to Map available options. Make sure to select the options that represent the same user. Click on Apply to save your mapping configuration. Then, click on Save to persist with your changes.
If a user was not found on the mapped options list, please verify you’re selecting the correct field for Assignees depending on your app, and confirm that the users exist for both instances. For example, other apps have the Assignee named Assigned to or Owner.
How to set default users
With Default mapping, you can designate a specific user or value as the primary assignee for both instances. For example, when synchronizing tasks through your integration, you can ensure that all tickets from Asana are assigned to Carlos in Jira, and all tickets from Jira are assigned to Julian in Asana.
Copying mapped users from one type mapping to another
This feature allows users to effortlessly transfer mapped users from one type of mapping to another within the integration settings. Easily replicate user assignments from one app to another, streamlining your workflow and ensuring consistency across platforms.
Last updated