Epic vs feature
An epic is a large body of work that spans several sprints or releases, and a feature is a piece of functionality inside it that delivers value to a user and breaks down into user stories. Where a feature sits in the hierarchy depends on the tool or framework in use. Scrum itself defines neither term.
The longer version
A common picture has three levels. An epic is the largest, a feature is the middle layer, and a user story is the piece a team finishes inside one sprint. An epic to let customers manage their own billing might hold features such as invoice history, stored payment methods and plan changes, and each of those holds the stories a team builds one at a time. The relationship between an epic and its stories is covered under epic vs user story, which mentions the feature only in passing.
No single authority fixes those levels. The Scrum Guide 2020 speaks only of Product Backlog items and uses none of the three words. Azure Boards builds the middle level in. Its Agile process ranks Epic, Feature, User Story and Task, and Microsoft's documentation describes a feature as a significant piece of functionality that might take one or more sprints, and an epic as a large body of work that can be broken down into multiple features. Jira's default hierarchy has three levels, Epic, Story and Subtask, with no feature level between them. Atlassian's documentation says Premium and Enterprise customers can create additional levels, and that a new level is created at the top of the hierarchy.
SAFe gives both words stricter meanings. It defines an epic as a significant solution development initiative, one that calls for a Lean business case and approval by portfolio leadership. A feature in SAFe is solution functionality that delivers business value and is sized to be delivered by an Agile Release Train within a planning interval, and teams split features into stories. A team moving between tools or frameworks should check what each level means locally before comparing backlogs. One rough test travels well. A story fits in a sprint, a feature is something a customer could name, and an epic is a goal that needs several features.
Common questions
What is the difference between an epic and a feature?
An epic is a large goal or body of work that takes several sprints or releases, and a feature is one distinct piece of functionality within it that delivers value to a user. Features are in turn broken down into user stories.
What is the difference between an epic, a feature and a user story?
The three are levels of size. A user story is small enough to finish in one sprint, a feature groups several stories into something a user would recognise as a capability, and an epic groups several features under one larger goal.
Does Scrum define epics and features?
The Scrum Guide 2020 defines neither. Its only unit of work is the Product Backlog item, so epic and feature are vocabulary that tools and scaling frameworks add on top of Scrum.
Does Jira have a feature level?
A feature level is absent from a new Jira site, whose default hierarchy runs Epic, Story and Subtask. On the Premium and Enterprise plans an administrator can add levels, and Atlassian's documentation places each new one at the top of the hierarchy.
How big should a feature be?
A feature should be small enough to deliver within a few sprints and large enough that a user would notice it as a capability. Microsoft's Azure Boards guidance says a feature might take one or more sprints, and SAFe sizes a feature to fit inside one planning interval.
Bug reports that arrive ready to triage.
Collect replay, console, network and browser context with the Free plan.