From 03803b2bf84aa9a0c04f281f4fb13ab8c848733e Mon Sep 17 00:00:00 2001
From: Armin Hergenhan <ahergenhan@gitlab.com>
Date: Wed, 24 Apr 2024 02:17:31 +0000
Subject: [PATCH] Resolve "Manage: Import and Integrate Group documentation
updates"
---
.../settings/import_export_rate_limits.md | 2 -
.../project_integration_management.md | 2 -
doc/api/bulk_imports.md | 4 +-
doc/api/graphql/index.md | 6 +--
doc/api/graphql/removed_items.md | 40 -------------------
doc/api/group_relations_export.md | 2 -
doc/api/integrations.md | 11 ++---
doc/api/project_import_export.md | 8 +---
doc/api/project_relations_export.md | 1 -
doc/api/rest/deprecations.md | 2 +-
doc/api/rest/index.md | 8 +---
doc/api/system_hooks.md | 2 -
doc/development/bulk_import.md | 2 -
doc/development/i18n/externalization.md | 3 --
doc/development/integrations/jira_connect.md | 1 -
doc/integration/datadog.md | 4 +-
doc/integration/jira/development_panel.md | 2 +-
doc/integration/jira/dvcs/troubleshooting.md | 17 --------
doc/integration/jira/troubleshooting.md | 33 +++++----------
doc/user/group/import/index.md | 11 +----
doc/user/project/import/bitbucket_server.md | 1 -
doc/user/project/import/manifest.md | 1 -
doc/user/project/integrations/github.md | 2 -
doc/user/project/integrations/harbor.md | 2 -
.../project/integrations/webhook_events.md | 5 +--
doc/user/project/integrations/webhooks.md | 1 -
doc/user/project/integrations/zentao.md | 2 -
27 files changed, 28 insertions(+), 147 deletions(-)
diff --git a/doc/administration/settings/import_export_rate_limits.md b/doc/administration/settings/import_export_rate_limits.md
index 785870e93ae5a..36f41b8eba5b7 100644
--- a/doc/administration/settings/import_export_rate_limits.md
+++ b/doc/administration/settings/import_export_rate_limits.md
@@ -10,8 +10,6 @@ DETAILS:
**Tier:** Free, Premium, Ultimate
**Offering:** Self-managed
-> - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/35728) in GitLab 13.2.
-
You can configure the rate limits for imports and exports of projects and groups:
To change a rate limit:
diff --git a/doc/administration/settings/project_integration_management.md b/doc/administration/settings/project_integration_management.md
index 45805d82db92f..9a8d539706acd 100644
--- a/doc/administration/settings/project_integration_management.md
+++ b/doc/administration/settings/project_integration_management.md
@@ -83,8 +83,6 @@ Resetting an instance-level default setting removes the integration from all pro
### View projects that use custom settings
-> - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/218252) in GitLab 14.2.
-
Prerequisites:
- You must have administrator access to the instance.
diff --git a/doc/api/bulk_imports.md b/doc/api/bulk_imports.md
index 61a43784984b1..9ff808bd89489 100644
--- a/doc/api/bulk_imports.md
+++ b/doc/api/bulk_imports.md
@@ -10,7 +10,6 @@ DETAILS:
**Tier:** Free, Premium, Ultimate
**Offering:** GitLab.com, Self-managed, GitLab Dedicated
-> - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/64335) in GitLab 14.1.
> - Project migration [introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/390515) in GitLab 15.11.
With the group migration by direct transfer API, you can start and view the progress of migrations initiated with
@@ -27,7 +26,6 @@ prerequisites for [migrating groups by direct transfer](../user/group/import/ind
## Start a new group or project migration
-> - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/66353) in GitLab 14.2.
> - `project_entity` source type [introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/390515) in GitLab 15.11.
Use this endpoint to start a new group or project migration. Specify:
@@ -45,7 +43,7 @@ POST /bulk_imports
| `configuration[url]` | String | yes | Source GitLab instance URL. |
| `configuration[access_token]` | String | yes | Access token to the source GitLab instance. |
| `entities` | Array | yes | List of entities to import. |
-| `entities[source_type]` | String | yes | Source entity type. Valid values are `group_entity` (GitLab 14.2 and later) and `project_entity` (GitLab 15.11 and later). |
+| `entities[source_type]` | String | yes | Source entity type. Valid values are `group_entity` and `project_entity` (GitLab 15.11 and later). |
| `entities[source_full_path]` | String | yes | Source full path of the entity to import. For example, `gitlab-org/gitlab`. |
| `entities[destination_slug]` | String | yes | Destination slug for the entity. GitLab uses the slug as the URL path to the entity. The name of the imported entity is copied from the name of the source entity and not the slug. |
| `entities[destination_name]` | String | no | Deprecated: Use `destination_slug` instead. Destination slug for the entity. |
diff --git a/doc/api/graphql/index.md b/doc/api/graphql/index.md
index 225de082053c8..d9ee312d5110f 100644
--- a/doc/api/graphql/index.md
+++ b/doc/api/graphql/index.md
@@ -210,12 +210,12 @@ possible. You should [verify your API calls against the schema without the depre
#### Deprecation example
The following fields are deprecated in different minor releases, but both
-removed in GitLab 14.0:
+removed in GitLab 17.0:
| Field deprecated in | Reason |
|:--------------------|:-------|
-| 12.7 | GitLab traditionally has 12 minor releases per major release. To ensure the field is available for 6 more releases, it is removed in the 14.0 major release (and not 13.0). |
-| 13.6 | The removal in 14.0 allows for 6 months of availability. |
+| 15.7 | GitLab traditionally has 12 minor releases per major release. To ensure the field is available for 6 more releases, it is removed in the 17.0 major release (and not 16.0). |
+| 16.6 | The removal in 17.0 allows for 6 months of availability. |
### List of removed items
diff --git a/doc/api/graphql/removed_items.md b/doc/api/graphql/removed_items.md
index 3f1c464bce74c..4ff5dfb276fd4 100644
--- a/doc/api/graphql/removed_items.md
+++ b/doc/api/graphql/removed_items.md
@@ -76,43 +76,3 @@ Fields removed in GitLab 15.0.
| Field name | GraphQL type | Deprecated in | Use instead |
| ------------------------------------------ | ------------------------ | ------------- | ---------------------------------------------------------------------------------- |
| `defaultMergeCommitMessageWithDescription` | `GraphQL::Types::String` | 14.5 | None. Define a [merge commit template](../../user/project/merge_requests/commit_templates.md) in your project and use `defaultMergeCommitMessage`. |
-
-## GitLab 14.0
-
-Fields [removed](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/63293) in GitLab 14.0:
-
-### GraphQL Mutations
-
-| Argument name | Mutation | Deprecated in | Use instead |
-| -------------------- | -------------------- | ------------- | -------------------------- |
-| `updated_ids` | `todosMarkAllDone` | 13.2 | `todos` |
-| `updated_ids` | `todoRestoreMany` | 13.2 | `todos` |
-| `global_id` | `dastScannerProfileCreate`| 13.6 | `todos` |
-| - | `addAwardEmoji` | 13.2 | `awardEmojiAdd` |
-| - | `removeAwardEmoji` | 13.2 | `awardEmojiRemove` |
-| - | `toggleAwardEmoji` | 13.2 | `ToggleAwardEmoji` |
-| - | `runDastScan` | 13.5 | `dastOnDemandScanCreate` |
-| - | `dismissVulnerability` | 13.5 | `vulnerabilityDismiss` |
-| - | `revertVulnerabilityToDetected` | 13.5 | `vulnerabilityRevertToDetected` |
-
-### GraphQL Types
-
-| Field name | GraphQL type | Deprecated in | Use instead |
-| -------------------- | -------------------- | ------------- | -------------------------- |
-| `blob` | `SnippetType` | 13.3 | `blobs` |
-| `global_id` | `DastScannerProfileType` | 13.6 | `blobs` |
-| `vulnerabilities_count_by_day_and_severity` | `GroupType`, `QueryType` | 13.3 | None. Plaintext tokens no longer supported for security reasons. |
-
-## GitLab 13.6
-
-Prior to GitLab 14.0, deprecated items could be removed in `XX.6` releases.
-
-Fields [removed](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/44866) in GitLab 13.6:
-
-| Field name | GraphQL type | Deprecated in | Use instead |
-|----------------------|--------------------------|---------------|----------------------------|
-| `date` | `Timelog` | 12.10 | `spentAt` |
-| `designs` | `Issue`, `EpicIssue` | 12.2 | `designCollection` |
-| `latestPipeline` | `Commit` | 12.5 | `pipelines` |
-| `mergeCommitMessage` | `MergeRequest` | 11.8 | `latestMergeCommitMessage` |
-| `token` | `GrafanaIntegration` | 12.7 | None. Plaintext tokens no longer supported for security reasons. |
diff --git a/doc/api/group_relations_export.md b/doc/api/group_relations_export.md
index b5f6417b51691..a158c73888d86 100644
--- a/doc/api/group_relations_export.md
+++ b/doc/api/group_relations_export.md
@@ -10,8 +10,6 @@ DETAILS:
**Tier:** Free, Premium, Ultimate
**Offering:** GitLab.com, Self-managed, GitLab Dedicated
-> - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/59978) in GitLab 13.12.
-
The group relations export API partially exports a group's structure as separate files for each
top-level
relation (for example, milestones, boards, and labels).
diff --git a/doc/api/integrations.md b/doc/api/integrations.md
index 77bd8d008ad1c..93969bd8086df 100644
--- a/doc/api/integrations.md
+++ b/doc/api/integrations.md
@@ -12,11 +12,6 @@ DETAILS:
This API enables you to work with external services that integrate with GitLab.
-NOTE:
-In GitLab 14.4, the `services` endpoint was [renamed](https://gitlab.com/gitlab-org/gitlab/-/issues/334500) to `integrations`.
-Calls to the integrations API can be made to both `/projects/:id/services` and `/projects/:id/integrations`.
-The examples in this document refer to the endpoint at `/projects/:id/integrations`.
-
This API requires an access token with the Maintainer or Owner role.
## List all active integrations
@@ -447,10 +442,10 @@ Parameters:
|------------------------|---------|----------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| `api_key` | string | true | API key used for authentication with Datadog. |
| `api_url` | string | false | (Advanced) The full URL for your Datadog site. |
-| `datadog_env` | string | false | For self-managed deployments, set the `env%` tag for all the data sent to Datadog. |
-| `datadog_service` | string | false | Tag all data from this GitLab instance in Datadog. Can be used when managing several self-managed deployments. |
+| `datadog_env` | string | false | For self-managed deployments, set the `env%` tag for all the data sent to Datadog. |
+| `datadog_service` | string | false | Tag all data from this GitLab instance in Datadog. Can be used when managing several self-managed deployments. |
| `datadog_site` | string | false | The Datadog site to send data to. To send data to the EU site, use `datadoghq.eu`. |
-| `datadog_tags` | string | false | Custom tags in Datadog. Specify one tag per line in the format `key:value\nkey2:value2` ([introduced](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/79665) in GitLab 14.8.). |
+| `datadog_tags` | string | false | Custom tags in Datadog. Specify one tag per line in the format `key:value\nkey2:value2` |
| `archive_trace_events` | boolean | false | When enabled, job logs are collected by Datadog and displayed along with pipeline execution traces ([introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/346339) in GitLab 15.3). |
### Disable Datadog
diff --git a/doc/api/project_import_export.md b/doc/api/project_import_export.md
index ba0d435c85154..d6171206fe4c6 100644
--- a/doc/api/project_import_export.md
+++ b/doc/api/project_import_export.md
@@ -213,15 +213,13 @@ requests.post(url, headers=headers, data=data, files=files)
NOTE:
The maximum import file size can be set by the Administrator. It defaults to `0` (unlimited).
-As an administrator, you can modify the maximum import file size. To do so, use the `max_import_size` option in the [Application settings API](settings.md#change-application-settings) or the [Admin Area](../administration/settings/account_and_limit_settings.md). Default [modified](https://gitlab.com/gitlab-org/gitlab/-/issues/251106) from 50 MB to 0 in GitLab 13.8.
+As an administrator, you can modify the maximum import file size. To do so, use the `max_import_size` option in the [Application settings API](settings.md#change-application-settings) or the [Admin Area](../administration/settings/account_and_limit_settings.md).
## Import a file from a remote object storage
DETAILS:
**Status:** Beta
-> - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/282503) in GitLab 13.12 in [Beta](../policy/experiment-beta-support.md#beta) [with a flag](../administration/feature_flags.md) named `import_project_from_remote_file`. Enabled by default.
-
FLAG:
On self-managed GitLab, by default this feature is available. To hide the feature, an administrator can [disable the feature flag](../administration/feature_flags.md) named `import_project_from_remote_file`.
On GitLab.com and GitLab Dedicated, this feature is available.
@@ -357,9 +355,7 @@ Status can be one of:
## Import a file from AWS S3
-> - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/348874) in GitLab 14.9 in [Beta](https://handbook.gitlab.com/handbook/product/gitlab-the-product/#experiment-beta-ga), [with a flag](../administration/feature_flags.md) named `import_project_from_remote_file_s3`. Disabled by default.
-> - [Enabled on GitLab.com](https://gitlab.com/gitlab-org/gitlab/-/issues/348874) in GitLab 14.10.
-> - [Enabled on self-managed](https://gitlab.com/gitlab-org/gitlab/-/issues/350571) in GitLab 15.11. Feature flag `import_project_from_remote_file_s3` removed.
+> - [Generally available](https://gitlab.com/gitlab-org/gitlab/-/issues/350571) in GitLab 15.11. Feature flag `import_project_from_remote_file_s3` removed.
```plaintext
POST /projects/remote-import-s3
diff --git a/doc/api/project_relations_export.md b/doc/api/project_relations_export.md
index 5375c1d44ce95..2c46e7792a340 100644
--- a/doc/api/project_relations_export.md
+++ b/doc/api/project_relations_export.md
@@ -10,7 +10,6 @@ DETAILS:
**Tier:** Free, Premium, Ultimate
**Offering:** GitLab.com, Self-managed, GitLab Dedicated
-> - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/70330) in GitLab 14.4 behind the `bulk_import` [feature flag](../administration/feature_flags.md), disabled by default.
> - New application setting `bulk_import_enabled` introduced in GitLab 15.8. `bulk_import` feature flag removed.
The project relations export API partially exports a project's structure as separate files for each
diff --git a/doc/api/rest/deprecations.md b/doc/api/rest/deprecations.md
index ba54ba46dddd8..24e49e0724cfe 100644
--- a/doc/api/rest/deprecations.md
+++ b/doc/api/rest/deprecations.md
@@ -87,7 +87,7 @@ Breaking change. [Related issue](https://gitlab.com/gitlab-org/gitlab/-/issues/3
Occurrences of the `active` identifier in the GitLab Runner GraphQL API endpoints will be
renamed to `paused` in GitLab 16.0.
-- In v4 of the REST API, starting in GitLab 14.8, you can use the `paused` property in place of `active`
+- In v4 of the REST API, you can use the `paused` property in place of `active`
- In v5 of the REST API, this change will affect endpoints taking or returning `active` property, such as:
- `GET /runners`
- `GET /runners/all`
diff --git a/doc/api/rest/index.md b/doc/api/rest/index.md
index 61c474caafbac..baf3a060b92e1 100644
--- a/doc/api/rest/index.md
+++ b/doc/api/rest/index.md
@@ -518,10 +518,9 @@ The type of filter depends on the
`order_by` option used, and we can have more than one additional filter.
WARNING:
-The `Links` header was removed in GitLab 14.0 to be aligned with the
+The `Links` header was removed to be aligned with the
[W3C `Link` specification](https://www.w3.org/wiki/LinkHeader). The `Link`
-header was [added in GitLab 13.1](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/33714)
-and should be used instead.
+header should be used instead.
When the end of the collection is reached and there are no additional
records to retrieve, the `Link` header is absent and the resulting array is
@@ -866,13 +865,10 @@ specifically used by GitLab.com, see
The GitLab API supports the `application/json` content type by default, though
some API endpoints also support `text/plain`.
-In [GitLab 13.10 and later](https://gitlab.com/gitlab-org/gitlab/-/issues/250342),
API endpoints do not support `text/plain` by default, unless it's explicitly documented.
## Resolve requests detected as spam
-> - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/352913) in GitLab 14.9.
-
REST API requests can be detected as spam. If a request is detected as spam and:
- A CAPTCHA service is not configured, an error response is returned. For example:
diff --git a/doc/api/system_hooks.md b/doc/api/system_hooks.md
index 009c5b8da3bad..5cbccca67b0b9 100644
--- a/doc/api/system_hooks.md
+++ b/doc/api/system_hooks.md
@@ -52,8 +52,6 @@ Example response:
## Get system hook
-> - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/81595) in GitLab 14.9.
-
Get a system hook by its ID.
```plaintext
diff --git a/doc/development/bulk_import.md b/doc/development/bulk_import.md
index 4a916fcba3655..1ffd431360e9b 100644
--- a/doc/development/bulk_import.md
+++ b/doc/development/bulk_import.md
@@ -6,8 +6,6 @@ info: Any user with at least the Maintainer role can merge updates to this conte
# Group migration by direct transfer
-> - [Introduced](https://gitlab.com/groups/gitlab-org/-/epics/2771) in GitLab 13.7.
-
NOTE:
To use direct transfer, ensure your GitLab installation is accessible from
[GitLab IP addresses](../user/gitlab_com/index.md#ip-range) and has a public DNS entry.
diff --git a/doc/development/i18n/externalization.md b/doc/development/i18n/externalization.md
index 06095427662b1..79c54ac04ca5b 100644
--- a/doc/development/i18n/externalization.md
+++ b/doc/development/i18n/externalization.md
@@ -6,8 +6,6 @@ info: Any user with at least the Maintainer role can merge updates to this conte
# Internationalization for GitLab
-> - [Introduced](https://gitlab.com/gitlab-org/gitlab-foss/-/merge_requests/10669) in GitLab 9.2.
-
For working with internationalization (i18n),
[GNU gettext](https://www.gnu.org/software/gettext/) is used given it's the most
used tool for this task and there are many applications that help us work with it.
@@ -933,7 +931,6 @@ strings have been translated and approved. Even though a larger number of string
translated, only the approved translations display in the GitLab UI.
NOTE:
-[Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/221012) in GitLab 13.3:
Languages with less than 2% of translations are not available in the UI.
Suppose you want to add translations for a new language, for example, French:
diff --git a/doc/development/integrations/jira_connect.md b/doc/development/integrations/jira_connect.md
index 94309b3079868..a1aacd16f5e58 100644
--- a/doc/development/integrations/jira_connect.md
+++ b/doc/development/integrations/jira_connect.md
@@ -80,7 +80,6 @@ To avoid external dependencies like Gitpod and a Jira Cloud instance, use the [J
## Test the GitLab OAuth authentication flow
-> - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/81126) in GitLab 14.9 [with a flag](../../administration/feature_flags.md) named `jira_connect_oauth`. Disabled by default.
> - [Generally available](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/117648) in GitLab 16.0. Feature flag `jira_connect_oauth` removed.
GitLab for Jira users can authenticate with GitLab using GitLab OAuth.
diff --git a/doc/integration/datadog.md b/doc/integration/datadog.md
index 84d0074ba6a2e..76611502d3877 100644
--- a/doc/integration/datadog.md
+++ b/doc/integration/datadog.md
@@ -10,8 +10,6 @@ DETAILS:
**Tier:** Free, Premium, Ultimate
**Offering:** GitLab.com, Self-managed, GitLab Dedicated
-> - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/270123) in GitLab 14.1
-
The Datadog integration enables you to send CI/CD pipeline and job information to
[Datadog](https://www.datadoghq.com/). The [Datadog CI Visibility](https://app.datadoghq.com/ci)
product helps you monitor for job failures and performance issues, then troubleshoot them.
@@ -48,7 +46,7 @@ project, group, or instance level:
the integration generates.
<!-- vale gitlab.Spelling = YES -->
1. Optional. To define any custom tags for all spans at which the integration is being configured,
- enter one tag per line in **Tags**. Each line must be in the format `key:value`. ([Introduced](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/79665) in GitLab 14.8.)
+ enter one tag per line in **Tags**. Each line must be in the format `key:value`.
1. Optional. Select **Test settings**.
1. Select **Save changes**.
diff --git a/doc/integration/jira/development_panel.md b/doc/integration/jira/development_panel.md
index 0e430d9209415..9e219399f0537 100644
--- a/doc/integration/jira/development_panel.md
+++ b/doc/integration/jira/development_panel.md
@@ -36,7 +36,7 @@ This table shows the features available with the Jira DVCS connector and the Git
| Sync interval | Up to 60 minutes | Real time |
| Create branches | **{dotted-circle}** No | **{check-circle}** Yes (GitLab.com only) |
| Create a merge request from a branch | **{check-circle}** Yes | **{check-circle}** Yes |
-| Create a branch from a Jira issue | **{dotted-circle}** No | **{check-circle}** Yes ([introduced](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/66032) in GitLab 14.2) |
+| Create a branch from a Jira issue | **{dotted-circle}** No | **{check-circle}** Yes |
## Connected projects in GitLab
diff --git a/doc/integration/jira/dvcs/troubleshooting.md b/doc/integration/jira/dvcs/troubleshooting.md
index b412ca034e4b3..a8332f62184b0 100644
--- a/doc/integration/jira/dvcs/troubleshooting.md
+++ b/doc/integration/jira/dvcs/troubleshooting.md
@@ -89,23 +89,6 @@ Potential resolutions:
[GitLab account configuration](index.md#create-a-gitlab-application-for-dvcs). Review
the **Scopes** field and ensure the `api` checkbox is selected.
-## Error when adding an account in Jira
-
-After you complete the **Add New Account** form in Jira and authorize access, you might
-encounter these issues:
-
-- An `Error! Failed adding the account: [Error retrieving list of repositories]` error.
-- An `Account is already integrated with JIRA` error when you select **Try Again**.
-- An account is visible in the DVCS accounts view, but no repositories are listed.
-
-To resolve this issue:
-
-- If you're using GitLab Free, ensure you're using GitLab 13.4 or later.
-- If you're using GitLab versions 11.10-12.7, upgrade to GitLab 12.8.10 or later
- to resolve [an identified issue](https://gitlab.com/gitlab-org/gitlab/-/issues/37012).
-
-[Contact GitLab Support](https://about.gitlab.com/support/) if none of these reasons apply.
-
## `410 Gone` when connecting to Jira
When you connect to Jira and synchronize repositories, you might get a `410 Gone` error.
diff --git a/doc/integration/jira/troubleshooting.md b/doc/integration/jira/troubleshooting.md
index c72afc807c0d8..7140da4943ae3 100644
--- a/doc/integration/jira/troubleshooting.md
+++ b/doc/integration/jira/troubleshooting.md
@@ -132,32 +132,21 @@ To change all Jira projects to use instance-level integration settings:
1. In a [Rails console](../../administration/operations/rails_console.md#starting-a-rails-console-session), run the following:
- - In GitLab 15.0 and later:
+ ```ruby
+ Integrations::Jira.where(active: true, instance: false, inherit_from_id: nil).find_each do |integration|
+ default_integration = Integration.default_integration(integration.type, integration.project)
- ```ruby
- Integrations::Jira.where(active: true, instance: false, inherit_from_id: nil).find_each do |integration|
- default_integration = Integration.default_integration(integration.type, integration.project)
+ integration.inherit_from_id = default_integration.id
- integration.inherit_from_id = default_integration.id
-
- if integration.save(context: :manual_change)
- if Gitlab.version_info >= Gitlab::VersionInfo.new(16, 9)
- Integrations::Propagation::BulkUpdateService.new(default_integration, [integration]).execute
- else
- BulkUpdateIntegrationService.new(default_integration, [integration]).execute
- end
+ if integration.save(context: :manual_change)
+ if Gitlab.version_info >= Gitlab::VersionInfo.new(16, 9)
+ Integrations::Propagation::BulkUpdateService.new(default_integration, [integration]).execute
+ else
+ BulkUpdateIntegrationService.new(default_integration, [integration]).execute
end
end
- ```
-
- - In GitLab 14.10 and earlier:
-
- ```ruby
- jira_integration_instance_id = Integrations::Jira.find_by(instance: true).id
- Integrations::Jira.where(active: true, instance: false, template: false, inherit_from_id: nil).find_each do |integration|
- integration.update_attribute(:inherit_from_id, jira_integration_instance_id)
- end
- ```
+ end
+ ```
1. Modify and save the instance-level integration from the UI to propagate the changes to all group-level and project-level integrations.
diff --git a/doc/user/group/import/index.md b/doc/user/group/import/index.md
index 49ae181b1864f..e9851399e20e4 100644
--- a/doc/user/group/import/index.md
+++ b/doc/user/group/import/index.md
@@ -10,9 +10,6 @@ DETAILS:
**Tier:** Free, Premium, Ultimate
**Offering:** GitLab.com, Self-managed, GitLab Dedicated
-> - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/249160) in GitLab 13.7 for group resources [with a flag](../../feature_flags.md) named `bulk_import`. Disabled by default.
-> - Group items [enabled on GitLab.com and self-managed](https://gitlab.com/gitlab-org/gitlab/-/issues/338985) in GitLab 14.3.
-> - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/267945) in GitLab 14.4 for project resources [with a flag](../../feature_flags.md) named `bulk_import_projects`. Disabled by default.
> - [Enabled on GitLab.com](https://gitlab.com/gitlab-org/gitlab/-/issues/339941) in GitLab 15.6.
> - New application setting `bulk_import_enabled` [introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/383268) in GitLab 15.8. `bulk_import` feature flag removed.
> - `bulk_import_projects` feature flag [removed](https://gitlab.com/gitlab-org/gitlab/-/issues/339941) in GitLab 15.10.
@@ -188,8 +185,7 @@ Before migrating by using direct transfer, see the following prerequisites.
### Versions
-The source GitLab instance must be running GitLab 14.0 or later to import groups and GitLab 14.4 or later to import
-projects. However, to maximize the chance of a successful and performant migration, you should:
+To maximize the chance of a successful and performant migration, you should:
- To take advantage of [batched exports and imports](https://gitlab.com/groups/gitlab-org/-/epics/9036) of relations,
update the source and destinations instances to GitLab 16.2 or later.
@@ -247,7 +243,7 @@ Create the group you want to import to and connect the source GitLab instance:
- A new subgroup. On existing group's page, either:
- Select **New subgroup**.
- On the left sidebar, at the top, select **Create new** (**{plus}**) and **New subgroup**. Then select the **import an existing group** link.
-1. Enter the base URL of a GitLab instance running GitLab 14.0 or later.
+1. Enter the base URL of a GitLab instance.
1. Enter the [personal access token](../../../user/profile/personal_access_tokens.md) for your source GitLab instance.
1. Select **Connect instance**.
@@ -390,7 +386,6 @@ Some group items are excluded from migration because they either:
DETAILS:
**Status:** Beta
-> - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/267945) in GitLab 14.4 [with a flag](../../feature_flags.md) named `bulk_import_projects`. Disabled by default.
> - [Enabled on GitLab.com](https://gitlab.com/gitlab-org/gitlab/-/issues/339941) in GitLab 15.6.
> - `bulk_import_projects` feature flag [removed](https://gitlab.com/gitlab-org/gitlab/-/issues/339941) in GitLab 15.10.
> - Project-only migrations using API [added](https://gitlab.com/gitlab-org/gitlab/-/issues/390515) in GitLab 15.11.
@@ -545,8 +540,6 @@ You can also see all migrated entities with any failures related to them using a
### Stale imports
-> - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/352985) in GitLab 14.10.
-
When troubleshooting group migration, an import may not complete because the import workers took
longer than 8 hours to execute. In this case, the `status` of either a `BulkImport` or
`BulkImport::Entity` is `3` (`timeout`):
diff --git a/doc/user/project/import/bitbucket_server.md b/doc/user/project/import/bitbucket_server.md
index be25cba558223..6a157ede035a8 100644
--- a/doc/user/project/import/bitbucket_server.md
+++ b/doc/user/project/import/bitbucket_server.md
@@ -114,7 +114,6 @@ The importer attempts to find:
### User assignment by username
-> - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/218609) in GitLab 13.4 [with a flag](../../../administration/feature_flags.md) named `bitbucket_server_user_mapping_by_username`. Disabled by default.
> - Not recommended for production use.
FLAG:
diff --git a/doc/user/project/import/manifest.md b/doc/user/project/import/manifest.md
index d937eea7cf3d7..d765469756101 100644
--- a/doc/user/project/import/manifest.md
+++ b/doc/user/project/import/manifest.md
@@ -10,7 +10,6 @@ DETAILS:
**Tier:** Free, Premium, Ultimate
**Offering:** GitLab.com, Self-managed, GitLab Dedicated
-> - [Introduced](https://gitlab.com/gitlab-org/gitlab-foss/-/issues/28811) in GitLab 11.2.
> - Ability to re-import projects [introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/23905) in GitLab 15.9.
GitLab allows you to import all the required Git repositories
diff --git a/doc/user/project/integrations/github.md b/doc/user/project/integrations/github.md
index 4b81876024550..7178d8332518f 100644
--- a/doc/user/project/integrations/github.md
+++ b/doc/user/project/integrations/github.md
@@ -48,8 +48,6 @@ to configure pipelines to run for open pull requests.
### Static or dynamic status check names
-> - [Changed](https://gitlab.com/gitlab-org/gitlab/-/issues/9931) in GitLab 12.4 to make static status check names the default behavior for new projects.
-
A status check name can be static or dynamic:
- **Static**: The hostname of your
diff --git a/doc/user/project/integrations/harbor.md b/doc/user/project/integrations/harbor.md
index 452316cd82e2f..5ecde26033db2 100644
--- a/doc/user/project/integrations/harbor.md
+++ b/doc/user/project/integrations/harbor.md
@@ -10,8 +10,6 @@ DETAILS:
**Tier:** Free, Premium, Ultimate
**Offering:** GitLab.com, Self-managed, GitLab Dedicated
-> - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/80999) in GitLab 14.9.
-
You can use Harbor as the container registry for your GitLab project.
[Harbor](https://goharbor.io/) is an open-source registry that can help you manage artifacts across cloud-native compute platforms like Kubernetes and Docker.
diff --git a/doc/user/project/integrations/webhook_events.md b/doc/user/project/integrations/webhook_events.md
index 1e8f00683f1b8..c3a163fa76677 100644
--- a/doc/user/project/integrations/webhook_events.md
+++ b/doc/user/project/integrations/webhook_events.md
@@ -1143,9 +1143,6 @@ Payload example:
Pipeline events are triggered when the status of a pipeline changes.
-In [GitLab 13.9](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/53159)
-and later, the pipeline webhook returns only the latest jobs.
-
In [GitLab 15.1](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/89546)
and later, pipeline webhooks triggered by blocked users are not processed.
@@ -1546,7 +1543,7 @@ If the pipeline has a name, that name is the value of `commit.name`.
Deployment events are triggered when a deployment:
-- Starts ([introduced](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/41214) in GitLab 13.5)
+- Starts
- Succeeds
- Fails
- Is cancelled
diff --git a/doc/user/project/integrations/webhooks.md b/doc/user/project/integrations/webhooks.md
index 48fff564a7a70..4393530ae776b 100644
--- a/doc/user/project/integrations/webhooks.md
+++ b/doc/user/project/integrations/webhooks.md
@@ -182,7 +182,6 @@ For GitLab self-managed, an administrator can [change the webhook timeout limit]
## Auto-disabled webhooks
-> - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/60837) for project webhooks in GitLab 13.12 [with a flag](../../../administration/feature_flags.md) named `web_hooks_disable_failed`. Disabled by default.
> - [Generally available](https://gitlab.com/gitlab-org/gitlab/-/issues/329849) for project webhooks in GitLab 15.7. Feature flag `web_hooks_disable_failed` removed.
> - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/385902) for group webhooks in GitLab 15.10.
> - [Disabled on self-managed](https://gitlab.com/gitlab-org/gitlab/-/issues/390157) in GitLab 15.10 [with a flag](../../../administration/feature_flags.md) named `auto_disabling_web_hooks`.
diff --git a/doc/user/project/integrations/zentao.md b/doc/user/project/integrations/zentao.md
index d33611e574225..15f7bf4970c31 100644
--- a/doc/user/project/integrations/zentao.md
+++ b/doc/user/project/integrations/zentao.md
@@ -10,8 +10,6 @@ DETAILS:
**Tier:** Premium, Ultimate
**Offering:** GitLab.com, Self-managed, GitLab Dedicated
-> - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/338178) in GitLab 14.5.
-
WARNING:
This feature was [deprecated](https://gitlab.com/gitlab-org/gitlab/-/issues/377825) in GitLab 15.7.
This change is a breaking change.
--
GitLab