Your company runs six products across three business units. Each product team has its own Jira board, its own backlog, and its own definition of "priority." Now the CPO asks a simple question: which initiatives actually move the needle for the whole portfolio? If the silence that follows sounds familiar, you are not alone. The Jira initiative issue type was designed to solve exactly this problem — yet most organizations never use it beyond a glorified label. This guide shows you how to structure, track, and report on Jira initiatives so they become the connective tissue between day-to-day execution and portfolio-level strategy.
A Jira initiative is an issue type that sits above epics in the work-type hierarchy. It represents a large, cross-cutting body of work — typically spanning multiple epics, multiple teams, and sometimes multiple Jira projects — that ties back to a strategic goal. Initiatives are available in Jira Cloud Premium and Enterprise through Jira Plans (formerly Advanced Roadmaps).
In practical terms, the standard hierarchy looks like this:
Initiative → Epic → Story / Task → Subtask
While epics group related user stories within a single product or team, initiatives group related epics across products and teams. That distinction matters enormously for anyone responsible for product and portfolio management, because it is the first level in Jira where you can see work in terms of business outcomes rather than delivery tasks.
Key takeaway: A Jira initiative is the highest standard hierarchy level in Jira and the primary mechanism for connecting team-level execution to portfolio-level strategy.
Understanding the hierarchy on paper is easy. Making it work across a real multi-product organization is where things get complicated.
Before you can use initiatives, a Jira administrator needs to add the initiative issue type to each relevant project's issue type scheme and map it to the correct hierarchy level in Jira Plans. The setup steps are straightforward:
Create the initiative issue type in your Jira site settings under Work Items → Work Type Hierarchy.
Add the initiative issue type to the issue type schemes of every project that will contribute to portfolio-level planning.
Map the hierarchy in Jira Plans so that initiatives sit at Level 2, above epics (Level 1) and stories (Level 0).
Create a plan in Jira Plans and add each contributing project as an issue source.
Once configured, you can create initiative issues, link epics from different projects as children, and visualize everything on a single timeline.
The real power of an initiative in Jira emerges when you attach epics that live in different Jira projects. For example, an initiative called "Unified onboarding experience" might include:
An epic in the Web App project for the new onboarding wizard
An epic in the Mobile project for the guided tour flow
An epic in the API Platform project for the new tenant provisioning endpoints
An epic in the Analytics project for onboarding funnel tracking
In Jira Plans, all four epics roll up under the single initiative. Progress bars aggregate automatically, giving portfolio managers a bird's-eye view of how the initiative is tracking without having to open four separate boards.
Keep initiatives outcome-oriented. Name them after the business result, not the feature: "Reduce time-to-value for new customers by 40%" is better than "Onboarding v2."
Limit the number of active initiatives. Most portfolio teams find that 8–12 active initiatives per quarter is the maximum they can meaningfully track. More than that dilutes focus.
Use labels or custom fields for strategic themes. Tagging initiatives with themes like "Growth," "Retention," or "Platform stability" makes it easier to filter the product roadmap by strategic pillar.
If initiatives sound like the perfect portfolio management system, there is a catch. In practice, many organizations hit a ceiling once they try to scale Jira initiatives beyond a handful of teams.
Jira Plans were originally designed for program-level planning — coordinating several teams working toward a shared release. Portfolio-level planning is a different beast. When you load 15 or 20 projects into a single plan, performance degrades, the timeline becomes unreadable, and conflicting filters make the view useless for executives who need a clean summary.
A Jira initiative captures what teams are building, but it has no native fields for why it matters. There is no built-in way to attach a business case, an expected revenue impact, a customer segment, or an OKR link. Portfolio leaders end up maintaining a parallel spreadsheet or slide deck — exactly the kind of disconnected artifact that initiatives were supposed to eliminate.
Jira's ranking system works within a single plan. It does not support cross-portfolio prioritization where you weigh initiatives from Product A against initiatives from Product B based on strategic fit, resource cost, and expected return. For organizations managing a product portfolio rather than a single product, this is a critical gap.
Boards and timelines in Jira are built for delivery teams. Extracting a portfolio-level executive report — one that shows initiative health, budget status, strategic alignment, and risk — requires either heavy JQL queries, third-party dashboard tools, or manual screenshot-and-paste work. None of these options scale gracefully.
Bottom line: Jira initiatives are necessary for portfolio-level planning, but they are not sufficient. They give you the hierarchy, but they do not give you the strategic layer that portfolio leaders need to make funding, prioritization, and resource allocation decisions.
Despite the limitations, you can get significantly more value out of Jira initiatives by applying a deliberate structure. Here is a framework that works well for organizations with three or more products.
Agree on a shared set of rules across all product teams:
Naming convention: [Product/Platform] — [Outcome statement]. Example: Mobile — Reduce churn in first 30 days by 25%.
Required custom fields: Strategic theme, target quarter, confidence level (High / Medium / Low), and expected business impact (T-shirt size or dollar estimate).
Status workflow: Use a simple four-stage workflow — Proposed → Approved → In Progress → Done — so portfolio leads can filter by stage.
Instead of one massive plan, create a dedicated portfolio plan that only includes initiative-level issues. Filter out epics, stories, and tasks. This keeps the view fast and focused. Use separate team-level plans for delivery detail.
In the portfolio plan:
Group by strategic theme to see how investment is distributed.
Sort by target quarter to build a timeline-style strategic roadmap.
Color-code by product line so executives can instantly see which products carry which initiatives.
Jira will not remind you to review your portfolio. Build a recurring meeting cadence:
Weekly: Quick async check — are any initiative statuses stale? Flag blockers.
Monthly: Portfolio review with product directors. Evaluate initiative progress against expected outcomes. Reprioritize if needed.
Quarterly: Strategic planning session. Retire completed initiatives, propose new ones, and adjust resource allocation.
One of the most powerful things you can do is link every initiative to a company or business-unit OKR. While Jira does not have native OKR support, you can use a custom field or link type to create this connection. This instantly answers the question every executive asks: How does this work contribute to our goals?
For teams using an OKRs dashboard to track cross-product progress, this linkage becomes even more valuable — you can see not just whether an initiative is shipping on time, but whether it is actually moving the key result it was designed to influence.
Executive stakeholders do not want to log in to Jira. They want a concise report that answers three questions:
Are we on track? Which initiatives are green, yellow, or red?
Are we investing in the right things? How does our initiative mix align with strategic priorities?
What needs a decision? Which initiatives are blocked, underfunded, or at risk of missing their target?
Here is a simple structure for a monthly portfolio report built from Jira initiative data:
You can pull much of this data from Jira using JQL queries and dashboard gadgets. For the strategic context columns — theme, risk commentary, business impact — you will likely need to maintain a lightweight layer on top of Jira.
Set up Jira automations to keep initiative statuses honest:
Auto-flag stale initiatives. If no child epic has been updated in 14 days, move the initiative status to "Needs attention."
Progress roll-up notifications. Send a weekly Slack digest showing initiative completion percentages.
Quarterly summary export. Use Jira's API or a third-party connector to pull initiative data into your reporting tool of choice.
For organizations managing a true product portfolio — multiple products, each with their own roadmap, their own revenue stream, and their own team — Jira initiatives cover the execution layer but leave gaps in three critical areas:
Deciding whether to invest in Product A's retention initiative or Product B's new-market expansion requires a framework that considers market opportunity, strategic alignment, resource cost, and risk. Jira does not provide scoring models, portfolio-level priority matrices, or what-if scenario planning.
Portfolio management is fundamentally about allocation: where do we put our money, our people, and our attention? Jira tracks work items, not budgets. It shows you how many story points are done, but not how much capital you have committed versus remaining.
Beyond individual initiative status, portfolio leaders need to see aggregate metrics: What percentage of our portfolio is invested in growth versus maintenance? How does actual delivery compare to planned delivery across all products? What is our initiative success rate over time?
These are the questions that a dedicated product portfolio management platform is built to answer.
This is where the gap between Jira's execution layer and portfolio-level strategy becomes an opportunity. ProductZip, a product portfolio management platform, is designed to sit above your delivery tools and provide the strategic layer that Jira lacks.
With ProductZip, you can:
Pull initiative and development data from Jira (as well as Linear and Slack) into a unified portfolio view, so you are not rebuilding context manually.
Track all your products in one place — each with its own roadmap, KPIs, budget, and development progress — while seeing the bigger picture across the entire portfolio.
Plan goals on a timeline and sync the strategic roadmap with product managers and team members, ensuring that Jira initiative work stays connected to business objectives.
Estimate budget and plan funding stages for each product, so portfolio decisions are grounded in financial reality, not just delivery velocity.
Monitor product performance and KPIs across the portfolio, giving you the aggregate health metrics that Jira cannot provide.
Use AI to analyze customer feedback and sentiment across products, adding a demand signal to your prioritization decisions.
The combination is powerful: Jira handles the initiative-to-story execution hierarchy, while ProductZip handles the strategy-to-initiative portfolio layer. Teams keep working in Jira. Leaders get the visibility and decision-making tools they need in ProductZip.
If you are ready to get more value from your Jira initiatives, here is a practical starting point:
Audit your current initiatives. Delete or archive anything that does not tie to a current strategic goal.
Standardize naming and fields. Adopt a consistent naming convention and add custom fields for strategic context.
Create a portfolio-level plan. Keep it initiative-only. Use team plans for delivery detail.
Link initiatives to OKRs. Even a simple text-field link creates accountability.
Set a review cadence. Monthly portfolio reviews at minimum.
Identify the gaps. If you need cross-product prioritization, budget planning, or aggregate performance tracking, evaluate a portfolio management layer like ProductZip to complement Jira.
The Jira initiative is a capable building block for portfolio-level planning. It gives you the hierarchy to connect strategy to execution across multiple products and teams. But hierarchy alone is not strategy. The organizations that get the most value from Jira initiatives are the ones that pair them with a deliberate structure, a consistent process, and — when the portfolio outgrows what Jira can offer — a platform purpose-built for portfolio management.
If you are managing multiple product lines and need to turn Jira initiative data into portfolio-level clarity, ProductZip gives you exactly that visibility — from strategic roadmaps down to feature-level progress, all in one place.