Commit b4f17280 authored by Marcin Sedlak-Jakubowski's avatar Marcin Sedlak-Jakubowski

Merge branch 'docs-remove-overview-plan' into 'master'

Doc: Remove unneeded Overview header from pages

See merge request gitlab-org/gitlab!43780
parents f1292137 9368fbac
...@@ -8,8 +8,6 @@ info: To determine the technical writer assigned to the Stage/Group associated w ...@@ -8,8 +8,6 @@ info: To determine the technical writer assigned to the Stage/Group associated w
> [Introduced](https://gitlab.com/gitlab-org/gitlab-foss/-/merge_requests/5554) in [GitLab 8.11](https://about.gitlab.com/releases/2016/08/22/gitlab-8-11-released/#issue-board). > [Introduced](https://gitlab.com/gitlab-org/gitlab-foss/-/merge_requests/5554) in [GitLab 8.11](https://about.gitlab.com/releases/2016/08/22/gitlab-8-11-released/#issue-board).
## Overview
The GitLab Issue Board is a software project management tool used to plan, The GitLab Issue Board is a software project management tool used to plan,
organize, and visualize a workflow for a feature or product release. organize, and visualize a workflow for a feature or product release.
It can be used as a [Kanban](https://en.wikipedia.org/wiki/Kanban_(development)) or a It can be used as a [Kanban](https://en.wikipedia.org/wiki/Kanban_(development)) or a
......
...@@ -8,8 +8,6 @@ info: To determine the technical writer assigned to the Stage/Group associated w ...@@ -8,8 +8,6 @@ info: To determine the technical writer assigned to the Stage/Group associated w
> [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/1904) in [GitLab Starter 9.2](https://about.gitlab.com/releases/2017/05/22/gitlab-9-2-released/#multiple-assignees-for-issues). > [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/1904) in [GitLab Starter 9.2](https://about.gitlab.com/releases/2017/05/22/gitlab-9-2-released/#multiple-assignees-for-issues).
## Overview
In large teams, where there is shared ownership of an issue, it can be difficult In large teams, where there is shared ownership of an issue, it can be difficult
to track who is working on it, who already completed their contributions, who to track who is working on it, who already completed their contributions, who
didn't even start yet. didn't even start yet.
......
...@@ -6,8 +6,6 @@ info: To determine the technical writer assigned to the Stage/Group associated w ...@@ -6,8 +6,6 @@ info: To determine the technical writer assigned to the Stage/Group associated w
# Labels # Labels
## Overview
As your count of issues, merge requests, and epics grows in GitLab, it's more and more challenging As your count of issues, merge requests, and epics grows in GitLab, it's more and more challenging
to keep track of those items. Especially as your organization grows from just a few people to to keep track of those items. Especially as your organization grows from just a few people to
hundreds or thousands. This is where labels come in. They help you organize and tag your work hundreds or thousands. This is where labels come in. They help you organize and tag your work
......
...@@ -14,8 +14,6 @@ info: To determine the technical writer assigned to the Stage/Group associated w ...@@ -14,8 +14,6 @@ info: To determine the technical writer assigned to the Stage/Group associated w
> value, so the burndown chart considers them as closed on the milestone > value, so the burndown chart considers them as closed on the milestone
> `start_date`. In that case, a warning will be displayed. > `start_date`. In that case, a warning will be displayed.
## Overview
Burndown Charts are visual representations of the progress of completing a milestone. Burndown Charts are visual representations of the progress of completing a milestone.
![burndown chart](img/burndown_chart.png) ![burndown chart](img/burndown_chart.png)
......
...@@ -7,8 +7,6 @@ info: To determine the technical writer assigned to the Stage/Group associated w ...@@ -7,8 +7,6 @@ info: To determine the technical writer assigned to the Stage/Group associated w
# Milestones # Milestones
## Overview
Milestones in GitLab are a way to track issues and merge requests created to achieve a broader goal in a certain period of time. Milestones in GitLab are a way to track issues and merge requests created to achieve a broader goal in a certain period of time.
Milestones allow you to organize issues and merge requests into a cohesive group, with an optional start date and an optional due date. Milestones allow you to organize issues and merge requests into a cohesive group, with an optional start date and an optional due date.
......
...@@ -10,8 +10,6 @@ info: To determine the technical writer assigned to the Stage/Group associated w ...@@ -10,8 +10,6 @@ info: To determine the technical writer assigned to the Stage/Group associated w
> - [Moved](https://gitlab.com/gitlab-org/gitlab/-/issues/214839) to [GitLab Starter](https://about.gitlab.com/pricing/) in 13.0. > - [Moved](https://gitlab.com/gitlab-org/gitlab/-/issues/214839) to [GitLab Starter](https://about.gitlab.com/pricing/) in 13.0.
> - [Moved](https://gitlab.com/gitlab-org/gitlab/-/issues/215364) to [GitLab Core](https://about.gitlab.com/pricing/) in 13.2. > - [Moved](https://gitlab.com/gitlab-org/gitlab/-/issues/215364) to [GitLab Core](https://about.gitlab.com/pricing/) in 13.2.
## Overview
Service Desk is a module that allows your team to connect directly Service Desk is a module that allows your team to connect directly
with any external party through email right inside of GitLab; no external tools required. with any external party through email right inside of GitLab; no external tools required.
An ongoing conversation right where your software is built ensures that user feedback ends An ongoing conversation right where your software is built ensures that user feedback ends
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment