Docs: Fixing anchors and links for all docs related to issues.
This commit is contained in:
Marcel Amirault
Evan Read
parent
83153e65a5
commit
b3587a8beb
7 changed files with 34 additions and 41 deletions
|
|
@ -36,34 +36,34 @@ To get familiar with the concepts needed to develop code on GitLab, read the fol
|
|||
|
||||
GitLab is a Git-based platform that integrates a great number of essential tools for software development and deployment, and project management:
|
||||
|
||||
- Hosting code in repositories with version control
|
||||
- Hosting code in repositories with version control.
|
||||
- Tracking proposals for new implementations, bug reports, and feedback with a
|
||||
fully featured [Issue Tracker](project/issues/index.md#issue-tracker)
|
||||
- Organizing and prioritizing with [Issue Boards](project/issues/index.md#issue-boards)
|
||||
fully featured [Issue Tracker](project/issues/index.md#issue-tracker).
|
||||
- Organizing and prioritizing with [Issue Boards](project/issues/index.md#issue-board).
|
||||
- Reviewing code in [Merge Requests](project/merge_requests/index.md) with live-preview changes per
|
||||
branch with [Review Apps](../ci/review_apps/index.md)
|
||||
- Building, testing and deploying with built-in [Continuous Integration](../ci/README.md)
|
||||
- Deploying personal and professional static websites with [GitLab Pages](project/pages/index.md)
|
||||
- Integrating with Docker by using [GitLab Container Registry](project/container_registry.md)
|
||||
- Tracking the development lifecycle by usingn [GitLab Cycle Analytics](project/cycle_analytics.md)
|
||||
branch with [Review Apps](../ci/review_apps/index.md).
|
||||
- Building, testing, and deploying with built-in [Continuous Integration](../ci/README.md).
|
||||
- Deploying personal and professional static websites with [GitLab Pages](project/pages/index.md).
|
||||
- Integrating with Docker by using [GitLab Container Registry](project/container_registry.md).
|
||||
- Tracking the development lifecycle by using [GitLab Cycle Analytics](project/cycle_analytics.md).
|
||||
|
||||
With GitLab Enterprise Edition, you can also:
|
||||
|
||||
- Provide support with [Service Desk](https://docs.gitlab.com/ee/user/project/service_desk.html)
|
||||
- Provide support with [Service Desk](https://docs.gitlab.com/ee/user/project/service_desk.html).
|
||||
- Improve collaboration with
|
||||
[Merge Request Approvals](https://docs.gitlab.com/ee/user/project/merge_requests/index.html#merge-request-approvals),
|
||||
[Multiple Assignees for Issues](https://docs.gitlab.com/ee/user/project/issues/multiple_assignees_for_issues.html),
|
||||
and [Multiple Issue Boards](https://docs.gitlab.com/ee/user/project/issue_board.html#multiple-issue-boards)
|
||||
- Create formal relationships between issues with [Related Issues](https://docs.gitlab.com/ee/user/project/issues/related_issues.html)
|
||||
and [Multiple Issue Boards](project/issue_board.md#multiple-issue-boards-starter).
|
||||
- Create formal relationships between issues with [Related Issues](https://docs.gitlab.com/ee/user/project/issues/related_issues.html).
|
||||
- Use [Burndown Charts](https://docs.gitlab.com/ee/user/project/milestones/burndown_charts.html) to track progress during a sprint or while working on a new version of their software.
|
||||
- Leverage [Elasticsearch](https://docs.gitlab.com/ee/integration/elasticsearch.html) with [Advanced Global Search](https://docs.gitlab.com/ee/user/search/advanced_global_search.html) and [Advanced Syntax Search](https://docs.gitlab.com/ee/user/search/advanced_search_syntax.html) for faster, more advanced code search across your entire GitLab instance
|
||||
- [Authenticate users with Kerberos](https://docs.gitlab.com/ee/integration/kerberos.html)
|
||||
- Leverage [Elasticsearch](https://docs.gitlab.com/ee/integration/elasticsearch.html) with [Advanced Global Search](https://docs.gitlab.com/ee/user/search/advanced_global_search.html) and [Advanced Syntax Search](https://docs.gitlab.com/ee/user/search/advanced_search_syntax.html) for faster, more advanced code search across your entire GitLab instance.
|
||||
- [Authenticate users with Kerberos](https://docs.gitlab.com/ee/integration/kerberos.html).
|
||||
- [Mirror a repository](https://docs.gitlab.com/ee/workflow/repository_mirroring.html) from elsewhere on your local server.
|
||||
- [Export issues as CSV](https://docs.gitlab.com/ee/user/project/issues/csv_export.html)
|
||||
- View your entire CI/CD pipeline involving more than one project with [Multiple-Project Pipeline Graphs](https://docs.gitlab.com/ee/ci/multi_project_pipeline_graphs.html)
|
||||
- [Lock files](https://docs.gitlab.com/ee/user/project/file_lock.html) to prevent conflicts
|
||||
- View the current health and status of each CI environment running on Kubernetes with [Deploy Boards](https://docs.gitlab.com/ee/user/project/deploy_boards.html)
|
||||
- Leverage continuous delivery method with [Canary Deployments](https://docs.gitlab.com/ee/user/project/canary_deployments.html)
|
||||
- [Export issues as CSV](https://docs.gitlab.com/ee/user/project/issues/csv_export.html).
|
||||
- View your entire CI/CD pipeline involving more than one project with [Multiple-Project Pipelines](https://docs.gitlab.com/ee/ci/multi_project_pipeline_graphs.html).
|
||||
- [Lock files](https://docs.gitlab.com/ee/user/project/file_lock.html) to prevent conflicts.
|
||||
- View the current health and status of each CI environment running on Kubernetes with [Deploy Boards](https://docs.gitlab.com/ee/user/project/deploy_boards.html).
|
||||
- Leverage continuous delivery method with [Canary Deployments](https://docs.gitlab.com/ee/user/project/canary_deployments.html).
|
||||
|
||||
You can also [integrate](project/integrations/project_services.md) GitLab with
|
||||
numerous third-party applications, such as Mattermost, Microsoft Teams, Trello,
|
||||
|
|
|
|||
|
|
@ -17,7 +17,7 @@ When you create a project in GitLab, you'll have access to a large number of
|
|||
|
||||
- [Issue tracker](issues/index.md): Discuss implementations with your team within issues
|
||||
- [Issue Boards](issue_board.md): Organize and prioritize your workflow
|
||||
- [Multiple Issue Boards](https://docs.gitlab.com/ee/user/project/issue_board.html#multiple-issue-boards): Allow your teams to create their own workflows (Issue Boards) for the same project **[STARTER]**
|
||||
- [Multiple Issue Boards](issue_board.md#multiple-issue-boards-starter): Allow your teams to create their own workflows (Issue Boards) for the same project **[STARTER]**
|
||||
- [Repositories](repository/index.md): Host your code in a fully
|
||||
integrated platform
|
||||
- [Branches](repository/branches/index.md): use Git branching strategies to
|
||||
|
|
|
|||
|
|
@ -28,11 +28,11 @@ Issue Boards** (version introduced in GitLab 8.11 - August 2016).
|
|||
### Advanced features of Issue Boards
|
||||
|
||||
With [GitLab Starter](https://about.gitlab.com/pricing/), you can create
|
||||
[multiple issue boards](#multiple-issue-boards) for a given project. **[STARTER]**
|
||||
[multiple issue boards](#multiple-issue-boards-starter) for a given project. **[STARTER]**
|
||||
|
||||
With [GitLab Premium](https://about.gitlab.com/pricing/), you can also create multiple
|
||||
issue boards for your groups, and add lists for [assignees](#assignee-lists) and
|
||||
[milestones](#milestone-lists). **[PREMIUM]**
|
||||
issue boards for your groups, and add lists for [assignees](#assignee-lists-premium) and
|
||||
[milestones](#milestone-lists-premium). **[PREMIUM]**
|
||||
|
||||
Check all the [advanced features of Issue Boards](#gitlab-enterprise-features-for-issue-boards)
|
||||
below.
|
||||
|
|
@ -97,7 +97,7 @@ If we have the labels "**backend**", "**frontend**", "**staging**", and
|
|||
|
||||
### Use cases for Multiple Issue Boards
|
||||
|
||||
With [Multiple Issue Boards](#multiple-issue-boards), available only in
|
||||
With [Multiple Issue Boards](#multiple-issue-boards-starter), available only in
|
||||
[GitLab Enterprise Edition](https://about.gitlab.com/pricing/),
|
||||
each team can have their own board to organize their workflow individually.
|
||||
|
||||
|
|
@ -220,7 +220,7 @@ Click the button at the top right to toggle focus mode on and off. In focus mode
|
|||
|
||||
The top of each list indicates the sum of issue weights for the issues that
|
||||
belong to that list. This is useful when using boards for capacity allocation,
|
||||
especially in combination with [assignee lists](#assignee-lists).
|
||||
especially in combination with [assignee lists](#assignee-lists-premium).
|
||||
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -1,6 +1,6 @@
|
|||
# Confidential issues
|
||||
|
||||
> [Introduced][ce-3282] in GitLab 8.6.
|
||||
> [Introduced](https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/3282) in GitLab 8.6.
|
||||
|
||||
Confidential issues are issues visible only to members of a project with
|
||||
[sufficient permissions](#permissions-and-access-to-confidential-issues).
|
||||
|
|
@ -67,7 +67,7 @@ There is also an indicator on the sidebar denoting confidentiality.
|
|||
|
||||
There are two kinds of level access for confidential issues. The general rule
|
||||
is that confidential issues are visible only to members of a project with at
|
||||
least [Reporter access][permissions]. However, a guest user can also create
|
||||
least [Reporter access](../../permissions.md#project-members-permissions). However, a guest user can also create
|
||||
confidential issues, but can only view the ones that they created themselves.
|
||||
|
||||
Confidential issues are also hidden in search results for unprivileged users.
|
||||
|
|
@ -77,6 +77,3 @@ project's search results respectively.
|
|||
| Maintainer access | Guest access |
|
||||
| :-----------: | :----------: |
|
||||
|  |  |
|
||||
|
||||
[permissions]: ../../permissions.md#project
|
||||
[ce-3282]: https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/3282
|
||||
|
|
|
|||
|
|
@ -48,13 +48,12 @@ issues in merge requests.
|
|||
|
||||
## From Merge Requests
|
||||
|
||||
Mentioning issues in merge request comments work exactly the same way
|
||||
Mentioning issues in merge request comments works exactly the same way as
|
||||
they do for [related issues](#from-related-issues).
|
||||
|
||||
When you mention an issue in a merge request description, you can either
|
||||
[close the issue as soon as the merge request is merged](closing_issues.md#via-merge-request),
|
||||
or simply link both issue and merge request as described in the
|
||||
[closing issues documentation](closing_issues.md#from-related-issues).
|
||||
When you mention an issue in a merge request description, it will simply
|
||||
[link the issue and merge request together](#from-related-issues). Additionally,
|
||||
you can also [set an issue to close as soon as the merge request is merged](closing_issues.md#via-merge-request).
|
||||
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -1,11 +1,11 @@
|
|||
# Due dates
|
||||
|
||||
> [Introduced][ce-3614] in GitLab 8.7.
|
||||
> [Introduced](https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/3614) in GitLab 8.7.
|
||||
|
||||
Please read through the [GitLab Issue Documentation](index.md) for an overview on GitLab Issues.
|
||||
|
||||
Due dates can be used in issues to keep track of deadlines and make sure
|
||||
features are shipped on time. Due dates require at least [Reporter permissions][permissions]
|
||||
features are shipped on time. Due dates require at least [Reporter permissions](../../permissions.md#project-members-permissions)
|
||||
to be able to edit them. On the contrary, they can be seen by everybody.
|
||||
|
||||
## Setting a due date
|
||||
|
|
@ -47,6 +47,3 @@ on the _Subscribe to calendar_ button on the following pages:
|
|||
GitLab header
|
||||
- on the **Project Issues** page
|
||||
- on the **Group Issues** page
|
||||
|
||||
[ce-3614]: https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/3614
|
||||
[permissions]: ../../permissions.md#project
|
||||
|
|
|
|||
|
|
@ -109,7 +109,7 @@ issue within your team only, you can make that
|
|||
[issue confidential](confidential_issues.md). Even if your project
|
||||
is public, that issue will be preserved. The browser will
|
||||
respond with a 404 error whenever someone who is not a project
|
||||
member with at least [Reporter level](../../permissions.md#project) tries to
|
||||
member with at least [Reporter level](../../permissions.md#project-members-permissions) tries to
|
||||
access that issue's URL.
|
||||
|
||||
Learn more about them on the [confidential issues documentation](confidential_issues.md).
|
||||
|
|
@ -140,7 +140,7 @@ Read through the documentation for [Issue Boards](../issue_board.md)
|
|||
to find out more about this feature.
|
||||
|
||||
With [GitLab Starter](https://about.gitlab.com/pricing/), you can also
|
||||
create various boards per project with [Multiple Issue Boards](https://docs.gitlab.com/ee/user/project/issue_board.html#multiple-issue-boards).
|
||||
create various boards per project with [Multiple Issue Boards](../issue_board.html#multiple-issue-boards-starter).
|
||||
|
||||
### Import Issues from CSV
|
||||
|
||||
|
|
|
|||
Loading…
Reference in a new issue