ServiceNow-Jira Bidirectional Sync
Budget: ₹1,500 – ₹12,500 INR
I need a solid, production-ready integration that keeps ServiceNow and Jira talking to each other in real time. The connection must work in both directions: when an incident, story, or task is opened or updated in ServiceNow it should appear or update in Jira, and the reverse must happen just as smoothly.
Scope of the sync
• Tickets / Issues
• Comments / Notes
• Status Updates
I already have admin-level access to both platforms and can provide API credentials, workflow diagrams, and a non-production sandbox for initial testing. You are free to leverage IntegrationHub, MID servers, REST APIs, webhooks, or an iPaaS tool—whichever meets enterprise security standards and proves easiest to maintain.
Acceptance criteria
1. Creating or updating a ticket in either system replicates the record, its current state, and its most recent comments in the other within 60 seconds.
2. Status changes remain aligned at all times, with no looping or duplicate updates.
3. Error logs are centralized and human-readable, with automated e-mail alerts on failure.
4. A concise hand-off document and 30-minute knowledge-transfer call wrap up the engagement.
If you have done a bidirectional ServiceNow–Jira sync before, especially using IntegrationHub spokes or custom REST scripts, I would love to see it in action.
Scope of the sync
• Tickets / Issues
• Comments / Notes
• Status Updates
I already have admin-level access to both platforms and can provide API credentials, workflow diagrams, and a non-production sandbox for initial testing. You are free to leverage IntegrationHub, MID servers, REST APIs, webhooks, or an iPaaS tool—whichever meets enterprise security standards and proves easiest to maintain.
Acceptance criteria
1. Creating or updating a ticket in either system replicates the record, its current state, and its most recent comments in the other within 60 seconds.
2. Status changes remain aligned at all times, with no looping or duplicate updates.
3. Error logs are centralized and human-readable, with automated e-mail alerts on failure.
4. A concise hand-off document and 30-minute knowledge-transfer call wrap up the engagement.
If you have done a bidirectional ServiceNow–Jira sync before, especially using IntegrationHub spokes or custom REST scripts, I would love to see it in action.