How to Map Fields
Improve Your Workflow with Precise Field Mappings
Unlock the full potential of integrating work items like tasks, bugs, service requests, and incidents across different platforms with our new Getint Field Mappings feature. This tool is designed to fit your workflow perfectly, making it easier to keep everything in sync. Let's dive into what this feature offers.
Understanding Field Mappings
Field mapping is all about linking important details of your projects, like titles, descriptions, who's in charge, and any attachments, across different tools. Our platform ensures these details match up between all sorts of work items—whether they're tickets, incidents, service requests, bugs, or contacts. This keeps your data in sync almost in real-time.
Here's how you can see this in action on our platform:
Starting with Manual Field Mapping
If you're missing a key piece in your mapping, the + Add field mapping button is there to help you find the right match.
Let’s say you're linking the Assignee field in Jira with the Assigned to field in Azure DevOps. Here's how easy it is:
Begin by selecting Jira.
Choose the Jira field you wish to integrate—Assignee.
Then, select Azure DevOps as the second application, choose the Assigned to field, and click the Add button.
Removing a Field Mapping
To remove a field mapping that's not working for you, just hover over it and click the delete icon. This won’t delete or modify any of your data.
Changing How Data Moves
With Getint, data usually moves back and forth between tools by default. But you can adjust this any way you like. Want to send data only one way? Just click on the arrows to set it up.
Handling Dropdown Fields
You'll see a warning icon for fields like Assignee, Priority, or Status if they need more detail. Hit the cog icon for more options.
Map options directly: Link specific options from one field to another, like matching Jack Smith in Jira to Jack Smith in DevOps.
Use default mapping: This is great for sending dropdown info to a text field without needing a detailed map. It just turns the dropdown choice into text.
Concatenating Fields
Starting from version 1.75, Getint will now allow the synchronization of multiple fields into a text-based field like the Description or the Title. This will be possible by clicking the Merge fields checkbox above the field mappings.
How to Merge Fields:
Select the side that you want to integrate and tick the merge fields checkbox.
Now, integrate fields into the text-based fields. Click the +Merge here option to integrate your selected field.
In this case, we'll merge the Assignee and Priority fields with the Title (Jira) and the URL field with the Description field. This means that every time a ticket is created or updated, it will transfer the Title from the issue and include the current Assignee and Priority. Additionally, we're merging the Description with the URL, which will bring the URL from the task to the other side of the integration. However, some fields, like the URL from the task, only sync when the item is created, as this is the only time the URL field is triggered for synchronization. We're using a Jira Azure DevOps integration as an example, but this applies to other integrations as well.
Merging fields operate unidirectionally, meaning synchronization occurs from only one side. Consequently, the Title on the opposite side cannot be synced with other fields simultaneously.
You can make different combinations as long as you don’t surpass the character limit for the text field on the other side.
Certain fields, like URL or ID, only sync during creation, as this is the only time when these fields are triggered for synchronization. As a result, updating existing items will not transfer the URL of the issue to the corresponding field you are syncing with.
Click Apply and Save your integration.
Mapping Special Fields
Some fields, like the URL or ID, can't be changed directly. To map these, you might need to create a special field on the other side first. Then, you can link them up. Read more in the following article: Storing Reference IDs/URLs Across Integrations.
Conclusion
As we've demonstrated, integrating fields in a unidirectional manner allows for smooth and consistent updates. However, it's important to note that certain fields, like URL or ID, only sync during creation, emphasizing the need for careful planning and implementation.
We hope this article has provided valuable insights into the steps of merging and mapping fields. If you have any questions or require further assistance, please do not hesitate to reach out to us. Our team is always ready to help you achieve a more efficient and effective data management system.
Last updated
Was this helpful?