Jira Project Integration

  • Updated

This article describes the Jira Project 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 Project. Items in the Jira projects 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.

 

 

Screenshot__17_.png

Features

The integration supports the following features:

  • Create OnePlan plans from Jira Projects.
  • Create Jira Projects from OnePlan.
  • Connect existing OnePlan plans to existing Jira Projects.
  • Create OnePlan backlog items in OnePlan from Jira items that are part of the Jira Project 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:

Setup

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

Next Steps

After installing the integration:

  • 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.  

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.

Was this article helpful?

0 out of 0 found this helpful

Have more questions? Submit a request