Mapping Multiple Statuses to One (N to 1) in Getint

When setting up an integration in Getint, users often want to consolidate several different statuses from the source system into a single status in the destination system. This is referred to as N-to-1 status mapping (many-to-one).

For example, you might want to map To Do, Ready, and Open from Jira to a single Active status in Azure DevOps.

This guide explains how to configure N-to-1 status mappings effectively, avoid common mistakes, and ensure smooth synchronization.

Why Use N-to-1 Mappings?

You might want to reduce complexity in the destination workflow, align with a simplified status model, or maintain a consistent reporting structure across tools.

Common scenarios include:

• Unifying multiple "open" states from a detailed workflow

• Migrating from a granular system (e.g., Jira) to a simpler one (e.g., Trello or Monday.com)

• Avoiding sync failures due to unmapped statuses

How to Configure N-to-1 Status Mapping

Step 1: Open Your Integration

• Open your Getint app and navigate to your integration.

• Select Edit and go to the Status Mapping section.

Step 2: Add a Status Mapping Rule

• Open the status mapping screen and locate the left-side dropdown.

• On the right side, select the corresponding target status that should receive the mapped value.

• To add more statuses from the source side to the same target status, select another source status and click the +Add option here.

• Both source statuses will now be mapped to the selected target status.

• By default, the first mapped status is treated as the default. This means that in a bidirectional sync, the source side will always use this default status when syncing values back from the target side.

• To change the Default status, click on Set Default on the side of the mapped status.

Step 3: Repeat for Each Source Status

Repeat the above step for each additional source status that should point to the same target status.

Repeat the above step for each additional source status that should point to the same target status.

Important: It is only possible to map each status once, and only in a many-to-one configuration.

Best Practices

• Check workflows: Make sure your target system accepts transitions into the chosen status. Some systems have workflow constraints.

• Test mappings: Use the integration logs to validate your mappings after enabling and running the sync.

Troubleshooting N-to-1 Mapping Issues

Problem: Status Not Updating as Expected

Cause: The destination status might not allow incoming transitions from all mapped source statuses. Solution: Review the destination tool’s workflow rules and allow the necessary transitions. We recommend reviewing our doc, Simplifying Workflow Sync with Getint: Jira, which should help to ensure a block-free workflow.

Problem: “Unmapped status” Warning

Cause: A source status was not included in your mapping. Solution: Go back to Status Mapping and add the missing status manually.

Configuring N-to-1 status mappings can simplify your synchronization process and help align differing workflows across platforms. However, it's essential to define each rule deliberately. Each status can only be mapped once, and mappings must follow a many-to-one structure.

Before finalizing your setup, double-check that each mapped status aligns with your destination workflow’s transition rules and that all relevant statuses are accounted for.

Still have questions or need support with your configuration? Visit our Help Center for expert assistance.