Jira Epics Integrations - Resource Planner Import

The Resource Planner in OnePlan provides visibility into who is assigned to which work items, how much effort is planned, and when that work is scheduled. When connected to Jira, the Resource Planner pulls in assignments and effort directly from your work items—enabling seamless alignment between your development teams and project/resource management.

The best part? This update happens automatically as part of the integration. Each time the OnePlanUpdate strategy runs, the Resource Planner is updated for every plan touched during that sync—no additional configuration required. As long as the right fields are mapped and data exists at the right level, updates flow straight into the Resource Planner without manual intervention.

This allows Project and Resource Managers to view current resource demand and availability across all synchronized plans, without duplicating work across systems.

Prerequisites

Jira Epics integration must be configured

The integration between Jira and OnePlan must be set up, and the relevant fields – Start, Due, Effort, and Assigned To – must be mapped in the Backlog – Issues table within OneConnect.

The OnePlan plan must already exist

Plans newly created through the Jira Integration won’t update the Resource Planner until after they have been saved in OnePlan. The Resource Planner will update during subsequent syncs after the first initial sync.

Work item details must exist at the lowest level of your hierarchy

Only the most detailed level of issue types (e.g., Story, Task, Bug if you are using the Epic -> Task, Story, Bug structure) will be included in the Resource Planner. These items must have:

Start
Due
Effort
Assigned To (Resource/Person)

Higher-level issue types (like Epic) will not show in the Resource Planner. This aligns with project management best practices, where detailed work and estimates are tracked at the lowest level and roll up to parent items.

Mind the Gap

The plan must already exist

If the plan was just created in Jira and brought into OnePlan, the Resource Planner would not update. The Resource Planner will update for plans that have already been established in OnePlan. If you do not see the Resource Planner populated, then please sync the data a second time to verify.

Only the most detailed work items will appear in the Resource Planner

In Jira, issue types are often organized in layers (Epic -> Task, Story, Bug). Only the lowest level items – whatever that may be for your setup- will sync to the Resource Planner. To show up, these items need to have a start date, due date, effort, and someone assigned. This follows best practices where detailed planning happens at the most granular level, with information rolling up to higher-level items.