spacer Solutions Products Partners Support Company Download
MetiLinx
 
 
 
 
 

 

Integrating Custom and In-House Tools with Jira: What to Do When the Marketplace Has No App

Last updated: November 2026

The Atlassian Marketplace offers thousands of apps, but none of them can connect Jira to a tool that only your organization uses. When you need to integrate Jira Cloud or Jira Data Center with an internally built, legacy or niche system, there are four main options: Jira automation and webhooks, custom code on the Jira REST API, Atlassian Forge or Connect apps, and external integration platforms. This article compares them, explains the key design decisions, and shows how no-code platforms such as ZigiOps can connect Jira even to systems that have no API.

Jira is where software and IT teams plan and track their work. Because so much work starts elsewhere, in service desks, monitoring tools, CRMs and internal portals, Jira integrations are among the most requested in any organization. For popular tools, the Marketplace usually has an answer. For everything else, teams need to look further.

Typical examples include an internal deployment tracker that should create Jira issues for failed releases, a home-grown QA tool whose defects must reach development, a legacy customer support system whose escalations need engineering attention, or an industry-specific application whose configuration requests are handled by an internal development team.

Why custom tools are hard to connect to Jira

  • No ready-made app. Marketplace vendors build apps for widely used products, not for your internal systems.
  • Different data models. Jira issues have projects, issue types, workflows, custom fields and hierarchies that internal tools rarely mirror.
  • Interface limitations. Many internal tools have no API, or only expose a database, SOAP services or a client library.
  • Cloud and Data Center differences. Jira Cloud and Jira Data Center differ in APIs, authentication and app frameworks, which affects integration design.
  • Bi-directional needs. Users of the internal tool usually want to see Jira status and comments, not just send issues one way.

Option 1: Jira automation and webhooks

Jira's built-in automation can send web requests to external systems when issues change, and incoming webhooks can trigger rules when external systems call Jira. Jira also supports outgoing webhooks for issue events.

Good for: simple, event-driven flows when the internal tool has an HTTP endpoint, such as notifying the tool when an issue is resolved.

Limitations: automation rules are not designed for full bi-directional synchronization with field mapping, correlation and error handling. Execution limits apply on some plans, and complex logic becomes hard to manage across many rules. They also require the custom tool to have an HTTP interface.

Option 2: Custom code on the Jira REST API

Developers can write services or scripts that call the Jira REST API and the internal tool's interface, moving data between them.

Good for: teams with development capacity and unique requirements.

Limitations: custom code must handle authentication, pagination, rate limits, retries, field mapping, correlation and loop prevention. It must also be hosted, monitored and maintained through Jira and internal tool changes. Over time, these services often become undocumented and fragile.

Option 3: Forge or Connect apps

Atlassian Forge, and the older Connect framework, let developers build apps that run alongside Jira Cloud. An internal app can add UI elements, react to events and call external services.

Good for: organizations that want a Jira-native experience, such as a panel that shows data from an internal system inside the issue view.

Limitations: building and maintaining an app is a software project. Forge apps have runtime limits and need network access to reach internal systems, which can be challenging for on-premises tools. Data Center requires a different app model.

Option 4: External integration platforms

External integration platforms connect Jira with other systems through configurable templates, field mapping and synchronization rules, running outside Jira.

Good for: bi-directional sync, many integrations managed in one place, and teams without spare development capacity.

Limitations: the value depends on whether the platform can connect to your custom tool. Many platforms support only popular SaaS products or generic REST.

ZigiOps is one example of this option. It connects Jira Cloud and Jira Data Center with ITSM, DevOps, monitoring and CRM tools, and it can connect custom systems through an API, SOAP, a database or a library. That means even an internal tool without an API can be synchronized with Jira. New connectors are typically built in about three days and then configured without code.

Options for integrating custom tools with Jira
OptionBi-directional syncCustom tool needs an APIEffortMaintenance
Automation and webhooksLimitedYes, HTTP endpointLowGrows with number of rules
Custom codePossibleDepends on codeHighHigh
Forge or Connect appPossibleUsually yesHighMedium to high
External integration platformBuilt inNot necessarily, depending on platformLow to mediumLow to medium

Key design decisions

Project and issue type

Decide which Jira project and issue type should receive records from the custom tool. For example, defects from an internal QA tool become Bugs in the relevant product project, while requests from an internal portal become Tasks in a platform team's project. Routing can depend on fields such as product, component or team.

Field mapping

Map the custom tool's fields to Jira's system and custom fields. Pay attention to select lists, user fields, labels, components and versions, which require valid values in Jira.

Example mapping from an internal QA tool to a Jira bug
Internal QA tool fieldJira fieldNotes
Defect IDCustom field "External ID"Used for correlation
SummarySummaryDirect mapping
Steps and expected resultDescriptionCombined into one formatted description
ModuleComponentMapping table between module names and Jira components
SeverityPriorityCritical to Highest, Major to High, Minor to Medium
Build numberAffects versionCreated in Jira if missing, or mapped to nearest release
StatusStatus (via transitions)Status changes require valid workflow transitions

Workflow transitions

Jira changes status through workflow transitions, not by writing a status value directly. The integration must know which transition to use for each status change, and must handle transitions that require screens or mandatory fields.

Comments and attachments

Decide which comments flow in which direction, and whether internal comments should be excluded. Attachments may be important for defects and screenshots, but consider size limits and sensitive content.

Hierarchy

If the custom tool has parent-child relationships, decide how they map to Jira epics, parent issues and sub-tasks.

