Syncing Many to Many Projects
This document provides best practices for handling many-to-many projects in Getint, where a single or multiple projects must synchronize with other target projects across apps such as Jira, ServiceNow, Monday, Azure DevOps, and Asana.
The many-to-many projects feature is only available for Jira–Jira, Jira–ServiceNow, Jira-Azure DevOps, Jira-Monday, and Jira–Asana integrations.
How to Sync Many Projects
To synchronize multiple projects, begin by creating an integration as you normally would. Next, choose Jira as the connector on the left side.
Next, either select an existing connection or create a new one. After the connection is set, you’ll see a checkbox labeled “Sync many projects” above the dropdown list.
Select the projects you want to sync, then click “Connect.”
Select the counterpart application—in this example, Jira. Then repeat the previous steps to choose the projects you want to sync.
Click “Start with Mapping Types” to map the work item types.
After mapping issue types, you can start adding fields to them. At the time we’re publishing this article, the “Quick Build” feature is not available for many-to-many projects. You will need to map fields manually.
Defining Conditions in Items Routing
The next step is to define conditions, as routing refers to the path a work item takes across connected systems. By setting clear rules, you ensure Getint knows which project each incoming work item belongs to and what type it should have.
Please follow the next steps to set up the rules for syncing your items, and then review the subsequent configuration steps to confirm that transitions, field mappings, and workflows are properly aligned.
Item routing must be defined on both sides; otherwise, work items will not sync.
Please select the project where the item will be routed and specify its issue type. In this example, we are configuring how items from the right side will sync into the corresponding project on the left.
Choose the field that will trigger the sync. For example, click “+Add New Field” to add conditions across multiple fields. If all conditions are met, the item will sync to the project you are routing it to.
Now repeat the same steps for the right side of the integration. In this case, you are defining how items from the left will sync into the corresponding project on the right as long as conditions are met.
Click “Apply” to submit the changes, then save the integration. After that, test the integration to confirm that routing works correctly and items are syncing as expected.
Removing or Adding Projects to Existing Integrations
You may need to adjust the projects connected to an integration. This can involve adding new projects to expand its scope or removing existing ones to simplify or restructure it. Follow the steps below to make these changes:
Click the box for the side of the app you want to modify. You can choose either side, depending on your goal.
Use the dropdown list to browse your projects and add new ones. You can also remove projects from the integration by clicking the “X” icon next to the project name. This works the same way as when you added or removed projects during the initial setup.
Close the tab and save the integration to submit your changes.
You need to define new conditions to route work items to any project you’ve added.
Conclusion
Managing integrations is not a one‑time task but an ongoing process. Whether you are adding new projects to expand collaboration or removing existing ones to simplify workflows, the key is to define clear routing conditions and test thoroughly. By carefully mapping fields, setting rules, and validating sync behavior, you ensure that work items flow correctly between systems.
Need more help? Visit our Help Center or reach out to support by clicking the chat bubble for direct assistance.
Last updated
Was this helpful?