Does the Jira dev ops integration pull all the records locally or use an API to pull them in dynamic

[billgoodall]

Hello! we are looking at activating the Jira integration for DPR.

1. Does this integration pull all the issues locally?
   1. Like millions of records to store in SN data tables
2. Or does it use live API calls to query up the Jira issuses dynamically
   1. by issue key
   2. or by FixVersion (pulling in the related issue keys.

[Vishal36]

Hi @billgoodall, 

• Before you activate any Jira–ServiceNow integration (for DPR or otherwise), here are a few things to consider:
• What kind of sync model do you actually need?
• If you're only referencing issue metadata (like summaries or IDs), live API calls might be sufficient.
• But if you need full traceability, history, or audit logs—local storage or caching is often required.
• Are you integrating for reporting, automation, or traceability?
  • For deep reporting (like trends, velocity, risk), you may need to replicate data locally.
  • For real-time automation, a dynamic lookup may work—but performance could be an issue at scale.
• Do you need full issue sets or just selective data?
  • Pulling everything (millions of issues) into ServiceNow can bloat your tables.
  • Instead, define filtered sync rules based on FixVersion, project, issue type, etc.

You may want to consider a ServiceNow Partner’s enterprise – grade integration tool, OpsHub Integration Manager that can help you with:

• Bidirectional sync without a line of code
• Context – rich data sync in real-time (with comments, attachments, traceability).
• Keeping ServiceNow lightweight, avoiding overloading your instance with unnecessary records.

There is a free Community edition of OpsHub Integration Manager (OIM) that supports your use case. You can immediately start syncing without requiring a license.

Hope it helps!