What we do
Tools
Industries
Department
How we workLet's talk →
Home/Jira Smartsheet Connector
Jira + Smartsheet

The Jira Smartsheet Connector: Set It Up Right the First Time, and Know What It Leaves Out

Smartsheet sells its own Jira Connector. It syncs Jira issues into a sheet, and sheet rows back into Jira, so a PMO can track engineering work without anyone exporting a CSV. It's a paid add-on, a few of its settings can't be changed after you save, and it doesn't carry everything leadership asks for. Here's the setup, then the edges.

The connector in four lines

What it is: Smartsheet's premium Jira Connector, priced through Smartsheet Sales on top of your plan.

Who can get it: Business, Enterprise and Advanced Work Management customers. It isn't offered in Smartsheet Gov.

Who sets it up: the connection needs a Jira Admin. Building workflows needs Editor access to the sheet, a Jira account on those projects and the Connector User role.

Where: the connector site, or from a sheet.

Data Integrations Manage Connectors Jira

Build a Jira workflow in Smartsheet

A workflow is one sync between a set of Jira projects and one sheet. Read step 1 twice: three of its choices are permanent.

  1. 1

    Start a workflow

    connectors.smartsheet.com/c/jira Add Workflow

    Sign in with your Smartsheet account. If the Jira connection doesn't exist yet, your Jira Admin creates it first.

  2. 2

    Choose direction, sheet and projects

    Pick one-way (Jira to Smartsheet or the reverse) or two-way, the target sheet (or Create a new sheet), and the Jira projects: up to 25 picked by name, or all of them.

    Watch for: direction, sheet and projects lock once you save. Getting one wrong means building a new workflow. A sheet can only hold one workflow, so plan which sheet is the portfolio sheet before you start.

  3. 3

    Map fields to columns

    Pair each Jira field with a column, or click New column to create one of the matching type. Issue Key and Error Column are required, and both only flow from Jira into the sheet.

    Watch for: custom fields added by Jira apps or plugins have limited support. Test the ones your teams rely on, like story points, before promising them in a report.

  4. 4

    Filter what syncs

    For one project, Add filter combines conditions with AND. For several projects, write a JQL query, which allows AND and OR. Sheet filters can limit which rows go to Jira, for example rows with a checkbox ticked.

    Watch for: an invalid JQL query turns the workflow off. Test it in Jira's issue search first. Our JQL guide covers the syntax.

  5. 5

    Keep the hierarchy and save

    Leave Maintain Jira hierarchy grouping ticked so stories, tasks and subtasks nest as they do in Jira. Check the Update Summary count, name the workflow, and tick Sync new rows created in Smartsheet to Jira if a new row should raise an issue. Then Save Workflow.

What the Jira Connector won’t do

These are by design, and they're the usual reason a portfolio sheet still gets edited by hand after the connector goes in.

No comments or attachments

How you'll know: Leadership asks why a task is late and the answer is in a Jira comment the sheet never shows.

Fix: Pull the latest comment or a blocker field through the Jira API into its own column, or keep the reason in a Jira field the connector can map.

One workflow per sheet

How you'll know: You want one sheet per program plus a combined portfolio sheet, all fed from Jira.

Fix: Use one multi-project workflow with JQL per sheet, then roll the sheets up with a Smartsheet report. If the rollup needs logic a report can't do, that's a sync to build outside the connector.

The workflow quietly stops

How you'll know: Rows stop changing. The workflow owner was moved to Contributor, or Jira's webhooks can't reach the connector.

Fix: Give ownership to a service account that won't change role, and check the run history (Sync to Smartsheet and Sync to Jira entries) after any Jira admin change.

Stopping a sync takes a moment

How you'll know: You deactivate a workflow mid-run and changes still arrive.

Fix: That's expected. The run in progress finishes, then the workflow stops.

The connector, or a pipeline from the Jira API

Most teams start with the connector. The question is whether leadership reads Smartsheet alone.

Smartsheet Jira Connector

Jira and one sheet, kept in step

  • Issues sync into a sheet and rows can raise issues, one way or both.
  • Set up through screens by a Smartsheet admin, with a Jira Admin for the connection.
  • Fields only: no comments, no attachments.
  • Lives entirely inside Smartsheet.
Custom pipeline

Jira status wherever leadership looks

  • The same Jira data feeds Smartsheet rollups, Power BI dashboards, SharePoint status docs and Tableau.
  • Can carry the latest comment, blocker reasons or cycle times worked out from issue history.
  • Runs live for an active dashboard or on a schedule for a weekly rollup.
  • Someone has to build, monitor and maintain it.

If the audience is a PMO working in Smartsheet, buy the connector. If the board deck pulls from Power BI and the status page lives in SharePoint, one pipeline from Jira is less work than three exports.

Why this keeps coming up

Engineering's own Jira reports are fine for the people running the sprint. The people funding the work look somewhere else: a Smartsheet portfolio, a Power BI page, a SharePoint document. Without a connection, someone exports from Jira every Friday and the numbers are stale by Monday.

n-frames builds the pipeline that keeps those views current straight from Jira's API, so an engineer isn't losing an afternoon each week to it. The same pattern works when the planning side is in Notion instead of Smartsheet.

Questions people ask

Doesn't Jira have its own reporting?

Yes, and it's good for engineering teams tracking their own sprints. The gap is getting that data into the Smartsheet, BI or document tool that leadership outside engineering actually checks.

How current does the data stay?

With the Smartsheet Jira Connector, you choose a manual or automatic sync, and Jira changes reach the sheet through Jira's webhooks. With a custom pipeline, it depends on use: near real time for an active dashboard, or a scheduled run for a daily or weekly rollup.

Can this work in both directions?

Yes. The connector can sync two ways, so a status change in Smartsheet can update the Jira issue and a new row can create one. Decide the direction carefully, because it can't be changed after you save the workflow.

Is the Smartsheet Jira Connector free?

No. It's a premium offering with its own cost, quoted by Smartsheet Sales, and it's available on Business, Enterprise and Advanced Work Management plans.

Is the quote for a Jira and Smartsheet sync really free, with no obligation?

Yes. n-frames maps where leadership reads project status, then writes up the Jira and Smartsheet sync it needs and its price. Whether it goes ahead is your call.

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.