# Many-to-One IFS to DTP Jira Integration Using a Common Exalate Connection
**URL:** https://community.exalate.com/t/many-to-one-ifs-to-dtp-jira-integration-using-a-common-exalate-connection/8396
**Category:** General Questions
**Created:** [September 24, 2026, 12:39pm UTC](https://community.exalate.com/t/many-to-one-ifs-to-dtp-jira-integration-using-a-common-exalate-connection/8396 "2026-09-24T12:39:21Z")
**Posts on this page:** 3
**Page:** 1
### Author:  [@pramak1X](https://community.exalate.com/u/pramak1X)
#### Post date: [September 24, 2026, 12:39pm UTC](https://community.exalate.com/t/many-to-one-ifs-to-dtp-jira-integration-using-a-common-exalate-connection/8396/1 "2026-09-24T12:39:21Z")
Hi Team,
We are using Exalate on **Jira Data Center**. We need to sync issues from many different projects to our external system.
Our expected setup is a **many-to-one integration model** , where multiple IFS Jira projects (Source) use the same Exalate bridge to send data to DTP Jira (Remote Instance). The bridge should function as an open pipeline, simply transferring the data from IFS Jira to DTP Jira without enforcing project-specific routing or logic. The responsibility for interpreting the incoming data and determining the appropriate destination project or processing logic should reside entirely on the DTP Jira side (Remote).
Please let us know whether this can be achievable and any limitations are there.
Thanks,
Prasad Ramakrishnan
---
### Author:  [@Aida](https://community.exalate.com/u/Aida)
#### Post date: [September 24, 2026, 12:39pm UTC](https://community.exalate.com/t/many-to-one-ifs-to-dtp-jira-integration-using-a-common-exalate-connection/8396/2 "2026-09-24T12:39:27Z")
Yes, your many-to-one integration scenario is achievable with Exalate on Jira Data Center. You can set up a single Exalate connection that allows multiple source projects (IFS Jira) to sync issues to a single remote Jira instance (DTP Jira). The key is to use flexible sync rules, especially on the DTP Jira side, to handle incoming issues and route or process them as needed.
Here’s how you can approach this:
- On the IFS Jira (source), you can configure outgoing sync rules to send issues from multiple projects through the same connection.
- On the DTP Jira (remote), you can use incoming sync rules to interpret the data and decide how to process or route the issues. For example, you can use the source issue’s project key or other fields to determine the target project or apply specific logic.
- The connection itself does not enforce project-specific routing; all logic can be centralized on the DTP Jira side, as you described.
Limitations and considerations:
- You need to ensure that your sync rules on the DTP Jira side are robust enough to handle issues from multiple projects and route them correctly.
- Permissions and Exalate node configuration must allow for cross-project syncing.
- If you want to sync issues from all projects, make sure your Exalate triggers and rules are set up to include all relevant projects and issue types.
For more details on configuring sync rules and managing many-to-one scenarios, check out the documentation:
- [How to configure sync rules](https://docs.exalate.com/docs/configuring-sync-rules)
- [Managing multiple project integrations](https://docs.exalate.com/docs/setting-up-multiple-project-integrations)
This setup gives you the flexibility you need, with all routing and processing logic handled on the DTP Jira side.
---
### Author:  [@Jillani\_Fazal](https://community.exalate.com/u/Jillani_Fazal)
#### Post date: [September 25, 2026, 6:01am UTC](https://community.exalate.com/t/many-to-one-ifs-to-dtp-jira-integration-using-a-common-exalate-connection/8396/4 "2026-09-25T06:01:37Z")
Hi @pramak1X
Thank you for opening a post on our community portal.
Yes, this setup is absolutely possible with Exalate Classic. Here’s how it works and what to consider:
### How It Works
- **Outgoing sync rules** on each IFS Jira project can be kept simple—just send the issue data as-is.
- **Incoming sync rules** on DTP Jira can contain all the logic to:
- Route issues to the correct project.
- Apply any processing or transformation needed.
- Exalate’s Groovy-based scripting engine gives you full control over how incoming issues are handled, including project assignment, field mapping, and more.
A post was open in the past regarding the same scenario, please have a look: [How to sync Multiple JIRA project ( on Local Instance) to JIRA project in Remote Instance with Many to One mapping of Issues? - #2 by xl8bot](https://community.exalate.com/t/how-to-sync-multiple-jira-project-on-local-instance-to-jira-project-in-remote-instance-with-many-to-one-mapping-of-issues/4226/2)
I hope that you will find it useful and let me know if you have any follow up question.
BR,
Jillani