Change milestones doc location

doc/analytics/README.md

 # Analytics
 
 - [Contribution Analytics](contribution_analytics.md)
-- (EE) [Burndown](../workflow/milestones.md#burndown-ee-only) 
+- (EE) [Burndown charts](../user/project/milestones/index.md#burndown-charts)

doc/intro/README.md

@@ -13,7 +13,7 @@ Create issues, labels, milestones, cast your vote, and review issues.
 
 - [Create a new issue](../gitlab-basics/create-issue.md)
 - [Assign labels to issues](../user/project/labels.md)
-- [Use milestones as an overview of your project's tracker](../workflow/milestones.md)
+- [Use milestones as an overview of your project's tracker](../user/project/milestones/index.md)
 - [Use voting to express your like/dislike to issues and merge requests](../workflow/award_emoji.md)
 
 ## Collaborate

doc/university/glossary/README.md

@@ -333,7 +333,7 @@ A [platform](https://www.meteor.com) for building javascript apps.
 
 ### Milestones
 
-Allow you to [organize issues](https://docs.gitlab.com/ce/workflow/milestones.html) and merge requests in GitLab into a cohesive group, optionally setting a due date. A common use is keeping track of an upcoming software version. Milestones are created per-project.
+Allow you to [organize issues](https://docs.gitlab.com/ce/user/project/milestones/) and merge requests in GitLab into a cohesive group, optionally setting a due date. A common use is keeping track of an upcoming software version. Milestones are created per-project.
 
 ### Mirror Repositories
 

doc/user/project/milestones/index.md

+# Milestones
+
+Milestones allow you to organize issues and merge requests into a cohesive group, optionally setting a due date.
+A common use is keeping track of an upcoming software version. Milestones are created per-project.
+
+You can find the milestones page under your project's **Issues ➔ Milestones**.
+
+## Creating a milestone
+
+To create a new milestone, simply click the **New milestone** button when in the
+milestones page. A milestone can have a title, a description and start/due dates.
+Once you fill in all the details, hit the **Create milestone** button.
+
+>**Note:**
+The start/due dates are required if you intend to use [Burndown charts](#burndown-charts).
+
+![Creating a milestone](img/milestone_create.png)
+
+## Groups and milestones
+
+You can create a milestone for several projects in the same group simultaneously.
+On the group's **Issues ➔ Milestones** page, you will be able to see the status
+of that milestone across all of the selected projects. To create a new milestone
+for selected projects in the group, click the **New milestone** button. The
+form is the same as when creating a milestone for a specific project with the
+addition of the selection of the projects you want to inherit this milestone.
+
+![Creating a group milestone](img/milestone_group_create.png)
+
+## Special milestone filters
+
+In addition to the milestones that exist in the project or group, there are some
+special options available when filtering by milestone:
+
+* **No Milestone** - only show issues or merge requests without a milestone.
+* **Upcoming** - show issues or merge request that belong to the next open
+  milestone with a due date, by project. (For example: if project A has
+  milestone v1 due in three days, and project B has milestone v2 due in a week,
+  then this will show issues or merge requests from milestone v1 in project A
+  and milestone v2 in project B.)
+* **Started** - show issues or merge requests from any milestone with a start
+  date less than today. Note that this can return results from several
+  milestones in the same project.
+
+## Burndown charts
+
+> [Introduced][ee-1540] in GitLab Enterprise Edition 9.1 and is available for
+  [Enterprise Edition Starter][ee] users.
+
+A burndown chart is available for every project milestone that has a set start
+date and a set due date and is located on the project's milestone page.
+
+It indicates the project's progress throughout that milestone (for issues that
+have that milestone assigned to it). In particular, it shows how many issues
+were or are still open for a given day in the milestone period. Since GitLab
+only tracks when an issue was last closed (and not its full history), the chart
+assumes that issue was open on days prior to that date. Reopened issues are
+considered as open on one day after they were closed.
+
+The burndown chart can also be toggled to display the cumulative open issue
+weight for a given day. When using this feature, make sure your weights have
+been properly assigned, since an open issue with no weight adds zero to the
+cumulative value.
+
+![burndown chart](img/burndown_chart.png)
+
+Closed or reopened issues prior to GitLab 9.1 version won't have a `closed_at`
+value, so the burndown chart considers it as closed on the milestone `start_date`.
+In that case, a warning will be displayed.
+
+![burndown chart warning](img/burndown_warning.png)
+
+[ee-1540]: https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/1540
+[ee]: https://about.gitlab.com/gitlab-ee

doc/workflow/README.md

@@ -30,7 +30,7 @@
 - [Time tracking](time_tracking.md)
 - [Web Editor](../user/project/repository/web_editor.md)
 - [Releases](releases.md)
-- [Milestones](milestones.md)
+- [Milestones](../user/project/milestones/index.md)
 - [Merge Requests](../user/project/merge_requests/index.md)
   - [Authorization for merge requests](../user/project/merge_requests/authorization_for_merge_requests.md)
   - [Cherry-pick changes](../user/project/merge_requests/cherry_pick_changes.md)

doc/workflow/milestones.md

-# Milestones
-
-Milestones allow you to organize issues and merge requests into a cohesive group, optionally setting a due date.
-A common use is keeping track of an upcoming software version. Milestones are created per-project.
-
-You can find the milestones page under your project's **Issues ➔ Milestones**.
-
-## Creating a milestone
-
-To create a new milestone, simply click the **New milestone** button when in the
-milestones page. A milestone can have a title, a description and start/due dates.
-Once you fill in all the details, hit the **Create milestone** button.
-
->**Note:**
-The start/due dates are required if you intend to use [Burndown charts](#burndown-charts).
-
-![milestone form](milestones/milestone_create.png)
-
-## Groups and milestones
-
-You can create a milestone for several projects in the same group simultaneously.
-On the group's **Issues ➔ Milestones** page, you will be able to see the status
-of that milestone across all of the selected projects. To create a new milestone
-for selected projects in the group, click the **New milestone** button. The
-form is the same as when creating a milestone for a specific project with the
-addition of the selection of the projects you want to inherit this milestone.
-
-![group milestone form](milestones/milestone_group_create.png)
-
-## Special milestone filters
-
-In addition to the milestones that exist in the project or group, there are some
-special options available when filtering by milestone:
-
-* **No Milestone** - only show issues or merge requests without a milestone.
-* **Upcoming** - show issues or merge request that belong to the next open
-  milestone with a due date, by project. (For example: if project A has
-  milestone v1 due in three days, and project B has milestone v2 due in a week,
-  then this will show issues or merge requests from milestone v1 in project A
-  and milestone v2 in project B.)
-* **Started** - show issues or merge requests from any milestone with a start
-  date less than today. Note that this can return results from several
-  milestones in the same project.
-
-## Burndown charts
-
-> [Introduced][ee-1540] in GitLab Enterprise Edition 9.1 and is available for
-  [Enterprise Edition Starter][ee] users.
-
-A burndown chart is available for every project milestone that has a set start
-date and a set due date and is located on the project's milestone page.
-
-It indicates the project's progress throughout that milestone (for issues that
-have that milestone assigned to it). In particular, it shows how many issues
-were or are still open for a given day in the milestone period. Since GitLab
-only tracks when an issue was last closed (and not its full history), the chart
-assumes that issue was open on days prior to that date. Reopened issues are
-considered as open on one day after they were closed.
-
-The burndown chart can also be toggled to display the cumulative open issue
-weight for a given day. When using this feature, make sure your weights have
-been properly assigned, since an open issue with no weight adds zero to the
-cumulative value.
-
-![burndown chart](milestones/burndown_chart.png)
-
-Closed or reopened issues prior to GitLab 9.1 version won't have a `closed_at`
-value, so the burndown chart considers it as closed on the milestone `start_date`.
-In that case, a warning will be displayed.
-
-![burndown chart warning](milestones/burndown_warning.png)
-
-[ee-1540]: https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/1540
-[ee]: https://about.gitlab.com/gitlab-ee
+This document was moved to [another location](../user/project/milestones/index.md).