Jira and ServiceNow record sync: a small pilot before rollout

Start with one table and an agreed purpose

The published Keelcroft app connects one Jira Cloud project to one supported ServiceNow table, such as incidents, problems, changes or supported task records. Choose the minimum fields each receiving team needs, the direction for each field and who will own failures.

Review the people who can read each destination. A sync is not a replacement for ServiceNow ACLs, Jira issue security or your organisation's data-sharing approval. Ask your ServiceNow administrator about API permission and applicable licensing.

Prepare a safe test

Use a non-production ServiceNow instance or an approved disposable test record, plus a nonsensitive Jira issue. Enter the dedicated instance credentials directly in the app. Do not use customer incidents as test fixtures or put a password in a support ticket.

The publisher has not independently completed a live ServiceNow instance round trip. The app's automated tests and Marketplace availability are not proof of your instance's ACLs, Business Rules or data policies. Validate those during evaluation.

Configure the connection and states

1. Save the permitted instance host and selected table in the Jira project's app settings.
2. Store credentials and run the setup check. Review the disposable-record result and cleanup instruction; a failed delete requires explicit cleanup.
3. Choose field directions and the actual state display labels used by your ServiceNow instance, not a guessed universal list.
4. Review which Jira transition corresponds to which ServiceNow state with the service owner. Done, Resolved and Closed can mean different things.
5. Enable sync and link one existing Jira issue to one ServiceNow record number.

Test the process, not just the connection

Edit the title of the test Jira issue and independently read the ServiceNow record. Repeat in reverse, then test permitted state transitions. A resolved record may require close code or close notes under your instance's policy; an API connection check alone cannot prove a transition will succeed.

Inspect reconciliation for agreement, conflicts or failures. Record the test result and approximate time before expanding the rollout. If an update fails, share the step and a redacted error. Do not send incident text, internal notes or credentials.

Avoid promises outside the shipped release

This checklist covers the existing public record-field sync, not the later attachment, resolution-rule or expanded recovery candidate. Do not promise file copying, equivalent internal-note visibility, an enterprise compliance certification or a five-minute delivery SLA from a development screenshot.

Polling and optional configured push have different operational implications. Missing or deleted records do not cause the ordinary sync to delete the surviving issue. Confirm your instance behaviour and the current public documentation before committing to a production workflow.

Decide using your own test result

Proceed only if the app covers your required scope and your first real test works. Check the Marketplace calculator for the licensed Jira site size; the number of people in the connected project is not necessarily the billing tier. A standard evaluation is not a paid subscription or a completed rollout.

Reference: Public ServiceNow app documentation and current boundaries. This guide describes Keelcroft's public foundational workflow and states candidate/live-testing boundaries separately; it is not a competitor benchmark or certification.