Correlation and loop prevention

Store the custom tool's ID in Jira and the Jira issue key in the custom tool where possible. In bi-directional sync, ensure that an update made by the integration does not trigger another update in the opposite direction.

Jira Cloud versus Jira Data Center considerations

  • Authentication. Jira Cloud uses API tokens or OAuth 2.0; Jira Data Center typically uses personal access tokens or basic authentication with a service account.
  • Network access. On-premises internal tools can usually reach Jira Data Center directly. For Jira Cloud, the integration layer must reach both the cloud and the internal network, which often means running it on-premises.
  • Rate limits. Jira Cloud applies rate limiting, so integrations must handle throttling.
  • Migration. Organizations moving from Data Center to Cloud should choose an integration approach that works with both, to avoid rebuilding integrations during migration.

ZigiOps can run on-premises or in the cloud, which helps when an internal tool sits behind a firewall and Jira runs in Atlassian's cloud.

Common scenarios

Internal QA tool to Jira

Defects logged in an in-house test management system create Jira bugs; developer comments and fix versions flow back to testers.

Legacy support system to Jira

Escalated customer issues in an older support platform create Jira issues for engineering, with status visible to support agents.

Deployment database to Jira

Failed deployments recorded in an internal release database create Jira issues assigned to the responsible team, linked to the release version.

Internal request portal to Jira

Requests for environment changes or access, submitted through a home-grown portal, become Jira tasks for platform teams, with resolution updates returned to the portal.

Security considerations

  • Use a dedicated Jira service account with project-level permissions limited to what the integration needs.
  • Use API tokens or OAuth with rotation; never use a personal account's credentials.
  • Give the integration least-privilege access to the internal tool, such as read-only database views for reads and staging tables for writes.
  • Keep sensitive data out of Jira if developers do not need it.
  • Check whether the integration layer stores issue content. ZigiOps does not store the data it transfers.

When to choose which option

A simple rule of thumb helps. If the custom tool has an HTTP endpoint and you only need to notify it of a few Jira events, automation rules are enough. If you need a Jira-native user interface showing internal data, consider a Forge app. If you have strong development capacity and a single, stable integration, custom code can work. If you need bi-directional sync, expect several custom tools to be connected over time, or the tool has no API, an external integration platform is usually the most sustainable choice, because it keeps all integrations in one place with consistent mapping, security and monitoring.

Measuring the impact

Before the integration goes live, capture a baseline so you can show its value. Useful measures include:

  • Time from a defect or request being logged in the custom tool to a Jira issue existing
  • Number of manual status requests between the custom tool's users and Jira teams
  • Number of duplicate or incomplete Jira issues created from the custom tool
  • Time spent per week copying information between the two systems
  • Time from a Jira fix to the custom tool's users being informed

These numbers usually improve quickly once records flow automatically, and they help justify integrating the next custom tool.

Implementation checklist

  1. Confirm which interface the custom tool offers: API, SOAP, database, library or files.
  2. Agree on target projects, issue types and routing rules.
  3. Build the field and status mapping tables with both teams.
  4. Define comment, attachment and hierarchy handling.
  5. Set up dedicated service accounts and permissions.
  6. Test with realistic data, including workflow transitions with required fields.
  7. Configure monitoring and alerts for failed synchronizations.
  8. Document the integration and assign an owner.

Frequently asked questions

How do I integrate Jira with a tool that has no Marketplace app?

Use Jira automation and webhooks for simple flows, custom code on the Jira REST API, a Forge or Connect app, or an external integration platform that supports your tool's interfaces.

Can Jira integrate with a system that has no API?

Not directly through Jira's own features, which rely on HTTP. An external integration platform that supports database, SOAP or library connectivity, such as ZigiOps, can bridge the gap.

Is Jira automation enough for bi-directional sync?

It can handle simple updates, but full bi-directional sync with mapping, correlation, comments, attachments and error handling is usually better handled by a dedicated integration platform.

Do integrations work the same for Jira Cloud and Jira Data Center?

The concepts are the same, but APIs, authentication, rate limits and app frameworks differ. Choose an approach that supports the edition you use now and the one you may migrate to.

How do I prevent duplicate Jira issues from an integration?

Store the external system's ID in a Jira field and check it before creating new issues. Integration platforms usually handle this correlation automatically.

Can comments be synchronized without exposing internal notes?

Yes. Most integration platforms let you filter comments by visibility, author or keyword, so only public comments are exchanged.

Can one integration connect several custom tools to Jira?

Yes. An integration platform can connect multiple custom tools to one or more Jira instances, each with its own mapping and routing rules, managed from a single place.

Key takeaways

  • The Marketplace covers popular tools, not custom or in-house systems.
  • Options include automation and webhooks, custom code, Forge or Connect apps and external integration platforms.
  • Design decisions about projects, mapping, transitions, comments, hierarchy and correlation determine success.
  • Jira Cloud and Data Center differ in authentication, network access and rate limits; plan for both if migration is likely.
  • ZigiOps connects Jira with custom tools, even those without an API, through no-code configuration and without storing transferred data.
Latest News

Bull and MetiLinx partner on infrastructure optimization and consolidation
(pdf)

MetiLinx & ParTec
announce strategic
alliance for
optimization of
cluster and grid
infrastructures
(pdf)

MetiLinx announces
ultimate suite of
database tools at
MySQL Users
Conference 2005
(pdf)

Legal Contact Us MetiLinx