This article describes the Jira Epics 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
The following video details how the Jira Epics to OnePlan Plans integration works.
This integration should be used if the goal is to have a single OnePlan plan for each Jira Epic or similar issue type. Child items of the connected epic will be stored and managed in the schedule or the backlog in the OnePlan plan.
This is in contrast with the Jira Project integration where each Jira Project becomes a OnePlan plan.
Features
The integration supports the following features:
- Create OnePlan plans from Jira Epics (or similar issue types).
- Create Jira Epics (or similar issue types) from OnePlan.
- Connect existing OnePlan plans to existing Jira Epics (or similar issue types).
- Create OnePlan tasks in the schedule from Jira items that are the child of the item connected to the OnePlan plan.
- Create OnePlan backlog items in OnePlan from Jira items that are the child of the item connected to the OnePlan plan.
- Update OnePlan tasks or 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:
- A Jira API token.
- Decide if you want to manage your Jira data in the schedule using tasks or in the backlog.
Setup
To configure the integration, refer to the Jira Integration Setup page.
Next Steps
After installing the integration:
- Configure custom issue types that you use in Jira if required.
- Configure field mappings and schedule sync jobs.
- Configure pre-filters or 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.
- 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.
Related to