2019-09-04 21:01:54 +05:30
---
type: reference, howto
2020-06-23 00:09:42 +05:30
stage: Plan
2021-01-29 00:20:46 +05:30
group: Product Planning
2021-02-22 17:27:13 +05:30
info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/engineering/ux/technical-writing/#assignments
2019-09-04 21:01:54 +05:30
---
2020-03-13 15:44:24 +05:30
# Epics **(PREMIUM)**
2019-07-31 22:56:46 +05:30
2021-12-11 22:18:48 +05:30
> - Introduced in GitLab 10.2.
> - Single-level epics were [moved](https://gitlab.com/gitlab-org/gitlab/-/issues/37081) from GitLab Ultimate to GitLab Premium in 12.8.
2019-07-31 22:56:46 +05:30
2021-06-08 01:23:25 +05:30
When [issues ](../../project/issues/index.md ) share a theme across projects and milestones,
you can manage them by using epics.
2019-07-31 22:56:46 +05:30
2021-06-08 01:23:25 +05:30
You can also create child epics, and assign start and end dates,
which creates a visual roadmap for you to view progress.
2020-07-28 23:09:34 +05:30
2021-06-08 01:23:25 +05:30
Use epics:
2020-10-24 23:57:45 +05:30
2021-06-08 01:23:25 +05:30
- When your team is working on a large feature that involves multiple discussions
in different issues in different projects in a [group ](../index.md ).
- To track when the work for the group of issues is targeted to begin and end.
- To discuss and collaborate on feature ideas and scope at a high level.
2019-12-21 20:55:43 +05:30
2020-05-24 23:13:21 +05:30
## Relationships between epics and issues
2020-03-13 15:44:24 +05:30
2020-05-24 23:13:21 +05:30
The possible relationships between epics and issues are:
2020-03-13 15:44:24 +05:30
2020-05-24 23:13:21 +05:30
- An epic is the parent of one or more issues.
2021-06-08 01:23:25 +05:30
- An epic is the parent of one or more child epics. For details see [Multi-level child epics ](manage_epics.md#multi-level-child-epics ).
2020-03-13 15:44:24 +05:30
2020-05-24 23:13:21 +05:30
```mermaid
graph TD
Parent_epic --> Issue1
Parent_epic --> Child_epic
Child_epic --> Issue2
```
2019-07-31 22:56:46 +05:30
2021-02-22 17:27:13 +05:30
## Roadmap in epics **(ULTIMATE)**
2019-12-21 20:55:43 +05:30
2021-12-11 22:18:48 +05:30
> [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/7327) in GitLab 11.10.
2019-07-31 22:56:46 +05:30
2021-06-08 01:23:25 +05:30
If your epic contains one or more [child epics ](manage_epics.md#multi-level-child-epics ) that
have a start or due date, a visual
[roadmap ](../roadmap/index.md ) of the child epics is listed under the parent epic.
2019-07-31 22:56:46 +05:30
2020-04-08 14:13:33 +05:30
2019-07-31 22:56:46 +05:30
## Permissions
2021-01-03 14:25:43 +05:30
If you have access to view an epic and an issue added to that epic, you can view the issue in the
epic's issue list.
2019-07-31 22:56:46 +05:30
2021-01-03 14:25:43 +05:30
If you have access to edit an epic and an issue added to that epic, you can add the issue to or
remove it from the epic.
2019-07-31 22:56:46 +05:30
2021-06-08 01:23:25 +05:30
For a given group, the visibility of all projects must be the same as
2019-07-31 22:56:46 +05:30
the group, or less restrictive. That means if you have access to a group's epic,
then you already have access to its projects' issues.
2020-04-08 14:13:33 +05:30
You can also consult the [group permissions table ](../../permissions.md#group-members-permissions ).
2019-07-31 22:56:46 +05:30
2021-06-08 01:23:25 +05:30
## Related topics
2019-07-31 22:56:46 +05:30
2021-06-08 01:23:25 +05:30
- [Manage epics ](manage_epics.md ) and multi-level child epics.
2021-11-11 11:23:49 +05:30
- Create workflows with [epic boards ](epic_boards.md ).
2021-06-08 01:23:25 +05:30
- [Turn on notifications ](../../profile/notifications.md ) for about epic events.
- [Award an emoji ](../../award_emojis.md ) to an epic or its comments.
- Collaborate on an epic by posting comments in a [thread ](../../discussions/index.md ).
- Use [health status ](../../project/issues/managing_issues.md#health-status ) to track your progress.
2019-09-04 21:01:54 +05:30
<!-- ## Troubleshooting
Include any troubleshooting steps that you can foresee. If you know beforehand what issues
one might have when setting this up, or when something is changed, or on upgrading, it's
important to describe those, too. Think of things that may go wrong and include them here.
This is important to minimize requests for support, and to avoid doc comments with
questions that you know someone might ask.
Each scenario can be a third-level heading, e.g. `### Getting error message X` .
If you have none to add when creating a doc, leave this section in place
but commented out to help encourage others to add to it in the future. -->
