How to Create Epics in Jira: A Complete Step-by-Step Guide
Need to organize a big Jira goal? Learn how to create epics in Jira, add related stories and tasks, and track progress. Read now to get started.
Creating an epic in Jira gives a large goal a clear place in your project, with related work grouped beneath it. You can create one from a Jira backlog or through an issue-creation screen, then add stories and tasks that support the goal.
Without that structure, a broad initiative can become a collection of disconnected tickets. Teams may miss dependencies, lose sight of progress, or struggle to explain how small tasks contribute to a larger outcome.
But here's the truth: an epic only helps when its purpose, scope, and child issues are clear. In this guide, I’ll walk you through creating an epic, organizing its work, and keeping it useful as your project changes.
How to create an epic in Jira: step-by-step
The quickest route is usually the backlog in a Jira Software project. The exact labels can vary by Jira version and project type, so use the issue-creation screen if you don’t see an epic panel.
-
Open the right project. Go to the Jira project where the team will complete the work. Check that you have permission to create issues and that the project supports epics.
-
Open the backlog. In a Jira Software project, choose the project’s backlog view. In many company-managed projects, an epics panel appears beside the backlog. Some team-managed projects use different navigation or issue views.
-
Start a new epic. Select the option to create an epic in the epics panel, if available. Otherwise, choose Create and select Epic as the issue type. If Epic is missing, ask a Jira administrator whether the issue type is enabled for your project.
-
Write a specific epic name. Choose a short name that teammates can recognize in a backlog or report. For example, Improve account recovery is clearer than Security work.
-
Add the epic details. Describe the outcome, the users or teams affected, and what completion means. You might write: “Let customers reset a forgotten password without contacting support.” Add an owner, target dates, labels, or other fields your team uses.
-
Create the epic. Review the issue type, project, and required fields, then submit the form. Jira should create an epic issue with its own key, such as WEB-42.
-
Add stories and tasks beneath it. From the backlog, drag issues into the epic or open an issue and set its parent epic. In some Jira versions, the relationship appears as a parent field. Confirm that each child issue belongs to the intended epic.
-
Check the epic in a planning view. Review the backlog, board, or roadmap available to your project. Confirm the epic and its child issues are visible, and that the work reflects the goal you described.
Here's why: creating the issue is only the first step. The epic becomes useful when the team can connect its day-to-day work to a meaningful outcome.

What an epic does in Jira
An epic is a large body of related work that can be divided into smaller issues, such as stories, tasks, and bugs. It helps you group work around a feature, customer outcome, or substantial project goal.
For example, an online store might create an epic called Launch gift cards. Child issues could cover gift-card purchases, balance checks, email delivery, and customer support guidance.
Epics are larger than individual stories, but their position in the issue hierarchy can depend on your Jira plan and configuration. Some teams also use higher-level planning items, such as initiatives. Check your project’s issue types and hierarchy before planning several levels of work.
Plan the epic before you create it
A little planning makes it easier to create an epic the team can understand and finish. Start with the result you want, rather than a list of implementation tasks.
Define the outcome and boundaries
Write one sentence explaining what should change when the epic is complete. Then note what belongs inside its scope and what does not. For example, a “guest checkout” epic might include order placement without an account, while a loyalty program remains out of scope.
Clear boundaries help teammates decide whether a new request belongs in the epic. They also make progress easier to discuss during planning meetings.
Choose a useful name and owner
Use a short, recognizable name that describes the outcome. Assign an owner who can answer questions about priority and scope, even when several people will complete the work.
A name such as Reduce checkout abandonment gives more context than Checkout project. Add a brief description with the intended audience, success criteria, and important constraints.
Organize stories and tasks under the epic
After creating the epic, break the goal into deliverable pieces. Each child issue should describe work that someone can estimate, prioritize, and complete.
Keep child issues focused
Suppose your epic is Improve account recovery. Possible child issues include adding a password-reset request screen, sending a time-limited reset link, and showing a confirmation after the password changes.
Those issues are easier to review than one large ticket called Build account recovery. If a child issue is still too large, split it again or clarify its acceptance criteria.
Set the parent relationship correctly
Jira may let you associate work with an epic through the backlog, a parent field, or an epic-related field. The available method depends on your project setup and Jira version.
After linking an issue, check that it appears under the intended epic. A task can look complete on a board while remaining outside the epic if its parent relationship was never set.
Preserve the team’s normal workflow
Use your project’s existing statuses, estimates, and sprint planning practices. An epic is a grouping and planning level; it does not replace the team’s process for moving individual issues through delivery.
For example, a team can keep its regular sprint board while using the epic view to understand how several sprints contribute to a larger feature.
Track progress and keep the epic current
Once work is underway, use the epic to discuss scope, dependencies, and progress. Jira’s available views and reports vary by project type, configuration, and subscription, so check which options your team can access.
Review child issues, not just the epic label
An epic may appear active even when its child issues are blocked or unfinished. Review issue statuses and unresolved dependencies, then decide whether the plan needs adjustment.
For instance, if a password-reset email depends on a messaging service change, make that dependency visible. The team can then plan the work in the right order.
Update scope when priorities change
Projects evolve. If a request changes the intended outcome or adds substantial work, update the epic description and discuss whether the new work belongs there.
Moving unrelated tickets into an epic just to make them easier to find can make progress confusing. Keep the relationship tied to the same goal.
Close the loop at completion
When the work is done, review whether the agreed outcome was achieved. Close completed issues, resolve remaining work, and capture any follow-up that should move into another epic.
This final review helps the team distinguish delivered work from work that was simply moved out of view.
Value proposition: ONES.com brings project management and knowledge management together on one platform, with ONES Project available for teams looking for a Jira alternative. ONES Project and ONES Wiki are sold separately.

