Stop Drowning in Epics: How to Configure Initiatives in Jira Cloud

There is a specific moment in every scaling company’s life when "Epics" stop working.

I saw this with a client just last month. Their backlog wasn’t a prioritized list anymore; it was a parking lot of 400 unconnected Epics. The CTO couldn't see the big picture because everything was flattened into the same tier. They didn't need a new project; they needed a new altitude.

If your Epics are too big to be manageable but too small to justify a whole new Jira Project, you are missing the most critical layer in the Jira hierarchy: The Initiative.

⚠️ Note on Interface: The video above walks through the logic using an older version of Jira. The core concepts are identical, but I have updated the step-by-step guide below to match the current 2026 Jira Cloud "Plans" interface.

The Prerequisite: You Need "Premium"

Before you start clicking, a reality check: The custom hierarchy features we are building today require Jira Cloud Premium (formerly known as "Portfolio" or "Advanced Roadmaps").

While you can hack an issue type called "Initiative" in the Standard plan, you will lose the ability to visualize the parent/child relationships. Without the "Plans" feature, your Initiative is just another ticket floating in the void.

Step 1: Create the "Initiative" Issue Type

By default, Jira stops at the Epic level. We need to manually tell Jira that a new container exists.

1. Go to Settings (The Cog) > Issues.
2. Select Issue types and click Add issue type.
3. Name it Initiative.
   • Pro Tip: Use a distinct icon (like the purple shield or the large roadmap icon) so it stands out visually on the board against purple Epics.

Step 2: Configure the Hierarchy Levels

Creating the ticket isn't enough; you have to tell Jira where it sits in the food chain.

1. Go to Settings > Products.
2. On the left sidebar, look for Advanced Roadmaps (or Plans) > Hierarchy configuration.
3. Click + Create Level.
4. Name the level Legend (or Initiative) and map your new "Initiative" issue type to this level.
5. Ensure it is placed above the Epic level.

Step 3: The "Parent Link" Field (Crucial Step)

This is the step most admins miss. If you don't expose the specific linking field, you won't be able to connect an Epic to an Initiative.

1. Go to Settings > Issues > Screens.
2. Find the Default Screen (or the specific screen scheme used by your project).
3. Add the field called Parent Link.
   • Note: Do not confuse this with the standard "Parent" field used for Subtasks. You specifically need Parent Link for hierarchies above Epic.

Step 4: Visualizing the "Mini-Project" in Plans

Now that the plumbing is connected, you can build the view.

1. Navigate to Plans in the top menu and create a new Plan.
2. Select your Issue Sources (Board, Project, or Filter).
3. In the Settings > Hierarchy, ensure your range includes Initiative to Sub-task.

You can now drag and drop existing Epics "under" your new Initiatives directly in the timeline view.

Technically, setting this up takes 10 minutes. Strategically, most teams get it wrong.

I often see teams trying to use Initiatives as "Buckets" for random work (e.g., "Marketing Initiatives"). This is a mistake.

In my experience, Initiatives work best when treated as Mini-Projects. They are for bodies of work that are:

• Too big to be an Epic (it will take more than a quarter to finish).
• Too small to be a dedicated Jira Project (it doesn't need a separate workflow or permission scheme).

A Note on Visibility: If your organization doesn't have Jira Premium, I generally advise against using this structure. Without the "Plans" view, the visibility of Initiatives is poor. However, if you are on Premium, the new List View updates have made this much easier to manage, allowing you to expand/collapse these hierarchies right from the navigator.

Ready to clean up your Jira instance?

If you are struggling with a messy backlog, adding layers might complicate things before it simplifies them.

• Option A: I’ve compiled a Jira Hierarchy Configuration Checklist that walks you through the permission schemes and screen setups I mentioned above. You can download it for free in my community. [Download PDF in Community]
• Option B: Don't have time to configure this yourself? I can audit your current hierarchy and deploy this structure for you in a 3-Day Sprint. I handle the build, the testing, and the team training. [Check Sprint Availability]