If you use Jira to track feature development, you’ll find it handy to integrate your Jira instance with productboard. Your engineering team can continue managing their development pipeline in Jira while product managers enjoy the flexibility of productboard for understanding user needs, prioritizing what to build next, and rallying everyone around the roadmap.

Article contents

  • Summary of benefits
  • Set up your Jira integration
  • Configuration
  • Map custom fields
  • Add links from Jira back to productboard
  • Pushing features into Jira
  • Pushing components into Jira
  • Pushing releases into Jira
  • Current limitations
  • Deactivating the Jira integration
  • Jira on demand vs. Jira self-hosted
  • Troubleshooting

Summary of benefits

  • One-time import from Jira: If you’re just getting started with productboard, you may wish to add some Jira issues as new productboard features. You can import all of your Jira issues, use JQL to specify criteria for which issues to load, or select individual features to load.
  • Flexible mapping: Depending on your team’s conventions, map productboard features to Jira issues and productboard components to Jira epics. Otherwise, if your productboard features are defined in broad terms, you can forget the components and map these features directly to Jira epics.
  • Pushing features made simple: The control is in your hands to push features into Jira when, and only when, you’re ready to share them with engineering. Push individual features, a component and all of its underlying features, or a release and all of its underlying features. (productboard releases map to Jira fix versions).
  • Support for multiple Jira projects: You can now opt to select a Jira destination project each time you push a feature. Or, select a default Jira project to which all newly pushed features will be sent.
  • Two-way sync: Opt to automatically sync changes in status, name, description, release/fix version, effort/story points, and custom fields between productboard and Jira. Any change you make in Jira will be reflected in productboard in real-time.
  • Auto import: When you or your engineering team create new issues in Jira, you can have productboard automatically import them in. One less thing to worry about!

Set up your Jira integration

Before you begin authorizing the integration, make sure you have Jira Administrator Global Permissions.

  1. In productboard, use the bottom left menu to select Integrations.
  2. Click Add new Jira integration.
  3. Enter the URL of your Jira instance.
  4. Click Set up integration.
  5. When the Jira window opens, log in and follow setup instructions as outlined in the productboard window.
  6. Click Authorize in productboard after you create the link in Jira.
  7. Click Allow in the Welcome to Jira dialog.
  8. Choose a target Jira project where you'll be pushing features from productboard.
  9. Select the Jira issue type to which productboard features will be mapped. (Recommended for Jira agile: "story").
  10. Click Enable.

Configuring your Jira integration

From productboard's Jira integration page, you can configure the following:

  • Server URL – Indicate your Jira server URL.
  • Project – Determine whether to push all features to the same default Jira project, or whether users should specify the relevant Jira project each time they push features.
  • Issues mapping – Determine whether productboard features should become epics (recommended) or stories when pushed to Jira (more info below).
  • 2-way-sync – Opt to automatically sync changes in name, description, release/fix version, effort/story points, and custom fields between productboard and Jira. Changes made in Jira are reflected in productboard in real-time. Changes made in productboard will be visible in Jira after refreshing your browser.
  • Auto import Opt to automatically import issues created in Jira into productboard or a subset of Jira issues, as specified by JQL. (Note: Only new issues created after auto import is enabled will be imported to productboard.) You can chose the location where newly imported issues should live, but we're also automatically tag all auto imported features in productboard with a tag "Jira-auto-import" so that you can find them easily.
  • Status – Customize the color of each Jira status value, as it will appear in the special Jira task column.
  • Custom fields – Choose custom fields in Jira to sync with custom columns in productboard (more info below).
  • One-time import – Manually import batches of existing Jira issues into productboard, either by selecting importing all issues, importing a subset of issues as specified by JQL, or importing specific issues of your choice.

Map entities between productboard and Jira

Depending on your team's conventions, you can map productboard features to Jira epics (recommended), or to Jira stories.

Map feature to Jira epics (recommended)

We recommend mapping productboard features to Jira epics because productboard is best used for high-level prioritization: which user needs you'll solve, and which features you'll build. Once you've pushed features into Jira as epics, you can break them down into stories representing more granular user scenarios devs will accommodate with the features they build.

