Skip to content
Snippets Groups Projects
Commit d5aae486 authored by Marcin Sedlak-Jakubowski's avatar Marcin Sedlak-Jakubowski Committed by Craig Norris
Browse files

Remove Starter and Bronze references 

This commit changes files
parent db52afb7
No related branches found
No related tags found
No related merge requests found
Hide whitespace changes
Inline Side-by-side
Showing
with 142 additions and 137 deletions
doc/api/group_iterations.md
+ 3
− 2
View file @ d5aae486
@@ -4,9 +4,10 @@ group: Project Management
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/#assignments
---
 
# Group iterations API **(STARTER)**
# Group iterations API **(PREMIUM)**
 
> [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/118742) in [GitLab Starter](https://about.gitlab.com/pricing/) 13.5.
> - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/118742) in GitLab 13.5.
> - Moved to GitLab Premium in 13.9.
 
This page describes the group iterations API.
There's a separate [project iterations API](iterations.md) page.
doc/api/group_milestones.md
+ 3
− 2
View file @ d5aae486
@@ -159,9 +159,10 @@ Parameters:
| `id` | integer/string | yes | The ID or [URL-encoded path of the group](README.md#namespaced-path-encoding) owned by the authenticated user |
| `milestone_id` | integer | yes | The ID of a group milestone |
 
## Get all burndown chart events for a single milestone **(STARTER)**
## Get all burndown chart events for a single milestone **(PREMIUM)**
 
> [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/4737) in GitLab 12.1
> - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/4737) in GitLab 12.1
> - Moved to GitLab Premium in 13.9.
 
Get all burndown chart events for a single milestone.
 
doc/api/groups.md
+ 2
− 2
View file @ d5aae486
@@ -670,7 +670,7 @@ Example response:
}
```
 
Users on GitLab [Starter, Bronze, or higher](https://about.gitlab.com/pricing/) also see
Users of [GitLab Premium or higher](https://about.gitlab.com/pricing/) also see
the `shared_runners_minutes_limit` and `extra_shared_runners_minutes_limit` parameters:
 
Additional response parameters:
@@ -685,7 +685,7 @@ Additional response parameters:
}
```
 
