There are several different types of Jira integrations that can be used with OnePlan.

The main difference is how Jira data is connected to OnePlan plans or work items.

Use Cases

Here are some of the most popular use cases for our Jira integrations:

Portfolio Planning and Management

Strategic Planning to Agile Execution Alignment

A portfolio manager creates a plan in OnePlan to track a strategic initiative. The integration links this plan to a Jira Epic. Child issues (Stories, Tasks, Bugs) are automatically synced, giving visibility into execution progress at the portfolio level.

Centralized Resource Management

Resource assignments in Jira sync to OnePlan. Resource managers use OnePlan to analyze workload and availability across projects, including those managed in Jira. This helps identify over- or under-utilization across agile teams.

Top-Down Planning with Automatic Work Breakdown

A project manager defines high-level deliverables in OnePlan and pushes them as Epics into Jira. Developers then break them down into child issues in Jira, which are automatically pulled back into OnePlan for consolidated tracking.

Capacity Planning Across Epics

Resource Managers use OnePlan to evaluate future demand based on Epics scheduled in Jira. As new Epics are created and linked, their associated effort (based on child issues) feeds into capacity models in OnePlan for proactive staffing decisions.

Execution

Progress Tracking Across Teams

PMO leaders use OnePlan to track progress of Epics across multiple teams. As teams update issues in Jira, OnePlan reflects real-time status updates without manual reporting.

Integrated Financial Planning

Cost estimates and actuals are managed in OnePlan at the plan level. Jira project activities feed time and effort data into OnePlan for budgeting and forecasting. The PMO has visibility into the financials

Change Management and Impact Analysis

A change in Jira (e.g., scope increase or delay) automatically updates the linked plan in OnePlan. Project Managers can quickly assess the impact across portfolios or dependencies.

Skill-Based Resource Allocation

OnePlan fields are mapped to skills or roles. As Jira Epics are synced, Resource Managers can see which types of resources (e.g., Developers, QA, UX) are being consumed per initiative and adjust allocations accordingly to meet delivery needs.

Reporting

Milestone and Timeline Reporting

A project manager sets target dates in OnePlan for an Epic and syncs them with Jira. Developers manage the details in Jira, while the PM monitors schedule performance in OnePlan.

Unified Status Reporting for Executives

Epics across multiple Jira boards are synced into OnePlan. Executives view real-time status dashboards in OnePlan without needing Jira access.

Cross-Functional Reporting

Project data from multiple Jira projects is brought into OnePlan to provide consolidated reporting on delivery, capacity, and risk across departments.

Subscription

Jira integrations are licensed individually. A single integration can only connect to a single Atlassian organization.

Review the different OneConnect Subscription types to determine which options fits your company's requirements.

Jira Projects Integration

The Jira Projects integration is best for teams managing larger or standalone Jira projects that align with OnePlan plans.

Please review this article for features, setup requirements, instructions and more.

Jira Epics Integration

The Jira Epics integration is ideal for teams that manage work using issue types (epics, features etc.) that maps to plans in OnePlan. In this case, an epic in Jira would become a plan in OnePlan and any child issues would be part of that plan.