# Many-to-One IFS to DTP Jira Integration Using a Common Exalate Connection **URL:** \ **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:** 1\ **Showing post:** 4
**Author:** ![Jillani\_Fazal](https://dub1.discourse-cdn.com/flex018/user_avatar/community.exalate.com/jillani_fazal/32/355_2.png) [@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 --- _[View the full topic](https://community.exalate.com/t/many-to-one-ifs-to-dtp-jira-integration-using-a-common-exalate-connection/8396)._