Jira Space Integration

This article describes the Jira Space to OnePlan Plans integration, and how it functions.

Please make sure you review our other Jira integration in case that better suits your scenario.

Overview

This integration should be used if the goal is to have a single OnePlan plan for each Jira Space within your Jira environment. Issue types/items within each space are stored and managed either in the schedule or the backlog in the OnePlan plan.

This is in contrast with the Jira Epic integration where each Jira Epic (or similar issue type) becomes a OnePlan plan.

Features

The integration supports the following features:

Connect to Jira using Tokens with Scopes (granular permissions).
Create OnePlan plans from each Jira Space.
Create Jira Space from OnePlan plans.
Connect existing OnePlan plans to existing Jira Spaces.
Create OnePlan backlog items in OnePlan from Jira items that are part of the Jira Space connected to the OnePlan plan.
Update OnePlan backlog items from connected Jira items.
Update Jira items from connected OnePlan items.
Supports custom issue types in Jira.
Synchronize custom fields and dropdowns.
Manual data import/export (plan by plan).
Automatic data sync via scheduled jobs.
Filter what data to sync.
Choose from different OneConnect subscription levels to match your needs.

Setup Requirements

To set up the Jira integration, you’ll need:

Review the Jira Authentication Methods page to decide on the method that aligns best for your company.
A Jira API token.

Setup

To configure the integration, refer to the Jira Integration Setup page.

Next Steps

After installing the integration:

Install the OnePlan Jira App from the Atlassian Marketplace.
Configure field mappings and schedule sync jobs.
Configure filters as required.
Load data from Jira into OnePlan.

Mind the Gap

Known limitations of the integration:

A numeric field in Jira that has no value will be synchronized to OnePlan with the value of zero.
Adding Jira items to your schedule requires a manual step via the OnePlan backlog view.
Depending on the amount of changes made in Jira, running a data import every hour may be unrealistic, as processing large amount of changes may take over an hour.
If creating Jira Spaces from OnePlan, only Company Managed Jira Spaces can be made. Team Managed Jira Spaces are not possible to create at this time.

Good to Know

Check out our best practices article for tips on optimizing the integration.

Troubleshooting

In case you see an error message in the log, please review the most common OneConnect errors and specific errors related to this integration first.