How to Integrate Jira with Front

What the Front–Jira integration actually does

Front ships two related but distinct Jira surfaces, and knowing which is which saves a lot of confusion. Per Front's Jira integration guide, the plugin is the sidebar panel inside a conversation: it lets any teammate manually create a new issue, link an existing one, and view issue details inline without leaving Front. The connectors, described in Front's Jira Connectors documentation, are the automation layer — they tap "every action available in the Jira API" so you can create issues and sync comments from rules, macros, and chatbots.

The practical split, per Front's marketing Jira integration page: the plugin is available on every plan and covers manual, human-in-the-loop work; the connectors require the Professional plan or above and cover automation and richer two-way comment sync. Most teams start with the plugin and graduate to connectors once the manual handoff proves its worth.

Step 1 — Enable the Jira app (admin, once)

Enabling is a company-admin action and only has to happen once. Per Front's Jira integration guide:

1. Click the gear icon to open settings, then go to Company settings → App store.
2. Find and select Jira, then click See details.
3. Click Enable app.
4. Open the Authentication tab and click Sign in.
5. Authenticate with your Jira credentials in the pop-up window.
6. Click Save to finish enabling the app.

That connect/overview page is where the relationship starts — it authorises Front to talk to your Jira instance, but it does not yet map any fields or link any issues. The real per-project configuration happens next, at the individual level.

Step 2 — Configure your default project and fields (each teammate)

After the app is enabled company-wide, each teammate who wants to file issues sets themselves up once. Per Front's documentation:

1. In Front, pin the Jira icon in the sidebar app switcher so it's always to hand.
2. On first use, sign in with your own Jira credentials — the integration acts as you in Jira, so issues are created under your account.
3. Click the gear icon in the Jira panel to configure your default project, default issue type, and the fields you want the create form to show.
4. Click Save.

Front includes default fields — Project, Issue type, Summary, Description — and surfaces any custom fields associated with the project and issue type you chose. This is the closest thing to field mapping the native integration offers: you decide which Jira fields appear on the create form, so the person filing the issue captures the right data (severity, component, customer tier) at handoff time rather than in a follow-up.

Step 3 — Create or link an issue from a conversation

This is the payoff. Open any conversation that needs to reach engineering or ops, and use the Jira panel:

1. To create a new issue: click Add issue in the This conversation tab, select the Project, choose New issue, fill in the configured fields (summary, description, and any custom fields), and click Create.
2. To link an existing issue: use the Search tab, select the project, type the issue name or key, press Enter, click the matching result, and use the three-dot menu to attach it.

Either way, Front links the issue to the conversation and records the action in the conversation's activity history, so anyone in the shared inbox can see it was escalated. Crucially — and this is the detail that makes the handoff two-directional — Front notes that when a Jira issue is attached to a conversation, "a link back to all related conversations in Front will be added to the description of the Jira issue." An engineer opening that Jira ticket can click straight back to the customer thread that raised it.

Step 4 — Sync status back to the conversation

The reason to link at all is so the loop closes. The most common sync teams rely on is status flowing from Jira back into Front: when the linked Jira issue is resolved or closed, Front can reopen the conversation so the agent knows it's time to reply to the customer. Per Front's Jira Connectors documentation, the connectors can "sync Jira status changes to Front conversations" and support custom status reopening rules.

There's a prerequisite worth flagging up front: status sync relies on Jira webhooks, and enabling those may require your Jira admin's help. If the reopen-on-close behaviour ever stops working, Front's guidance is to check the webhook and, if needed, re-authenticate the integration.

For teams on Professional or above, the connectors go further — they can send and receive comments between a Jira issue and its Front conversation, so a developer's note on the ticket lands in the conversation's comments and vice versa. That's the true two-way sync; the plugin alone is closer to create-and-link plus one-way status.

Plugin vs. connectors: which to use

Because the two surfaces overlap, here's the decision at a glance, drawn from Front's Jira Connectors documentation:

The short version: plugin for humans, connectors for automation. A support team that escalates a handful of bugs a week is perfectly served by the plugin. A high-volume ops team that wants every conversation tagged bug to auto-file a Jira issue — and every Jira comment to appear in Front — needs the connectors, and therefore Professional or above.

The honest limits — and where an AI layer picks up

The native Front–Jira integration is genuinely good at what it's built for: giving a human a fast, in-context way to escalate a conversation into Jira and keep the two linked. Credit where it's due — the create form, the back-link in the Jira description, and the reopen-on-close status sync solve the real handoff problem cleanly.

But it's worth being clear about the edges. Status sync is effectively one-way for the plugin (Jira → Front reopening), and the fuller two-way comment sync is gated behind Professional-plus connectors, per Front's documentation. Deep configuration — webhooks, custom reopening rules, field-level behaviour — often needs a Jira admin and lives in your Jira instance, not fully inside Front. Front's cloud connectors also don't cover on-premise Jira Server the way they do Jira Cloud, so self-hosted setups hit a wall. And most importantly, the integration is mechanical, not judgmental: it will happily create a duplicate Jira issue for the tenth report of the same bug, because it has no idea the other nine exist.

That last gap is where an AI agent layer fits — not to replace the integration, but to add the reasoning a create-form can't. The broader category of AI agents for customer service exists for exactly this kind of judgment work. Macha is one such layer: it runs on top of the Front you already use through the live Macha–Front connector — it doesn't replace Front, your shared inboxes, or your Jira link. Macha's agent reads the incoming conversation, decides whether it's a genuine new bug or a known one, checks for an existing linked issue before filing a duplicate, and creates or links the Jira issue through a custom tool that turns the Jira API into something the agent can call — capturing the right fields automatically. The native plugin puts a create button in the sidebar; the agent decides when to press it and what to write. If you want the mechanics of wiring Front to an AI layer, connecting Front to Macha to route conversations to AI walks through it, and Macha's credits are consumed per AI action, never per resolution. For the wider picture of what plugs into Front, see the best Front integrations and how the shared inbox fits together.

FAQ

How do I enable the Jira integration in Front? A company admin goes to the gear icon → Company settings → App store → Jira → See details → Enable app, then signs in with Jira credentials on the Authentication tab and clicks Save. After that, each teammate pins the Jira icon and signs in with their own Jira account to set a default project, issue type, and fields.

How do I create a Jira issue from a Front conversation? Open the conversation, click Add issue in the Jira panel's This conversation tab, select a Project, choose New issue, fill in the fields, and click Create. Front links the issue to the conversation and adds a link back to the conversation in the Jira issue's description.

Does the Front–Jira integration sync two ways? Partly. Status can sync from Jira back to Front — closing a linked Jira issue can reopen the Front conversation — and this relies on Jira webhooks that a Jira admin may need to enable. Full two-way comment sync (comments flowing both directions) requires Front's Jira connectors, which are on the Professional plan or above.

What's the difference between the Jira plugin and the connectors? The plugin is a sidebar panel for manually creating, linking, and viewing issues, and it's available on all plans. The connectors expose the full Jira API to automate issue creation and comment/status sync through rules and macros, and they require Professional or above.

Can I add AI to the Front–Jira handoff without replacing Front? Yes. An AI layer like Macha connects to Front as a live connector on top of your existing inboxes and Jira link. The agent reads the conversation, checks for existing linked issues to avoid duplicates, and creates or links the Jira issue with the right fields — while your team's inboxes, rules, and Jira setup stay exactly where they are.

Ready to turn a manual "file a Jira ticket" step into something an agent handles in context? Start a free trial of Macha and connect it to your Front in minutes.