What we do
Tools
Industries
Department
How we workLet's talk →
Home/Jira/Jira Integrations
Jira

Jira integrations: what already exists, and what has to be built

Somebody asked whether Jira can talk to another system, and you're the one who has to find out. For Slack, Teams and GitHub the answer's an app Atlassian already makes. For a CRM, a help desk or an ERP it's a Marketplace app, an Automation rule, or code on the REST API. Here's how to tell which one you're looking at.

The pairings Jira already covers

If your request is one of these, install the official app before anyone writes a line of code.

01

Slack

The Jira Cloud app for Slack posts issue updates into a channel, and people can create an issue or move one to its next status from a message.

02

Microsoft Teams

Atlassian's Jira Cloud app for Teams does the same job inside Teams: notifications in a channel, and issues created or updated from the chat.

03

GitHub and Bitbucket

Bitbucket is built in, and the GitHub for Jira app connects GitHub. Put the issue key in a branch name, commit message or pull request title, and it shows up in the issue's development panel.

04

Confluence

Same company, same login. Pages and issues link to each other, and you can embed issue lists in a page.

05

Smartsheet

For teams that plan in sheets and build in Jira, there's a connector, and it's worth knowing which fields it can and can't sync.

06

Jira Service Management

Support requests and engineering work in the same Atlassian site, linked from request to bug.

Install a Marketplace app, or write an Automation rule?

Both avoid custom code, but each one fits a different job.

Atlassian Marketplace

An app someone else maintains

  • Thousands of third-party apps, built by Atlassian partners, covering CRMs, time tracking, test management and more.
  • Good when the app's model of the other system matches yours, field for field.
  • Many are billed per user on top of your Jira subscription, so price it at your full headcount.
  • Check who publishes it and how recently it was updated before your process depends on it.
Automation for Jira

A rule that calls out, or listens

  • The Send web request action posts issue data to any URL when the rule fires: an issue is created, a status changes, a field is set.
  • The Incoming webhook trigger lets another system start a rule in Jira by calling its URL.
  • Good for one event, one destination, and a payload you can build from smart values.
  • Rule runs count against your plan's monthly automation allowance. The Jira Automation page has the limits.

If an app covers your system and your fields, install it. If you only need Jira to announce one event to a URL, a rule is quicker. When the data has to go both ways, match records, or survive the other system being down, it's code.

Systems with no app worth installing

Marketplace coverage is deep for popular SaaS tools and thin for the rest: an internal line-of-business system, an enterprise platform like NetSuite, Workfront or Intercom where the available app doesn't match how you use it, or an older tool like TFS, or ticket references buried in SVN history.

Here an integration means someone builds it. Usually that's a small service on the Jira REST API that creates and updates issues, plus a receiver for Jira webhooks so changes in Jira flow back out. When people want to see the other system's data inside the issue itself, it can be a Forge app, Atlassian's platform for Jira Cloud apps, installed on your own site without a Marketplace listing.

n-frames builds these links for teams whose Jira has to agree with a system nobody sells an app for. A NetSuite project status written onto the epic, an Intercom conversation turned into a bug with the customer attached, or a support escalation that closes itself when the fix ships.

Leaving SVN, TFS or another tracker for Jira

A move like this is a one-time job, and it goes better as a script than as weeks of re-entry.

  • Which history actually needs to come across?

    Open work almost always does. Ten years of closed tickets may only need to be searchable, which can mean an archive rather than a full import.

  • How do old statuses map to your Jira workflow?

    Every old status needs a home in the new workflow before import, or issues land in the wrong column and nobody trusts the board.

  • Do the people match?

    Assignees and reporters have to map to Jira accounts. Someone who left five years ago needs a placeholder, not a failed row.

  • What happens to attachments and comments?

    Jira's CSV import covers fields and even comments. Full change history, and files in bulk, usually need a script on the API.

  • Where do links to old ticket numbers go?

    Commit messages, wiki pages and emails still say TFS-4412. Keeping the old ID in a field makes them findable.

Questions people ask

Does Jira integrate with Slack?

Yes. The official Jira Cloud app for Slack sends issue updates to a channel, and lets people create an issue or change its status from a Slack message.

Can Jira connect to GitHub?

Yes. Install the GitHub for Jira app, then include the issue key in branch names, commit messages or pull request titles. Commits, branches and pull requests then appear in the issue's development panel. Bitbucket works the same way without a separate app.

Is there a Jira integration for NetSuite?

Some Marketplace and third-party connectors pair the two, but they're built for a general case, and coverage of NetSuite's records and your custom fields varies a lot. When none fits, the link is built on both APIs: project or order status from NetSuite onto the Jira epic, and delivery dates back the other way.

Can I migrate from SVN or TFS into Jira?

Yes, but there's no single one-click path from every old tracker. Fields come across through Jira's CSV import. Comments, attachments and history usually need a scripted, one-time migration on the API, run once on a test site and then for real.

Can Jira call another system on its own when an issue changes?

Yes, two ways. An Automation rule with the Send web request action posts to a URL when the rule fires. A system webhook, registered by an admin, sends every matching event. Either way, something on the other end has to receive it, check it and act.

Who builds a Jira integration when the Marketplace has nothing?

That's a job n-frames takes on: the REST API service or Forge app, the webhook receiver, and the monitoring that spots a failed sync before your team does. We keep it running when Atlassian changes an endpoint.

Let's talk

Tell us the one thing your team does manually that eats up time. We read every message and reply within a day.