Commit 6e575337 authored by Russell Dickenson's avatar Russell Dickenson

Merge branch 'issue_215364_docs' into 'master'

Update service desk documentation

See merge request gitlab-org/gitlab!37116
parents c5ff07ca 36421310
...@@ -123,7 +123,7 @@ The following documentation relates to the DevOps **Plan** stage: ...@@ -123,7 +123,7 @@ The following documentation relates to the DevOps **Plan** stage:
| [Related Issues](user/project/issues/related_issues.md) **(STARTER)** | Create a relationship between issues. | | [Related Issues](user/project/issues/related_issues.md) **(STARTER)** | Create a relationship between issues. |
| [Requirements Management](user/project/requirements/index.md) **(ULTIMATE)** | Check your products against a set of criteria. | | [Requirements Management](user/project/requirements/index.md) **(ULTIMATE)** | Check your products against a set of criteria. |
| [Roadmap](user/group/roadmap/index.md) **(ULTIMATE)** | Visualize epic timelines. | | [Roadmap](user/group/roadmap/index.md) **(ULTIMATE)** | Visualize epic timelines. |
| [Service Desk](user/project/service_desk.md) **(STARTER)** | A simple way to allow people to create issues in your GitLab instance without needing their own user account. | | [Service Desk](user/project/service_desk.md) | A simple way to allow people to create issues in your GitLab instance without needing their own user account. |
| [Time Tracking](user/project/time_tracking.md) | Track time spent on issues and merge requests. | | [Time Tracking](user/project/time_tracking.md) | Track time spent on issues and merge requests. |
| [Todos](user/todos.md) | Keep track of work requiring attention with a chronological list displayed on a simple dashboard. | | [Todos](user/todos.md) | Keep track of work requiring attention with a chronological list displayed on a simple dashboard. |
......
...@@ -17,7 +17,7 @@ GitLab has several features based on receiving incoming emails: ...@@ -17,7 +17,7 @@ GitLab has several features based on receiving incoming emails:
allow GitLab users to create a new merge request by sending an email to a allow GitLab users to create a new merge request by sending an email to a
user-specific email address. user-specific email address.
- [Service Desk](../user/project/service_desk.md): provide e-mail support to - [Service Desk](../user/project/service_desk.md): provide e-mail support to
your customers through GitLab. **(STARTER)** your customers through GitLab.
## Requirements ## Requirements
......
...@@ -1228,7 +1228,7 @@ PUT /projects/:id ...@@ -1228,7 +1228,7 @@ PUT /projects/:id
| `only_mirror_protected_branches` | boolean | no | **(STARTER)** Only mirror protected branches | | `only_mirror_protected_branches` | boolean | no | **(STARTER)** Only mirror protected branches |
| `mirror_overwrites_diverged_branches` | boolean | no | **(STARTER)** Pull mirror overwrites diverged branches | | `mirror_overwrites_diverged_branches` | boolean | no | **(STARTER)** Pull mirror overwrites diverged branches |
| `packages_enabled` | boolean | no | **(PREMIUM ONLY)** Enable or disable packages repository feature | | `packages_enabled` | boolean | no | **(PREMIUM ONLY)** Enable or disable packages repository feature |
| `service_desk_enabled` | boolean | no | **(PREMIUM ONLY)** Enable or disable service desk feature | | `service_desk_enabled` | boolean | no | Enable or disable service desk feature |
NOTE: **Note:** NOTE: **Note:**
If your HTTP repository is not publicly accessible, If your HTTP repository is not publicly accessible,
......
...@@ -306,7 +306,7 @@ Examples: ...@@ -306,7 +306,7 @@ Examples:
docs: docs:
- doc_title: Service Desk - doc_title: Service Desk
doc_url: 'user/project/service_desk.html' doc_url: 'user/project/service_desk.html'
ee_only: true ee_only: false
# note that the URL above ends in html and, as the # note that the URL above ends in html and, as the
# document is EE-only, the attribute ee_only is set to true. # document is EE-only, the attribute ee_only is set to true.
``` ```
......
...@@ -115,7 +115,7 @@ Examples of valid email keys: ...@@ -115,7 +115,7 @@ Examples of valid email keys:
- `1234567890abcdef1234567890abcdef-unsubscribe` (unsubscribe from a conversation) - `1234567890abcdef1234567890abcdef-unsubscribe` (unsubscribe from a conversation)
- `1234567890abcdef1234567890abcdef` (reply to a conversation) - `1234567890abcdef1234567890abcdef` (reply to a conversation)
Please note that the action `-issue-` is used in GitLab Premium as the handler for the Service Desk feature. Please note that the action `-issue-` is used in GitLab as the handler for the Service Desk feature.
### Legacy format ### Legacy format
...@@ -127,7 +127,7 @@ These are the only valid legacy formats for an email handler: ...@@ -127,7 +127,7 @@ These are the only valid legacy formats for an email handler:
- `namespace` - `namespace`
- `namespace+action` - `namespace+action`
Please note that `path/to/project` is used in GitLab Premium as handler for the Service Desk feature. Please note that `path/to/project` is used in GitLab as the handler for the Service Desk feature.
--- ---
......
...@@ -702,8 +702,8 @@ appear to be associated to any of the services running, since they all appear to ...@@ -702,8 +702,8 @@ appear to be associated to any of the services running, since they all appear to
| `projects_jira_active` | `usage_activity_by_stage` | `plan` | | EE | | | `projects_jira_active` | `usage_activity_by_stage` | `plan` | | EE | |
| `projects_jira_dvcs_server_active` | `usage_activity_by_stage` | `plan` | | EE | | | `projects_jira_dvcs_server_active` | `usage_activity_by_stage` | `plan` | | EE | |
| `projects_jira_dvcs_server_active` | `usage_activity_by_stage` | `plan` | | EE | | | `projects_jira_dvcs_server_active` | `usage_activity_by_stage` | `plan` | | EE | |
| `service_desk_enabled_projects` | `usage_activity_by_stage` | `plan` | | EE | | | `service_desk_enabled_projects` | `usage_activity_by_stage` | `plan` | | CE+EE | |
| `service_desk_issues` | `usage_activity_by_stage` | `plan` | | EE | | | `service_desk_issues` | `usage_activity_by_stage` | `plan` | | CE+EE | |
| `deployments` | `usage_activity_by_stage` | `release` | | CE+EE | Total deployments | | `deployments` | `usage_activity_by_stage` | `release` | | CE+EE | Total deployments |
| `failed_deployments` | `usage_activity_by_stage` | `release` | | CE+EE | Total failed deployments | | `failed_deployments` | `usage_activity_by_stage` | `release` | | CE+EE | Total failed deployments |
| `projects_mirrored_with_pipelines_enabled` | `usage_activity_by_stage` | `release` | | EE | Projects with repository mirroring enabled | | `projects_mirrored_with_pipelines_enabled` | `usage_activity_by_stage` | `release` | | EE | Projects with repository mirroring enabled |
......
...@@ -46,10 +46,10 @@ GitLab is a Git-based platform that integrates a great number of essential tools ...@@ -46,10 +46,10 @@ GitLab is a Git-based platform that integrates a great number of essential tools
- Deploying personal and professional static websites with [GitLab Pages](project/pages/index.md). - Deploying personal and professional static websites with [GitLab Pages](project/pages/index.md).
- Integrating with Docker by using [GitLab Container Registry](packages/container_registry/index.md). - Integrating with Docker by using [GitLab Container Registry](packages/container_registry/index.md).
- Tracking the development lifecycle by using [GitLab Value Stream Analytics](project/cycle_analytics.md). - Tracking the development lifecycle by using [GitLab Value Stream Analytics](project/cycle_analytics.md).
- Provide support with [Service Desk](project/service_desk.md).
With GitLab Enterprise Edition, you can also: With GitLab Enterprise Edition, you can also:
- Provide support with [Service Desk](project/service_desk.md).
- Improve collaboration with: - Improve collaboration with:
- [Merge Request Approvals](project/merge_requests/merge_request_approvals.md). **(STARTER)** - [Merge Request Approvals](project/merge_requests/merge_request_approvals.md). **(STARTER)**
- [Multiple Assignees for Issues](project/issues/multiple_assignees_for_issues.md). **(STARTER)** - [Multiple Assignees for Issues](project/issues/multiple_assignees_for_issues.md). **(STARTER)**
......
...@@ -76,7 +76,7 @@ create issues for the same project. ...@@ -76,7 +76,7 @@ create issues for the same project.
![Create issue from group-level issue tracker](img/create_issue_from_group_level_issue_tracker.png) ![Create issue from group-level issue tracker](img/create_issue_from_group_level_issue_tracker.png)
### New issue via Service Desk **(STARTER)** ### New issue via Service Desk
Enable [Service Desk](../service_desk.md) for your project and offer email support. Enable [Service Desk](../service_desk.md) for your project and offer email support.
By doing so, when your customer sends a new email, a new issue can be created in By doing so, when your customer sends a new email, a new issue can be created in
......
...@@ -4,10 +4,11 @@ group: Certify ...@@ -4,10 +4,11 @@ group: Certify
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/#designated-technical-writers 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/#designated-technical-writers
--- ---
# Service Desk **(STARTER)** # Service Desk
> - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/149) in [GitLab Premium](https://about.gitlab.com/pricing/) 9.1. > - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/149) in [GitLab Premium](https://about.gitlab.com/pricing/) 9.1.
> - [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.
## Overview ## Overview
...@@ -61,10 +62,10 @@ users will only see the thread through email. ...@@ -61,10 +62,10 @@ users will only see the thread through email.
## Configuring Service Desk ## Configuring Service Desk
NOTE: **Note:** NOTE: **Note:**
Service Desk is enabled on GitLab.com. If you're a [Silver subscriber](https://about.gitlab.com/pricing/#gitlab-com), Service Desk is enabled on GitLab.com.
you can skip step 1 below; you only need to enable it per project. You can skip step 1 below; you only need to enable it per project.
If you have the correct access and a Premium license, you have the option to set up Service Desk. If you have project maintainer access you have the option to set up Service Desk.
Follow these steps to do so: Follow these steps to do so:
1. [Set up incoming email](../../administration/incoming_email.md#set-it-up) for the GitLab instance. 1. [Set up incoming email](../../administration/incoming_email.md#set-it-up) for the GitLab instance.
......
...@@ -68,7 +68,7 @@ Some features depend on others: ...@@ -68,7 +68,7 @@ Some features depend on others:
- If you disable the **Issues** option, GitLab also removes the following - If you disable the **Issues** option, GitLab also removes the following
features: features:
- **Issue Boards** - **Issue Boards**
- [**Service Desk**](#service-desk-starter) **(STARTER)** - [**Service Desk**](#service-desk-starter)
NOTE: **Note:** NOTE: **Note:**
When the **Issues** option is disabled, you can still access **Milestones** When the **Issues** option is disabled, you can still access **Milestones**
......
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