For teams reviewing how they manage epics, the practical question is whether a platform can support planning, execution, and team knowledge without adding unnecessary complexity. Here are several ways ONES Project addresses common planning needs.
Core capabilities
Planning feels scattered: ONES Project offers custom workflows and fields, so teams can represent their planning process in the project. The result is work that better reflects how the team operates.
Epic work is hard to track: Built-in reporting helps teams review project progress. This gives leads a way to discuss delivery without relying only on individual ticket updates.
Sprint planning needs structure: Sprint management supports planning work across iterations. Teams can connect sprint-level activity with broader project goals.
Repeated actions take time: Automation can handle selected routine workflow actions. That can reduce manual steps for common processes.
Jira workflows are already familiar: Jira-compatible workflows can make the transition more approachable for teams with established Jira practices.
Too many add-ons complicate operations: Native capabilities can reduce reliance on plugins for common planning and workflow needs. Teams can evaluate which extensions they still require.
Deployment requirements vary: ONES.com supports Cloud, On-Premise, Private Cloud, and Air-gapped deployments. This gives organizations options for different infrastructure and network needs.
Self-hosting raises feature concerns: ONES.com offers full feature parity between its cloud and self-hosted versions. Teams can assess deployment needs without choosing a reduced feature set.
Application scenarios
A product team could use ONES Project to organize a multi-sprint feature epic, manage child issues, and review progress through built-in reporting. Custom fields could capture details such as a target release or responsible team.
An organization with restricted network requirements could evaluate an On-Premise, Private Cloud, or Air-gapped deployment. A team that also needs knowledge management can consider ONES Wiki separately; it serves as a knowledge base and a Confluence alternative.
ONES.com includes a free plan for up to 30 seats. Its platform is powered by ONES Assistant, and organizations can assess the project and knowledge management products separately to match their needs.
Common challenges when creating Jira epics
The Epic issue type is missing
Problem: You open the create menu and cannot select Epic. Solution: Check whether you are in the correct project and ask a Jira administrator to review the project’s issue types and permissions.
Child issues do not appear under the epic
Problem: A story exists, but it is absent from the epic view. Solution: Open the story and check its parent or epic relationship. Set the correct epic, then refresh the planning view.
The epic keeps growing
Problem: New requests turn one goal into a catch-all. Solution: Compare each request with the epic’s intended outcome. Move unrelated work into a separate epic or backlog item.
The epic name is too broad
Problem: Names such as Platform improvements leave teammates unsure about the goal. Solution: Name the outcome and add a short description with scope and success criteria.
Frequently asked questions
Can I create an epic from the Jira backlog?
In many Jira Software projects, yes. Open the backlog and look for an epics panel or an option to add an epic. The interface can vary between company-managed and team-managed projects. If the option is missing, use the create screen and select Epic, or ask a Jira administrator to check your project configuration and permissions.

How do I add a story to an epic in Jira?
Depending on your Jira setup, you can drag a story into an epic in the backlog or open the story and set its parent epic. Then verify the relationship in the backlog or epic view. If the story does not appear, check that it belongs to the correct project and that the parent field points to the intended epic.
Can an epic contain another epic?
In many standard Jira Software setups, epics group stories, tasks, and similar issues rather than other epics. Higher-level planning may require an additional hierarchy level, which can depend on your Jira plan and configuration. Check the issue hierarchy available in your organization before designing a multi-level structure.
What should I include in an epic description?
Describe the outcome, the audience or team affected, and what completion means. Add scope boundaries, important dependencies, and relevant constraints when they help the team make decisions. For example, a checkout epic might state that customers can place an order without creating an account, while loyalty rewards remain outside its scope.
Can I change an epic after creating it?
Yes. You can generally update its name, description, fields, and child issues, subject to your project permissions and configuration. If the goal changes substantially, explain the revised scope to the team and review which issues still belong. For a major change, a separate epic may make planning and progress easier to understand.
Conclusion
Creating an epic in Jira starts with a clear outcome, a useful name, and the right issue type. Add focused stories and tasks, confirm their parent relationship, and review progress as the work develops.
But here's the truth: an epic is only as clear as the goal and boundaries behind it. If you keep those visible, your team can connect everyday tasks to the larger result and adjust the plan when priorities shift.
If Jira’s setup no longer fits your team, ONES Project is one Jira alternative to evaluate for epic-based planning. Choose the approach that helps your team understand the work, coordinate delivery, and keep progress visible.