Users on GitLab [Premium or higher](https://about.gitlab.com/pricing/) also see
Users of [GitLab Premium or higher](https://about.gitlab.com/pricing/) also see
the `marked_for_deletion_on` attribute:
 
```json
doc/api/issues.md
+ 18
− 18
View file @ d5aae486
@@ -169,7 +169,7 @@ Example response:
]
```
 
Users on GitLab [Starter, Bronze, or higher](https://about.gitlab.com/pricing/) can also see
Users of [GitLab Premium or higher](https://about.gitlab.com/pricing/) can also see
the `weight` parameter:
 
```json
@@ -183,7 +183,7 @@ the `weight` parameter:
]
```
 
Users on GitLab [Ultimate](https://about.gitlab.com/pricing/) can also see
Users of [GitLab Ultimate](https://about.gitlab.com/pricing/) can also see
the `health_status` parameter:
 
```json
@@ -347,7 +347,7 @@ Example response:
]
```
 
Users on GitLab [Starter, Bronze, or higher](https://about.gitlab.com/pricing/) can also see
Users of [GitLab Premium or higher](https://about.gitlab.com/pricing/) can also see
the `weight` parameter:
 
```json
@@ -361,7 +361,7 @@ the `weight` parameter:
]
```
 
Users on GitLab [Ultimate](https://about.gitlab.com/pricing/) can also see
Users of [GitLab Ultimate](https://about.gitlab.com/pricing/) can also see
the `health_status` parameter:
 
```json
@@ -530,7 +530,7 @@ Example response:
]
```
 
Users on GitLab [Starter, Bronze, or higher](https://about.gitlab.com/pricing/) can also see
Users of [GitLab Premium or higher](https://about.gitlab.com/pricing/) can also see
the `weight` parameter:
 
```json
@@ -544,7 +544,7 @@ the `weight` parameter:
]
```
 
Users on GitLab [Ultimate](https://about.gitlab.com/pricing/) can also see
Users of [GitLab Ultimate](https://about.gitlab.com/pricing/) can also see
the `health_status` parameter:
 
```json
@@ -684,7 +684,7 @@ Example response:
}
```
 
Users on GitLab [Starter, Bronze, or higher](https://about.gitlab.com/pricing/) can also see
Users of [GitLab Premium or higher](https://about.gitlab.com/pricing/) can also see
the `weight` parameter:
 
```json
@@ -696,7 +696,7 @@ the `weight` parameter:
}
```
 
Users on GitLab [Ultimate](https://about.gitlab.com/pricing/) can also see
Users of [GitLab Ultimate](https://about.gitlab.com/pricing/) can also see
the `epic` property:
 
```javascript
@@ -833,7 +833,7 @@ Example response:
}
```
 
Users on GitLab [Starter, Bronze, or higher](https://about.gitlab.com/pricing/) can also see
Users of [GitLab Premium or higher](https://about.gitlab.com/pricing/) can also see
the `weight` parameter:
 
```json
@@ -845,7 +845,7 @@ the `weight` parameter:
}
```
 
Users on GitLab [Premium](https://about.gitlab.com/pricing/) can also see
Users of [GitLab Premium](https://about.gitlab.com/pricing/) can also see
the `epic` property:
 
```javascript
@@ -864,7 +864,7 @@ the `epic` property:
}
```
 
Users on GitLab [Ultimate](https://about.gitlab.com/pricing/) can also see the `health_status`
Users of [GitLab Ultimate](https://about.gitlab.com/pricing/) can also see the `health_status`
property:
 
```json
@@ -980,7 +980,7 @@ Example response:
}
```
 
Users on GitLab [Starter, Bronze, or higher](https://about.gitlab.com/pricing/) can also see
Users of [GitLab Premium or higher](https://about.gitlab.com/pricing/) can also see
the `weight` parameter:
 
```json
@@ -992,7 +992,7 @@ the `weight` parameter:
}
```
 
Users on GitLab [Ultimate](https://about.gitlab.com/pricing/) can also see
Users of [GitLab Ultimate](https://about.gitlab.com/pricing/) can also see
the `health_status` parameter:
 
```json
@@ -1133,7 +1133,7 @@ Example response:
}
```
 
Users on GitLab [Starter, Bronze, or higher](https://about.gitlab.com/pricing/) can also see
Users of [GitLab Premium or higher](https://about.gitlab.com/pricing/) can also see
the `weight` parameter:
 
```json
@@ -1145,7 +1145,7 @@ the `weight` parameter:
}
```
 
Users on GitLab [Ultimate](https://about.gitlab.com/pricing/) can also see
Users of [GitLab Ultimate](https://about.gitlab.com/pricing/) can also see
the `health_status` parameter:
 
```json
@@ -1298,7 +1298,7 @@ Example response:
}
```
 
Users on GitLab [Starter, Bronze, or higher](https://about.gitlab.com/pricing/) can also see
Users of [GitLab Premium or higher](https://about.gitlab.com/pricing/) can also see
the `weight` parameter:
 
```json
@@ -1310,7 +1310,7 @@ the `weight` parameter:
}
```
 
Users on GitLab [Ultimate](https://about.gitlab.com/pricing/) can also see
Users of [GitLab Ultimate](https://about.gitlab.com/pricing/) can also see
the `health_status` parameter:
 
```json
@@ -1421,7 +1421,7 @@ Example response:
}
```
 
Users on GitLab [Starter, Bronze, or higher](https://about.gitlab.com/pricing/) can also see
Users of [GitLab Premium or higher](https://about.gitlab.com/pricing/) can also see
the `weight` parameter:
 
```json
doc/api/iterations.md
+ 3
− 2
View file @ d5aae486
@@ -4,9 +4,10 @@ group: Project Management
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/#assignments
---
 
# Project iterations API **(STARTER)**
# Project iterations API **(PREMIUM)**
 
> [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/118742) in [GitLab Starter](https://about.gitlab.com/pricing/) 13.5.
> - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/118742) in GitLab 13.5.
> - Moved to GitLab Premium in 13.9.
 
This page describes the project iterations API.
There's a separate [group iterations API](group_iterations.md) page.
doc/api/merge_requests.md
+ 1
− 1
View file @ d5aae486
@@ -1183,7 +1183,7 @@ POST /projects/:id/merge_requests
}
```
 
Users on GitLab [Starter, Bronze, or higher](https://about.gitlab.com/pricing/) also see
Users of [GitLab Premium or higher](https://about.gitlab.com/pricing/) also see
the `approvals_before_merge` parameter:
 
```json
doc/api/milestones.md
+ 3
− 2
View file @ d5aae486
@@ -159,9 +159,10 @@ Parameters:
- `id` (required) - The ID or [URL-encoded path of the project](README.md#namespaced-path-encoding) owned by the authenticated user
- `milestone_id` (required) - The ID of a project milestone
 
## Get all burndown chart events for a single milestone **(STARTER)**
## Get all burndown chart events for a single milestone **(PREMIUM)**
 
> [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/4737) in GitLab 12.1
> - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/4737) in GitLab 12.1
> - Moved to GitLab Premium in 13.9.
 
Gets all burndown chart events for a single milestone.
 
doc/api/projects.md
+ 27
− 28
View file @ d5aae486
@@ -298,11 +298,11 @@ When the user is authenticated and `simple` is not set this returns something li
```
 
NOTE:
For users of GitLab [Premium or higher](https://about.gitlab.com/pricing/),
For users of [GitLab Premium or higher](https://about.gitlab.com/pricing/),
the `marked_for_deletion_at` attribute has been deprecated, and is removed
in API v5 in favor of the `marked_for_deletion_on` attribute.
 
Users of GitLab [Starter, Bronze, or higher](https://about.gitlab.com/pricing/)
Users of [GitLab Premium or higher](https://about.gitlab.com/pricing/)
can also see the `approvals_before_merge` parameter:
 
```json
@@ -933,7 +933,7 @@ GET /projects/:id
}
```
 
Users on GitLab [Starter, Bronze, or higher](https://about.gitlab.com/pricing/)
Users of [GitLab Premium or higher](https://about.gitlab.com/pricing/)
can also see the `approvals_before_merge` parameter:
 
```json
@@ -1053,7 +1053,7 @@ POST /projects
|-------------------------------------------------------------|---------|------------------------|-------------|
| `allow_merge_on_skipped_pipeline` | boolean | **{dotted-circle}** No | Set whether or not merge requests can be merged with skipped jobs. |
| `analytics_access_level` | string | no | One of `disabled`, `private` or `enabled` |
| `approvals_before_merge` **(STARTER)** | integer | **{dotted-circle}** No | How many approvers should approve merge requests by default. |
| `approvals_before_merge` **(PREMIUM)** | integer | **{dotted-circle}** No | How many approvers should approve merge requests by default. |
| `auto_cancel_pending_pipelines` | string | **{dotted-circle}** No | Auto-cancel pending pipelines. This isn't a boolean, but enabled/disabled. |
| `auto_devops_deploy_strategy` | string | **{dotted-circle}** No | Auto Deploy strategy (`continuous`, `manual` or `timed_incremental`). |
| `auto_devops_enabled` | boolean | **{dotted-circle}** No | Enable Auto DevOps for this project. |
@@ -1081,8 +1081,8 @@ POST /projects
| `merge_method` | string | **{dotted-circle}** No | Set the [merge method](#project-merge-method) used. |
| `merge_requests_access_level` | string | **{dotted-circle}** No | One of `disabled`, `private`, or `enabled`. |
| `merge_requests_enabled` | boolean | **{dotted-circle}** No | _(Deprecated)_ Enable merge requests for this project. Use `merge_requests_access_level` instead. |
| `mirror_trigger_builds` **(STARTER)** | boolean | **{dotted-circle}** No | Pull mirroring triggers builds. |
| `mirror` **(STARTER)** | boolean | **{dotted-circle}** No | Enables pull mirroring in a project. |
| `mirror_trigger_builds` **(PREMIUM)** | boolean | **{dotted-circle}** No | Pull mirroring triggers builds. |
| `mirror` **(PREMIUM)** | boolean | **{dotted-circle}** No | Enables pull mirroring in a project. |
| `name` | string | **{check-circle}** Yes (if path isn't provided) | The name of the new project. Equals path if not provided. |
| `namespace_id` | integer | **{dotted-circle}** No | Namespace for the new project (defaults to the current user's namespace). |
| `operations_access_level` | string | **{dotted-circle}** No | One of `disabled`, `private`, or `enabled`. |
@@ -1127,7 +1127,7 @@ POST /projects/user/:user_id
|-------------------------------------------------------------|---------|------------------------|-------------|
| `allow_merge_on_skipped_pipeline` | boolean | **{dotted-circle}** No | Set whether or not merge requests can be merged with skipped jobs. |
| `analytics_access_level` | string | no | One of `disabled`, `private` or `enabled` |
| `approvals_before_merge` **(STARTER)** | integer | **{dotted-circle}** No | How many approvers should approve merge requests by default. |
| `approvals_before_merge` **(PREMIUM)** | integer | **{dotted-circle}** No | How many approvers should approve merge requests by default. |
| `auto_cancel_pending_pipelines` | string | **{dotted-circle}** No | Auto-cancel pending pipelines. This isn't a boolean, but enabled/disabled. |
| `auto_devops_deploy_strategy` | string | **{dotted-circle}** No | Auto Deploy strategy (`continuous`, `manual` or `timed_incremental`). |
| `auto_devops_enabled` | boolean | **{dotted-circle}** No | Enable Auto DevOps for this project. |
@@ -1153,8 +1153,8 @@ POST /projects/user/:user_id
| `merge_method` | string | **{dotted-circle}** No | Set the [merge method](#project-merge-method) used. |
| `merge_requests_access_level` | string | **{dotted-circle}** No | One of `disabled`, `private`, or `enabled`. |
| `merge_requests_enabled` | boolean | **{dotted-circle}** No | _(Deprecated)_ Enable merge requests for this project. Use `merge_requests_access_level` instead. |
| `mirror_trigger_builds` **(STARTER)** | boolean | **{dotted-circle}** No | Pull mirroring triggers builds. |
| `mirror` **(STARTER)** | boolean | **{dotted-circle}** No | Enables pull mirroring in a project. |
| `mirror_trigger_builds` **(PREMIUM)** | boolean | **{dotted-circle}** No | Pull mirroring triggers builds. |
| `mirror` **(PREMIUM)** | boolean | **{dotted-circle}** No | Enables pull mirroring in a project. |
| `name` | string | **{check-circle}** Yes | The name of the new project. |
| `namespace_id` | integer | **{dotted-circle}** No | Namespace for the new project (defaults to the current user's namespace). |
| `operations_access_level` | string | **{dotted-circle}** No | One of `disabled`, `private`, or `enabled`. |
@@ -1200,7 +1200,7 @@ PUT /projects/:id
|-------------------------------------------------------------|----------------|------------------------|-------------|
| `allow_merge_on_skipped_pipeline` | boolean | **{dotted-circle}** No | Set whether or not merge requests can be merged with skipped jobs. |
| `analytics_access_level` | string | no | One of `disabled`, `private` or `enabled` |
| `approvals_before_merge` **(STARTER)** | integer | **{dotted-circle}** No | How many approvers should approve merge request by default. |
| `approvals_before_merge` **(PREMIUM)** | integer | **{dotted-circle}** No | How many approvers should approve merge request by default. |
| `auto_cancel_pending_pipelines` | string | **{dotted-circle}** No | Auto-cancel pending pipelines. This isn't a boolean, but enabled/disabled. |
| `auto_devops_deploy_strategy` | string | **{dotted-circle}** No | Auto Deploy strategy (`continuous`, `manual`, or `timed_incremental`). |
| `auto_devops_enabled` | boolean | **{dotted-circle}** No | Enable Auto DevOps for this project. |
@@ -1229,15 +1229,15 @@ PUT /projects/:id
| `merge_method` | string | **{dotted-circle}** No | Set the [merge method](#project-merge-method) used. |
| `merge_requests_access_level` | string | **{dotted-circle}** No | One of `disabled`, `private`, or `enabled`. |
| `merge_requests_enabled` | boolean | **{dotted-circle}** No | _(Deprecated)_ Enable merge requests for this project. Use `merge_requests_access_level` instead. |
| `mirror_overwrites_diverged_branches` **(STARTER)** | boolean | **{dotted-circle}** No | Pull mirror overwrites diverged branches. |
| `mirror_trigger_builds` **(STARTER)** | boolean | **{dotted-circle}** No | Pull mirroring triggers builds. |
| `mirror_user_id` **(STARTER)** | integer | **{dotted-circle}** No | User responsible for all the activity surrounding a pull mirror event. _(admins only)_ |
| `mirror` **(STARTER)** | boolean | **{dotted-circle}** No | Enables pull mirroring in a project. |
| `mirror_overwrites_diverged_branches` **(PREMIUM)** | boolean | **{dotted-circle}** No | Pull mirror overwrites diverged branches. |
| `mirror_trigger_builds` **(PREMIUM)** | boolean | **{dotted-circle}** No | Pull mirroring triggers builds. |
| `mirror_user_id` **(PREMIUM)** | integer | **{dotted-circle}** No | User responsible for all the activity surrounding a pull mirror event. _(admins only)_ |
| `mirror` **(PREMIUM)** | boolean | **{dotted-circle}** No | Enables pull mirroring in a project. |
| `name` | string | **{dotted-circle}** No | The name of the project. |
| `operations_access_level` | string | **{dotted-circle}** No | One of `disabled`, `private`, or `enabled`. |
| `only_allow_merge_if_all_discussions_are_resolved` | boolean | **{dotted-circle}** No | Set whether merge requests can only be merged when all the discussions are resolved. |
| `only_allow_merge_if_pipeline_succeeds` | boolean | **{dotted-circle}** No | Set whether merge requests can only be merged with successful jobs. |
| `only_mirror_protected_branches` **(STARTER)** | boolean | **{dotted-circle}** No | Only mirror protected branches. |
| `only_mirror_protected_branches` **(PREMIUM)** | boolean | **{dotted-circle}** No | Only mirror protected branches. |
| `packages_enabled` | boolean | **{dotted-circle}** No | Enable or disable packages repository feature. |
| `pages_access_level` | string | **{dotted-circle}** No | One of `disabled`, `private`, `enabled`, or `public`. |
| `requirements_access_level` | string | **{dotted-circle}** No | One of `disabled`, `private`, `enabled` or `public` |
@@ -1877,7 +1877,7 @@ This endpoint:
- Deletes a project including all associated resources (including issues and
merge requests).
- From [GitLab 13.2](https://gitlab.com/gitlab-org/gitlab/-/issues/220382) on
[Premium](https://about.gitlab.com/pricing/) or higher tiers, group
[Premium or higher](https://about.gitlab.com/pricing/) tiers, group
admins can [configure](../user/group/index.md#enabling-delayed-project-removal)
projects within a group to be deleted after a delayed period. When enabled,
actual deletion happens after the number of days specified in the
@@ -2187,8 +2187,6 @@ curl --header "PRIVATE-TOKEN: <your_access_token>" "https://gitlab.example.com/a
 
## Start the Housekeeping task for a project
 
> Introduced in GitLab 9.0.
```plaintext
POST /projects/:id/housekeeping
```
@@ -2197,9 +2195,9 @@ POST /projects/:id/housekeeping
|-----------|----------------|------------------------|-------------|
| `id` | integer/string | **{check-circle}** Yes | The ID of the project or NAMESPACE/PROJECT_NAME. |
 
## Push Rules **(STARTER)**
## Push Rules **(PREMIUM)**
 
### Get project push rules **(STARTER)**
### Get project push rules **(PREMIUM)**
 
Get the [push rules](../push_rules/push_rules.md#enabling-push-rules) of a
project.
@@ -2231,7 +2229,7 @@ GET /projects/:id/push_rule
}
```
 
Users of GitLab [Premium or higher](https://about.gitlab.com/pricing/)
Users of [GitLab Premium or higher](https://about.gitlab.com/pricing/)
can also see the `commit_committer_check` and `reject_unsigned_commits`
parameters:
 
@@ -2245,7 +2243,7 @@ parameters:
}
```
 
### Add project push rule **(STARTER)**
### Add project push rule **(PREMIUM)**
 
Adds a push rule to a specified project.
 
@@ -2268,7 +2266,7 @@ POST /projects/:id/push_rule
| `prevent_secrets` | boolean | **{dotted-circle}** No | GitLab rejects any files that are likely to contain secrets. |
| `reject_unsigned_commits` **(PREMIUM)** | boolean | **{dotted-circle}** No | Reject commit when it's not signed through GPG. |
 
### Edit project push rule **(STARTER)**
### Edit project push rule **(PREMIUM)**
 
Edits a push rule for a specified project.
 
@@ -2293,7 +2291,7 @@ PUT /projects/:id/push_rule
 
### Delete project push rule
 
> Introduced in [GitLab Starter](https://about.gitlab.com/pricing/) 9.0.
> - Moved to GitLab Premium in 13.9.
 
Removes a push rule from a project. This is an idempotent method and can be
called multiple times. Either the push rule is available or not.
@@ -2440,9 +2438,10 @@ Read more in the [Project import/export](project_import_export.md) documentation
 
Read more in the [Project members](members.md) documentation.
 
## Configure pull mirroring for a project **(STARTER)**
## Configure pull mirroring for a project **(PREMIUM)**
 
> Introduced in [GitLab Starter](https://about.gitlab.com/pricing/) 11.2.
> - Introduced in GitLab 11.
> - Moved to GitLab Premium in 13.9.
 
Configure pull mirroring while [creating a new project](#create-project) or [updating an existing project](#edit-project) using the API if the remote repository is publicly accessible or via `username/password` authentication. In case your HTTP repository is not publicly accessible, you can add the authentication information to the URL: `https://username:password@gitlab.company.com/group/project.git`, where password is a [personal access token](../user/profile/personal_access_tokens.md) with the API scope enabled.
 
@@ -2452,9 +2451,9 @@ The relevant API parameters to update are:
- `mirror`: Enables pull mirroring on project when set to `true`.
- `only_mirror_protected_branches`: Set to `true` for protected branches.
 
## Start the pull mirroring process for a Project **(STARTER)**
## Start the pull mirroring process for a Project **(PREMIUM)**
 
> Introduced in [GitLab Starter](https://about.gitlab.com/pricing/) 10.3.
> - Moved to GitLab Premium in 13.9.
 
```plaintext
POST /projects/:id/mirror/pull
doc/api/resource_iteration_events.md
+ 4
− 3
View file @ d5aae486
@@ -4,10 +4,11 @@ group: Project Management
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/#assignments
---
 
# Resource iteration events API **(STARTER)**
# Resource iteration events API **(PREMIUM)**
 
> - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/229463) in [GitLab Starter](https://about.gitlab.com/pricing/) 13.4.
> - [Feature flag removed](https://gitlab.com/gitlab-org/gitlab/-/issues/229463) in [GitLab Starter](https://about.gitlab.com/pricing/) 13.5.
> - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/229463) in GitLab 13.4.
> - [Feature flag removed](https://gitlab.com/gitlab-org/gitlab/-/issues/229463) in GitLab 13.5.
> - Moved to GitLab Premium in 13.9.
 
Resource iteration events keep track of what happens to GitLab [issues](../user/project/issues/).
 
doc/api/users.md
+ 4
− 4
View file @ d5aae486
---
stage: none
group: unassigned
stage: Manage
group: Access
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/#assignments
---
 
@@ -171,7 +171,7 @@ GET /users
]
```
 
Users on GitLab [Starter, Bronze, or higher](https://about.gitlab.com/pricing/) also see the `shared_runners_minutes_limit`, `extra_shared_runners_minutes_limit`, and `using_license_seat` parameters.
Users on GitLab [Premium or higher](https://about.gitlab.com/pricing/) also see the `shared_runners_minutes_limit`, `extra_shared_runners_minutes_limit`, and `using_license_seat` parameters.
 
```json
[
@@ -340,7 +340,7 @@ Example Responses:
NOTE:
The `plan` and `trial` parameters are only available on GitLab Enterprise Edition.
 
Users on GitLab [Starter, Bronze, or higher](https://about.gitlab.com/pricing/) also see
Users on GitLab [Premium or higher](https://about.gitlab.com/pricing/) also see
the `shared_runners_minutes_limit`, and `extra_shared_runners_minutes_limit` parameters.
 
```json
doc/user/group/iterations/index.md
+ 10
− 9
View file @ d5aae486
@@ -5,15 +5,16 @@ group: Project Management
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/#assignments
---
 
# Iterations **(STARTER)**
# Iterations **(PREMIUM)**
 
> - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/214713) in [GitLab Starter](https://about.gitlab.com/pricing/) 13.1.
> - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/214713) in GitLab 13.1.
> - It was deployed behind a feature flag, disabled by default.
> - [Became enabled by default](https://gitlab.com/gitlab-org/gitlab/-/issues/221047) on GitLab 13.2.
> - It's enabled on GitLab.com.
> - It's able to be enabled or disabled per-group.
> - It's recommended for production use.
> - For GitLab self-managed instances, GitLab administrators can opt to [disable it](#disable-iterations). **(STARTER ONLY)**
> - For GitLab self-managed instances, GitLab administrators can opt to [disable it](#disable-iterations). **(PREMIUM ONLY)**
> - Moved to GitLab Premium in 13.9.
 
Iterations are a way to track issues over a period of time. This allows teams
to track velocity and volatility metrics. Iterations can be used with [milestones](../../project/milestones/index.md)
@@ -50,7 +51,7 @@ To create an iteration:
 
## Edit an iteration
 
> [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/218277) in [GitLab Starter](https://about.gitlab.com/pricing/) 13.2.
> [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/218277) in GitLab 13.2.
 
NOTE:
You need Developer [permissions](../../permissions.md) or higher to edit an iteration.
@@ -59,14 +60,14 @@ To edit an iteration, click the three-dot menu (**{ellipsis_v}**) > **Edit itera
 
## Add an issue to an iteration
 
> [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/216158) in [GitLab Starter](https://about.gitlab.com/pricing/) 13.2.
> [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/216158) in GitLab 13.2.
 
To learn how to add an issue to an iteration, see the steps in
[Managing issues](../../project/issues/managing_issues.md#add-an-issue-to-an-iteration).
 
## View an iteration report
 
> Viewing iteration reports in projects [introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/222763) in [GitLab Starter](https://about.gitlab.com/pricing/) 13.5.
> Viewing iteration reports in projects [introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/222763) in GitLab 13.5.
 
You can track the progress of an iteration by reviewing iteration reports.
An iteration report displays a list of all the issues assigned to an iteration and their status.
@@ -79,8 +80,8 @@ To view an iteration report, go to the iterations list page and click an iterati
 
### Iteration burndown and burnup charts
 
> - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/222750) in [GitLab Starter](https://about.gitlab.com/pricing/) 13.5.
> - [Feature flag removed](https://gitlab.com/gitlab-org/gitlab/-/issues/269972) in [GitLab Starter](https://about.gitlab.com/pricing/) 13.7.
> - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/222750) in GitLab 13.5.
> - [Feature flag removed](https://gitlab.com/gitlab-org/gitlab/-/issues/269972) in GitLab 13.7.
 
The iteration report includes [burndown and burnup charts](../../project/milestones/burndown_and_burnup_charts.md),
similar to how they appear when viewing a [milestone](../../project/milestones/index.md).
@@ -104,7 +105,7 @@ To group issues by label:
You can also search for labels by typing in the search input.
1. Click or tap outside of the label dropdown. The page is now grouped by the selected labels.
 
## Disable iterations **(STARTER ONLY)**
## Disable iterations **(PREMIUM SELF)**
 
GitLab Iterations feature is deployed with a feature flag that is **enabled by default**.
[GitLab administrators with access to the GitLab Rails console](../../../administration/feature_flags.md)
doc/user/project/description_templates.md
+ 2
− 5
View file @ d5aae486
@@ -6,8 +6,6 @@ info: To determine the technical writer assigned to the Stage/Group associated w
 
# Description templates
 
> [Introduced](https://gitlab.com/gitlab-org/gitlab-foss/-/merge_requests/4981) in GitLab 8.11.
We all know that a properly submitted issue is more likely to be addressed in
a timely manner by the developers of a project.
 
@@ -87,10 +85,9 @@ For example: `https://gitlab.com/gitlab-org/gitlab/-/issues/new?issuable_templat
 
![Description templates](img/description_templates.png)
 
## Setting a default template for merge requests and issues **(STARTER)**
## Setting a default template for merge requests and issues **(PREMIUM)**
 
> - Templates for merge requests [introduced](https://gitlab.com/gitlab-org/gitlab/commit/7478ece8b48e80782b5465b96c79f85cc91d391b) in GitLab 6.9.
> - Templates for issues [introduced](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/28) in GitLab 8.1.
> - Moved to GitLab Premium in 13.9.
 
The visibility of issues or merge requests should be set to either "Everyone
with access" or "Only Project Members" in your project's **Settings / Visibility, project features, permissions** section, otherwise the
doc/user/project/issue_board.md
+ 13
− 17
View file @ d5aae486
@@ -6,8 +6,6 @@ info: To determine the technical writer assigned to the Stage/Group associated w
 
# Issue Boards **(FREE)**
 
> [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).
The GitLab Issue Board is a software project management tool used to plan,
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
@@ -52,9 +50,8 @@ the Issue Board feature.
 
## Multiple issue boards
 
> - [Introduced](https://about.gitlab.com/releases/2016/10/22/gitlab-8-13-released/) in GitLab 8.13.
> - Multiple issue boards per project [moved](https://gitlab.com/gitlab-org/gitlab-foss/-/issues/53811) to [GitLab Free](https://about.gitlab.com/pricing/) in GitLab 12.1.
> - Multiple issue boards per group are available in [GitLab Premium](https://about.gitlab.com/pricing/).
> - Multiple issue boards per project [moved](https://gitlab.com/gitlab-org/gitlab-foss/-/issues/53811) to GitLab Free in 12.1.
> - Multiple issue boards per group are available in GitLab Premium.
 
Multiple issue boards allow for more than one issue board for a given project **(FREE)** or group **(PREMIUM)**.
This is great for large projects with more than one team or when a repository hosts the code of multiple products.
@@ -230,10 +227,10 @@ and vice versa.
GitLab issue boards are available on the GitLab Free tier, but some
advanced functionality is present in [higher tiers only](https://about.gitlab.com/pricing/).
 
### Configurable issue boards **(STARTER)**
### Configurable issue boards **(PREMIUM)**
 
> - [Introduced](https://about.gitlab.com/releases/2017/11/22/gitlab-10-2-released/#issue-boards-configuration) in GitLab 10.2.
> - Setting current iteration as scope [introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/196804) in GitLab 13.8.
> - Moved to GitLab Premium in 13.9.
 
An issue board can be associated with a [milestone](milestones/index.md#milestones),
[labels](labels.md), assignee, weight, and current [iteration](../group/iterations/index.md),
@@ -256,14 +253,15 @@ the Configurable Issue Board feature.
 
### Focus mode
 
> - [Introduced]((https://about.gitlab.com/releases/2017/04/22/gitlab-9-1-released/#issue-boards-focus-mode-ees-eep)) in [GitLab Starter](https://about.gitlab.com/pricing/) 9.1.
> - [Moved](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/28597) to the Free tier of GitLab SaaS in 12.10.
> - [Moved](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/28597) to GitLab Free SaaS in 12.10.
> - [Moved](https://gitlab.com/gitlab-org/gitlab/-/issues/212331) to GitLab Free self-managed in 13.0.
 
To enable or disable focus mode, select the **Toggle focus mode** button (**{maximize}**) at the top
right. In focus mode, the navigation UI is hidden, allowing you to focus on issues in the board.
 
### Sum of issue weights **(STARTER)**
### Sum of issue weights **(PREMIUM)**
> Moved to GitLab Premium in 13.9.
 
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,
@@ -273,9 +271,6 @@ especially in combination with [assignee lists](#assignee-lists).
 
### Group issue boards **(PREMIUM)**
 
> - One group issue board per group introduced in GitLab 10.6.
> - Multiple group issue boards [introduced](https://about.gitlab.com/releases/2017/09/22/gitlab-10-0-released/#group-issue-boards) in [GitLab Premium](https://about.gitlab.com/pricing/) 10.0.
Accessible at the group navigation level, a group issue board offers the same features as a project-level board.
It can display issues from all projects in that
group and its descendant subgroups. Similarly, you can only filter by group labels for these
@@ -359,9 +354,10 @@ You can also [drag issues](#drag-issues-between-lists) to change their position
 
![Drag issues between swimlanes](img/epics_swimlanes_drag_and_drop.png)
 
## Work In Progress limits **(STARTER)**
## Work In Progress limits **(PREMIUM)**
 
> [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/11403) in GitLab 12.7
> - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/11403) in GitLab 12.7
> - Moved to GitLab Premium in 13.9.
 
You can set a Work In Progress (WIP) limit for each issue list on an issue board. When a limit is
set, the list's header shows the number of issues in the list and the soft limit of issues.
@@ -546,8 +542,8 @@ to another list, the label changes and a system note is recorded.
 
When dragging issues between lists, different behavior occurs depending on the source list and the target list.
 
| | To Open | To Closed | To label `B` list | To assignee `Bob` list |
|----------------------------|--------------------|--------------|------------------------------|---------------------------------------|
| | To Open | To Closed | To label `B` list | To assignee `Bob` list |
| ------------------------------ | ------------------ | ------------ | ---------------------------- | ------------------------------------- |
| **From Open** | - | Issue closed | `B` added | `Bob` assigned |
| **From Closed** | Issue reopened | - | Issue reopened<br/>`B` added | Issue reopened<br/>`Bob` assigned |
| **From label `A` list** | `A` removed | Issue closed | `A` removed<br/>`B` added | `Bob` assigned |
doc/user/project/issues/issue_data_and_actions.md
+ 8
− 7
View file @ d5aae486
@@ -23,13 +23,13 @@ The numbers in the image correspond to the following features:
- **1.** [Issue actions](#issue-actions)
- **2.** [To Do](#to-do)
- **3.** [Assignee](#assignee)
- **3.1.** [Multiple Assignees **(STARTER)**](#multiple-assignees)
- **4.** [Epic **(PREMIUM)**](#epic)
- **3.1.** [Multiple Assignees](#multiple-assignees)
- **4.** [Epic](#epic)
- **5.** [Milestone](#milestone)
- **6.** [Time tracking](#time-tracking)
- **7.** [Due date](#due-date)
- **8.** [Labels](#labels)
- **9.** [Weight **(STARTER)**](#weight)
- **9.** [Weight](#weight)
- **10.** [Confidentiality](#confidentiality)
- **11.** [Lock issue](#lock-issue)
- **12.** [Participants](#participants)
@@ -86,7 +86,7 @@ An issue can be assigned to:
 
- Yourself.
- Another person.
- [Many people](#multiple-assignees). **(STARTER)**
- [Many people](#multiple-assignees). **(PREMIUM)**
 
The assignees can be changed as often as needed. The idea is that the assignees are
responsible for that issue until it's reassigned to someone else to take it from there.
@@ -96,7 +96,7 @@ NOTE:
If a user is not member of that project, it can only be
assigned to them if they created the issue themselves.
 
#### Multiple Assignees **(STARTER)**
#### Multiple Assignees **(PREMIUM)**
 
Often, multiple people work on the same issue together. This can be difficult
to track in large teams where there is shared ownership of an issue.
@@ -138,7 +138,7 @@ available to all projects in the group.
If a label doesn't exist yet, you can create one by clicking **Edit**
followed by **Create new label** in the dropdown menu.
 
### Weight **(STARTER)**
### Weight **(PREMIUM)**
 
[Assign a weight](issue_weight.md) to an issue.
Larger values are used to indicate more effort is required to complete the issue. Only
@@ -194,7 +194,8 @@ The plain text title and description of the issue fill the top center of the iss
The description fully supports [GitLab Flavored Markdown](../../markdown.md#gitlab-flavored-markdown-gfm),
allowing many formatting options.
 
> [In GitLab 12.6](https://gitlab.com/gitlab-org/gitlab/-/issues/10103) and later, changes to an issue's description are listed in the [issue history](#issue-history). **(STARTER)**
[In GitLab 12.6](https://gitlab.com/gitlab-org/gitlab/-/issues/10103) and later, changes to an
issue's description are listed in the [issue history](#issue-history). **(PREMIUM)**
 
### Mentions
 
doc/user/project/issues/issue_weight.md
+ 3
− 3
View file @ d5aae486
@@ -5,15 +5,15 @@ group: Project Management
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/#assignments
---
 
# Issue weight **(STARTER)**
# Issue weight **(PREMIUM)**
 
> [Introduced](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/76) in [GitLab Starter](https://about.gitlab.com/pricing/) 8.3.
> - Moved to GitLab Premium in 13.9.
 
When you have a lot of issues, it can be hard to get an overview.
By adding a weight to each issue, you can get a better idea of how much time,
value or complexity a given issue has or costs.
 
You can set the weight of an issue during its creation, by simply changing the
You can set the weight of an issue during its creation, by changing the
value in the dropdown menu. You can set it to a non-negative integer
value from 0, 1, 2, and so on. (The database stores a 4-byte value, so the
upper bound is essentially limitless).
doc/user/project/issues/managing_issues.md
+ 6
− 5
View file @ d5aae486
@@ -287,9 +287,9 @@ editing it and clicking on the delete button.
 
## Promote an issue to an epic **(PREMIUM)**
 
> - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/3777) in [GitLab Ultimate](https://about.gitlab.com/pricing/) 11.6.
> - [Moved](https://gitlab.com/gitlab-org/gitlab/-/issues/37081) to [GitLab Premium](https://about.gitlab.com/pricing/) in 12.8.
> - Promoting issues to epics via the UI [introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/233974) in [GitLab Premium](https://about.gitlab.com/pricing/) 13.6.
> - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/3777) in GitLab Ultimate 11.6.
> - Moved to GitLab Premium in 12.8.
> - Promoting issues to epics via the UI [introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/233974) in GitLab Premium 13.6.
 
You can promote an issue to an epic in the immediate parent group.
 
@@ -302,9 +302,10 @@ Alternatively, you can use the `/promote` [quick action](../quick_actions.md#qui
 
Read more about promoting an issue to an epic on the [Manage epics page](../../group/epics/manage_epics.md#promote-an-issue-to-an-epic).
 
## Add an issue to an iteration **(STARTER)**
## Add an issue to an iteration **(PREMIUM)**
 
> [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/216158) in [GitLab Starter](https://about.gitlab.com/pricing/) 13.2.
> - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/216158) in GitLab 13.2.
> - Moved to GitLab Premium in 13.9.
 
To add an issue to an [iteration](../../group/iterations/index.md):
 
doc/user/project/issues/multiple_assignees_for_issues.md
+ 3
− 3
View file @ d5aae486
@@ -4,9 +4,9 @@ group: Project Management
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/#assignments
---
 
# Multiple Assignees for Issues **(STARTER)**
# Multiple Assignees for Issues **(PREMIUM)**
 
> [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).
> - Moved to GitLab Premium in 13.9.
 
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
@@ -40,4 +40,4 @@ to assign the issue to.
 
![adding multiple assignees](img/multiple_assignees.gif)
 
An assignee can be easily removed by deselecting them from the same dropdown menu.
To remove an assignee, deselect them from the same dropdown menu.
doc/user/project/milestones/burndown_and_burnup_charts.md
+ 9
− 9
View file @ d5aae486
@@ -5,18 +5,17 @@ group: Project Management
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/#assignments
---
 
# Burndown and burnup charts **(STARTER)**
# Burndown and burnup charts **(PREMIUM)**
 
[Burndown](#burndown-charts) and [burnup](#burnup-charts) charts show the progress of completing a milestone.
 
![burndown and burnup chart](img/burndown_and_burnup_charts_v13_6.png)
 
## Burndown charts
## Burndown charts **(PREMIUM)**
 
> - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/1540) in [GitLab Starter](https://about.gitlab.com/pricing/) 9.1 for project milestones.
> - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/5354) in [GitLab Premium](https://about.gitlab.com/pricing/) 10.8 for group milestones.
> - [Added](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/6495) to [GitLab Starter](https://about.gitlab.com/pricing/) 11.2 for group milestones.
> - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/6903) [fixed burndown charts](#fixed-burndown-charts) in [GitLab Starter](https://about.gitlab.com/pricing/) 13.6.
> - [Added](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/6495) to GitLab 11.2 for group milestones.
> - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/6903) [fixed burndown charts](#fixed-burndown-charts) in GitLab 13.6.
> - Moved to GitLab Premium in 13.9.
 
Burndown charts show the number of issues over the course of a milestone.
 
@@ -101,10 +100,11 @@ Therefore, when the milestone start date is changed, the number of opened issues
change.
Reopened issues are considered as having been opened on the day after they were last closed.
 
## Burnup charts
## Burnup charts **(PREMIUM)**
 
> - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/6903) in [GitLab Starter](https://about.gitlab.com/pricing/) 13.6.
> - [Feature flag removed](https://gitlab.com/gitlab-org/gitlab/-/issues/268350) in [GitLab Starter](https://about.gitlab.com/pricing/) 13.7.
> - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/6903) in GitLab 13.6.
> - [Feature flag removed](https://gitlab.com/gitlab-org/gitlab/-/issues/268350) in GitLab 13.7.
> - Moved to GitLab Premium in 13.9.
 
Burnup charts show the assigned and completed work for a milestone.
 
doc/user/project/milestones/index.md
+ 16
− 8
View file @ d5aae486
@@ -123,10 +123,16 @@ From the project and group issue/merge request list pages, you can [filter](../.
 
### Filtering in issue boards
 
- From [project issue boards](../issue_board.md), you can filter by both group milestones and project milestones in the [search and filter bar](../../search/index.md#issue-boards).
- From [group issue boards](../issue_board.md#group-issue-boards), you can filter by only group milestones in the [search and filter bar](../../search/index.md#issue-boards). **(PREMIUM)**
- From [project issue boards](../issue_board.md), you can filter by both group milestones and project milestones in the [issue board configuration](../issue_board.md#configurable-issue-boards). **(STARTER)**
- From [group issue boards](../issue_board.md#group-issue-boards) you can filter by only group milestones in the [issue board configuration](../issue_board.md#configurable-issue-boards). **(STARTER)**
From [project issue boards](../issue_board.md), you can filter by both group milestones and project
milestones in:
- [Search and filter bar](../../search/index.md#issue-boards)
- [Issue board configuration](../issue_board.md#configurable-issue-boards)
From [group issue boards](../issue_board.md#group-issue-boards), you can filter by only group milestones in:
- [Search and filter bar](../../search/index.md#issue-boards)
- [Issue board configuration](../issue_board.md#configurable-issue-boards)
 
### Special milestone filters
 
@@ -155,15 +161,17 @@ There are also tabs below these that show the following:
- **Participants**: Shows all assignees of issues assigned to the milestone.
- **Labels**: Shows all labels that are used in issues assigned to the milestone.
 
### Project Burndown Charts **(STARTER)**
### Project Burndown Charts
 
For project milestones in [GitLab Starter](https://about.gitlab.com/pricing/), a [burndown chart](burndown_and_burnup_charts.md) is in the milestone view, showing the progress of completing a milestone.
For project milestones, a [burndown chart](burndown_and_burnup_charts.md) is in the milestone view,
showing the progress of completing a milestone.
 
![burndown chart](img/burndown_chart_v13_6.png)
 
### Group Burndown Charts **(STARTER)**
### Group Burndown Charts
 
For group milestones in [GitLab Starter](https://about.gitlab.com/pricing/), a [burndown chart](burndown_and_burnup_charts.md) is in the milestone view, showing the progress of completing a milestone.
For group milestones, a [burndown chart](burndown_and_burnup_charts.md) is in the milestone view,
showing the progress of completing a milestone.
 
### Milestone sidebar
 
doc/user/project/service_desk.md
+ 4
− 7
View file @ d5aae486
@@ -6,9 +6,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w
 
# Service Desk **(FREE)**
 
> - [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/215364) to [GitLab Free](https://about.gitlab.com/pricing/) in 13.2.
> - Moved to GitLab Free in 13.2.
 
Service Desk is a module that allows your team to connect
with any external party through email, without any external tools.
@@ -89,9 +87,8 @@ Service Desk is now enabled for this project! You should be able to access it fr
 
### Using customized email templates
 
> - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/2460) in [GitLab Premium](https://about.gitlab.com/pricing/) 12.7.
> - [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 Free](https://about.gitlab.com/pricing/) in 13.2.
> - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/2460) in GitLab Premium 12.7.
> - Moved to GitLab Free in 13.2.
 
An email is sent to the author when:
 
@@ -159,7 +156,7 @@ To edit the custom email display name:
 
### Using custom email address
 
> - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/2201) in [GitLab Premium](https://about.gitlab.com/pricing/) 13.0.
> - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/2201) in GitLab Premium 13.0.
> - [Feature flag removed](https://gitlab.com/gitlab-org/gitlab/-/issues/284656) in GitLab 13.8.
 
If the `service_desk_email` is configured, then you can create Service Desk
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