Help Center
💡Pulse best practices

Jira epics guidelines

What Is an Epic?

An Epic represents a specific initiative with a defined outcome, not a system area or component. It should answer "what are we trying to achieve, and how will we know it's done?", not "what area of the app does this touch?"

A good Epic has a clear outcome, a natural end point (it can be closed), and one accountable owner. If it can't be closed because it's an ongoing area of the product, it's not an Epic and belongs in Components or Labels instead.

Why This Matters

Epics naming after system areas (Deposits, Customer Portal) never close, accumulate unrelated work, and make it impossible to answer "what did we ship?" Getting this right is what makes the roadmap and release reporting trustworthy.

How to Name an Epic

Name it after what's actually changing, not the feature area:

  • New functionality → signal something new is being built: Introduce Deposits, Launch Deposits
  • Existing functionality changing → describe the substance of the change: Rework Deposits Calculation, Deposits: Configurable Amounts, Expand Partial Payment Options
  • Default pattern: [Action verb] + [what changes]. A name that's just [Feature] with no verb is usually a system area in disguise.

When Is an Epic Needed?

  1. The feature spans more than one task
  2. Multiple tasks/improvements belong to the same initiative

If neither applies, skip the Epic! A task/bug/improvement outside a current initiative can stand alone. Forcing it into a generic Epic adds noise, not clarity.

What to Avoid

  • Catch-all Epics describing an area, not an initiative: UI Improvements, Infrastructure — never finish, dilute reporting.
  • Vague change names: Deposits Update (update to what?) → prefer Deposits: Configurable Amounts.

Before creating an Epic, check:

  • Does it cover more than one task, or group related tasks under one goal?
  • Is it an initiative, not a system area?
  • Is it actually in focus right now — not a catch-all for random work?
  • Does it have an owner and a clear "done"?
  • Does the name say what's changing (e.g. "Introduce X", "Rework Y") — not just the feature name?