Align your product strategy with execution with Productboard's Jira integration.
Productboard serves as your single source of truth - capture and prioritize your feature ideas, push features to delivery, and monitor progress all from within a single dashboard.
In this article, you'll learn how to use our Jira integration to unify your product and engineering workflows.
To learn more about how to set up your Jira integration, see our article Getting started with Jira.
If you're trying to solve a problem, see our article Troubleshooting Jira.
In this article:
- Push features from Productboard into Jira
- Push subfeatures from Productboard into Jira
- Mapping fields between Jira and Productboard
- Automate propagation of Jira Development Status to a Productboard Feature Status
- Unlink a feature or a subfeature from a Jira issue
- Push a release into Jira
Import Jira issues into Productboard
- Frequently asked questions
Push features from Productboard into Jira
Once the Jira integration is enabled, maker+admins can push a feature into Jira in its details side pane:
Maker+admins can also display a special Jira task column on your boards:
The Jira task column allows you to easily push many features into Jira:
At the moment you push a feature into Jira, you can decide its issue type. This can always be updated later in Jira. You can also choose to link a Productboard feature to an existing issue in Jira.
Features in Productboard are typically pushed to Jira as epics.
- In some cases you may have small, yet important, ideas represented as features in Productboard. These can be pushed to Jira as stories, bugs, tasks, or other custom issue types.
- Even after pushing a feature to Jira, you can always update its issue type in Jira.
Once features are pushed, whether from the details pane or task column, you'll see the issue's status displayed (and issue ID on hover). Select this to navigate to the issue in Jira. (You can use the Productboard URL field on issues to navigate back to features in Productboard.)
Push subfeatures from Productboard into Jira
Subfeatures can be pushed to Jira in the same way as features.
- Subfeatures are typically pushed to Jira as Stories, but they can also be pushed as Bugs, Tasks, Sub-tasks, or other custom issue types.
- Maker+admins need to push subfeatures individually. For example, if you push a feature, the subfeatures won't be pushed automatically.
If a maker+admin pushes the feature as an Epic, the connected subfeatures you push will automatically be linked to the Epic in JIRA.
Note: If you push a subfeature as an Epic, it won't be linked to the parent feature that's also an Epic.
- Even after pushing a subfeature to Jira, maker+admins can change it to a feature at any stage. You can also update its issue type in Jira.
- When pushing subfeatures as Sub-tasks, their parent features will be pushed into Jira as well. (In Jira, Sub-tasks must have a parent).
Mapping fields between Jira and Productboard
When features/subfeatures are pushed into Jira, their fields are mapped to Jira issue fields in the following way:
Productboard | Jira
- Feature name | Issue name
- Feature name | Issue summary
- Feature description | Issue description
- Jira "Task" status | Issue status
- Release | Fix version
- Feature owner | Reporter
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.
Below, you can find how JIRA custom fields map to fields in Productboard:
Using Markdown in a feature description
If your Productboard feature description contains the following Markdown elements, those elements will be represented in your Jira issue description:
- Jira color tag
Automate propagation of Jira Development Status to a Productboard Feature Status
A Maker+admin of your Productboard workspace can set this up by following the steps below:
- Click your Avatar in the bottom left of your account and then click Integrations ().
- Scroll down to your Jira Integration and select the Jira Integration you want to set up the Status Sync for.
Scroll down to the section Sync Status Updates. and click on the + Add status rule button.
- On the left dropdown, select all the Jira statuses that if changed in Jira will trigger a change of status in Productboard. Only the statuses in the selected project will be shown. If you select "Let me pick with every project" all statuses from the whole Jira Workspace will be shown.
- On the right dropdown, select the Productboard status that will change in Productboard if the associated Jira issue is changed to any of the selected statuses on the left side. If you have not set up your Productboard statuses yet, see our article Customize status values for features.
Repeat the previous steps as many times as you need to automate the status sync.
Note: You don't have to do this for all the statuses, only the ones you care about.
- Click Save status rules. From now on, if anybody changes a connected Jira issue status to the one you predefined, the status of the connected Productboard feature will be changed based on the rules you’ve set.
When automating propagation of a Jira Development status to a Productboard feature status, from time to time you might receive some errors. The steps below describe how to resolve these errors.
Status no longer exists in Jira or is not available for the selected project only
If the status is deleted on the Jira side but is mapped for this integration on Productboard, and/or the status is not available for the selected project, it’s going to be highlighted and won’t be updated on the Features Board.
To resolve the error:
- Remove the highlighted status from the rule via clicking the X button in the status box.
- Remap the status that corresponds to your current flow.
- Save status rules.
Status no longer exists in Productboard
If the Productboard status is removed, the dropdown is going to be highlighted and the rule won’t be working until the status is remapped.
To resolve the error:
- Click on the dropdown and select the status that corresponds to the Jira statuses mapped.
- Save status rules.
Loading of states failure. All or partial fail
It may happen that statuses may fail to load, fully or partially. In this case, You can try to load them again.
To resolve the error:
- Click the Try Again button to load the statuses.
Rule not configured entirely
It won’t be possible to save the rule if any of the statuses is not selected. Both dropdowns will be highlighted and the Save status rule button will be disabled.
To resolve the error:
- Select at least one Jira status and one Productboard status to be able to save the rule.
Unlink a feature or a subfeature from a Jira issue
No longer wish to link a Productboard feature or subfeature to a Jira issue? Accidentally pushed a feature to the wrong Jira issue? You can unlink your Jira issue, which removes the Productboard URL and allows you to relink that Jira issue to a different Productboard feature or subfeature:
- Click on the Productboard feature to open the feature description window.
- Scroll down to the Jira integration field.
- Click the broken link icon to unlink the feature from the Jira issue.
Push a release into Jira
Maker+admins can push a release and all its underlying features and subfeatures into Jira. You'll find this option in the side panel after selecting the release to access its details.
- Releases are mapped to Jira fix versions.
- If you have multiple release groups in Productboard, you can decide which one to map to Jira fix version in Productboard's Jira integration settings.
- When pushing a release into Jira you can decide whether to push just the release or push all features in the release as well.
- Releases may automatically be pushed to Jira if a feature that's already been pushed to Jira is added to that release. In this case, it's no longer possible to manually push the release (and all the rest of its features) to Jira
- All releases within the same release group must have a unique name. Creating a release without a name will create a release called "Unnamed release".
Note: Please ensure the Fix Version checkbox is ticked in the Jira Integration settings on Productboard to push the release through.
Import Jira issues into Productboard
Maker+admins can perform one-time imports of Jira issues into Productboard from Productboard's Jira integration settings. This is especially helpful if you previously used Jira to organize your feature backlog and are adopting a product management system for the first time.
If you would like to import many issues, it's recommended that you do so in batches that will all be added to the same area of your product hierarchy.
When you map custom fields of the same type between Jira and Produtboard these fields will be one-time imported from Jira to Productboard.
This applies only:
- To fields that are of the same data type. (Productboard supports text (plain-text), number, and dropdown custom fields).
- If the fields were mapped BEFORE the one-time import.
Maker+admins can also use JQL to auto-import certain types of new issues into Productboard on an ongoing basis. For example, if your team logs certain types of unexpected behavior directly in Jira, you may decide to add these to Productboard as well so they can be prioritized against other feature ideas. These features are automatically tagged Jira-auto-import so you can easily find them in Productboard. (Psst...need help writing a JQL query? Here's a cheat sheet.)
The Jira 2 way sync is used to automatically update your Productboard feature and your Jira issue when there is a change in either platform.
Note: Only an admin maker can enable the 2-way sync through in your Productboard space.
To enable 2-way sync:
- Navigate to your avatar and click Integrations ().
- Scroll down to open the specific Jira integration you would like to enable 2-way sync.
- Check the box next to 2-way sync and Click Save Changes.
Once you have selected the 2-way sync button, nothing will happen initially.
Pre-existing links will now update when there is a change in either platform.
If you have no pre-existing links, you will either need to conduct the one-time import or push individual features from Productboad to your Jira issues.
Deactivate the Jira integration
A maker+admin can deactivate the Jira integration at any time by selecting Remove on the Integrations page.
Frequently asked questions
How do I add a Jira administrator?
Follow these steps:
- Go to Settings › Projects.
- Choose the project you have connected to Productboard.
- Under 'People' click 'Add People'
- Add the project admin
Which features can I push into Jira?
Features beneath any given component can only be pushed to a single project. As soon as one feature has been pushed into a given project, all sibling features under the same component must be pushed into the same project.
If I delete a feature in Productboard that's already linked to Jira will the 2-way sync delete the story in Jira?
No, the Productboard link in Jira will disappear but the data in Jira will remain.
Is it possible to import existing Jira fix versions into Productboard?
Not quite, but there's a trick. If you create a release by the same name in Productboard, when you push features within that release into Jira, they will automatically sync with the existing fix version.
Is it possible to push a Productboard component to an epic in Jira?
It is no longer possible to push components to Jira.
Components are useful for organizing feature ideas in Productboard (e.g. around user need, product area, or technical component) but do not represent ideas that are to be executed. We recommend using features for that.
Is it possible to map the JIRA timeframe to a feature timeframe?
The JIRA timeframe can't be mapped in-app to a feature timeframe however it can be done via our API.
Watch an on-demand webinar!
Learn best practices for setting up your Jira integration. A member of Team Productboard will explain key concepts, share tips, and answer all your questions so you feel prepared to hit the ground running.
Note: Webinars are available for trial users and paid customers only.