Edited "Epics" to comply with SSOT
This commit is contained in:
parent
80307e7b43
commit
7a2bebc9a2
|
@ -1,3 +1,7 @@
|
||||||
|
---
|
||||||
|
type: reference, howto
|
||||||
|
---
|
||||||
|
|
||||||
# Epics **[ULTIMATE]**
|
# Epics **[ULTIMATE]**
|
||||||
|
|
||||||
> Introduced in [GitLab Ultimate][ee] 10.2.
|
> Introduced in [GitLab Ultimate][ee] 10.2.
|
||||||
|
@ -215,3 +219,15 @@ Once you wrote your comment, you can either:
|
||||||
## Notifications
|
## Notifications
|
||||||
|
|
||||||
- [Receive notifications](../../../workflow/notifications.md) for epic events.
|
- [Receive notifications](../../../workflow/notifications.md) for epic events.
|
||||||
|
|
||||||
|
<!-- ## 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. -->
|
||||||
|
|
Loading…
Reference in New Issue