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.

What You'll Learn Here:

  • Basics of field mapping on our platform

  • How to set up a new mapping

  • How to remove a mapping you don't need anymore

  • How to change the integration direction

  • Understanding why some directions can't be changed

  • Tips for customizing an existing mapping

  • Special settings for when you create or update something

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 makes sure 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:

While some fields like Title, Description, Status, and Comments are easy to match across platforms, others might need a bit more thought. For instance, Azure DevOps uses "Area Path," while ServiceNow uses "Assignment Group." Tools like Jira have many fields ready to use, whereas Monda starts with just a few. Sometimes, you'll need to set up your tools before starting. After that, you can pick and choose fields to map using our clear interface.

Think of it like building a dictionary where some words are the same across languages, but others are very different. Our client Andreas put it well: setting up an integration is like making two people who don't speak the same language talk to each other. Getint helps them understand each other better.

Starting with a Custom 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:

  1. Begin by selecting Jira.

  2. Choose the Jira field you wish to integrate—“Assignee.”

  3. Then, select Azure DevOps as the second application.

  4. Finally, choose the “Assigned to” field and click the “Add” button.

Removing a Field Mapping

To get rid of a mapping that's not working for you, just hover over it and click the delete icon. This won’t mess up 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

For fields like Assignee, Priority, or Status, you’ll see a warning icon 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.

  • Handle empty values: Set a default for when there’s no info to fill a required field

Mapping Special Fields

Some fields, like the Reporter 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 here.

Last updated