With this configuration, productboard components are not pushed to Jira. They serve only to keep features organized in productboard.

Field equivalencies:

Reporter is only mapped if a user with a matching email address exists in Jira. Assignee is left blank so it can be filled out in Jira.

Map features to Jira stories

When productboard features are mapped to Jira stories, the lowest tier of productboard components are mapped to Jira epics.

Field equivalencies:

Reporter is only mapped if a user with a matching email address exists in Jira. Assignee is left blank so it can be filled out in Jira.

Map custom fields

If your team relies on custom Jira fields to plan and deliver features, you'll appreciate being able to access and update this data right from within productboard. Any updates are mirrored across both systems, so you need only make changes once.

Set up custom field mapping before importing issues from Jira. Otherwise custom field values won't be synced until a change has manually been made.

Jira custom fields can only be mapped to productboard custom columns with the same value type. For example, a checkbox field in Jira cannot be mapped to a dropdown field in productboard.

Story points can be mapped to productboard's default Effort column.

Add links from Jira back to productboard

In just a few minutes, you can save users hours of time by offering direct links from Jira issues to their associated productboard features.

Upon setting up your Jira integration, productboard automatically creates a new productboard URL field in Jira. This field will be visible on all issues pushed from productboard into Jira, as well as issued imported from Jira into productboard.

To make the new field visible for your users, update Jira settings:

  1. In Jira, log in as the same user you used to configure the Jira integration. Go to Settings (gear icon) > Issues.
  2. Under Fields, select Custom fields.
  3. Locate the productboard URL field and use its gear dropdown to select Screens.
  4. On the screens page, use the checkboxes to associate the productboard URL field to the screens used for your Edit Issue and Create Issue Jira operations. (In many cases, this will include the Default screen, but may also include others: see note below.)
  5. Click Update.

If you are unsure of which screens are used for the Edit Issue and Create Issue operations, in a new tab: select the Jira settings menu (gear icon) > Projects > [your_project_title] > Screens. Uncollapse the screen schemes and see which screens are associated with the Edit Issue and Create Issue operations. Then return to your original tab and ensure the productboard URL field is associated with this/these screen(s).

*Note:  We don’t fill in the custom field for these URL's retrospectively for already pushed features.

Pushing features from productboard into Jira

In productboard, features can be pushed into Jira one at a time using the special Jira task column that may be added to your Features board.

  1. On the Features board, check to make sure the Task column group is toggled on (see graphic below).
  2. Find the feature you'd like to push to Jira and click Push in its Jira column.

You can also push a feature using controls available in a feature's details pane:

When a feature is pushed into Jira, productboard creates a new epic/story in Jira in the project you've specified. And since the integration is two-way, you can also track a feature's Jira status right from your Features board:

Pushing components from productboard into Jira

If productboard features are configured to map to Jira stories, you can push the lowest level of components into Jira as epics. Doing so pushes all underlying features into Jira as stories.

Once you push a productboard component into Jira, you will only be able to change the productboard type of the component (i.e. to a feature) if the component has no underlying features in productboard.

Pushing releases from productboard into Jira

You can push releases and all underlying features into Jira using the Jira push option on a release's details pane. productboard releases map to Jira fixVersion.

Current Limitations

  • It's not currently possible to link existing Jira stories or epics to existing productboard features. Links between features and stories/epics can only be made by importing stories/epics into productboard as new features, or pushing features into Jira as new stories/epics.
  • Jira's latest project type (next-gen) is not yet fully supported. See below.

Deactivating the Jira integration

You can deactivate the Jira integration at any time by selecting Remove on the Integrations page.

Note: Should the Owner of your Integrations change, contact us to reset your integration permissions.

A note on Jira next-gen projects

Looking to integrate with a Jira next-gen project? We don't yet support Jira's newest project type, but will be working on some enhancements there soon.

Jira on demand (cloud) vs. self-hosted (on-premise)

What's the difference between Jira on-demand and Jira on-premise? Learn more about productboard plans and Atlassian's cloud and self-hosted offerings.

Troubleshooting ⚠️

Troubleshooting the Jira integration

Did this answer your question?