Skip to content

Links to moved FOSS issues should be updated

There is a huge number of links to issues in the FOSS repo. Many of these issues are closed, and will stay in the FOSS repo permanently. There is probably still a large number of these that were open when we moved to a Single Codebase, which were therefore moved to the gitlab repo.

One "solution" is that whenever you are working on a doc, and see a link to something like https://gitlab.com/gitlab-org/gitlab-foss/issues/#####, you could check if the issue was moved and thus update the link.

The problem with this "solution" is that there is no way to know if someone else has already checked a link. Unless someone else has a good idea, it might be best to find a "volunteer" to sit down and check all to gitlab-foss issues in one go, and update them as needed, so that we don't repeatedly check the same links.

At first count (none in runner or charts):

CE = 263 links 
./install/requirements.md:It does **not** run on Microsoft Windows, and we have no plans to support it in the near future. For the latest development status view this [issue](https://gitlab.com/gitlab-org/gitlab-foss/issues/46567).
./install/aws/index.md:[open an issue](https://gitlab.com/gitlab-org/gitlab-foss/issues/new)
./install/installation.md:**Note:** In order to receive mail notifications, make sure to install a mail server. By default, Debian is shipped with exim4 but this [has problems](https://gitlab.com/gitlab-org/gitlab-foss/issues/12754) while Ubuntu does not ship with one. The recommended mail server is postfix and you can install it with:
./update/upgrading_from_source.md:[dropped support for older versions](https://gitlab.com/gitlab-org/gitlab-foss/issues/54255).
./system_hooks/system_hooks.md:`owner_name` and `owner_email` are always `null`. Please see <https://gitlab.com/gitlab-org/gitlab-foss/issues/39675>.
./system_hooks/system_hooks.md:`owner_name` and `owner_email` are always `null`. Please see <https://gitlab.com/gitlab-org/gitlab-foss/issues/39675>.
./system_hooks/system_hooks.md:`owner_name` and `owner_email` are always `null`. Please see <https://gitlab.com/gitlab-org/gitlab-foss/issues/39675>.
./customization/system_header_and_footer_messages.md:> [Added](https://gitlab.com/gitlab-org/gitlab-foss/issues/55057) to [GitLab Core](https://about.gitlab.com/pricing/) in 11.9.
./security/webhooks.md:> [Introduced](https://gitlab.com/gitlab-org/gitlab-foss/issues/44496) in GitLab 12.2
./development/documentation/feature-change-workflow.md:  issues is forthcoming and you are welcome to join the [discussion](https://gitlab.com/gitlab-org/gitlab-foss/issues/56813).
./development/documentation/feature-change-workflow.md:     - **To request a post-merge technical writer review**, [create an issue for one using the Doc Review template](https://gitlab.com/gitlab-org/gitlab-foss/issues/new?issuable_template=Doc%20Review) and link it from the MR that makes the doc change.
./development/documentation/feature-change-workflow.md:- Upon merging, if a technical writer review has not been performed and there is not yet a linked issue for a follow-up review, the maintainer should [create an issue using the Doc Review template](https://gitlab.com/gitlab-org/gitlab-foss/issues/new?issuable_template=Doc%20Review), link it from the MR, and
./development/documentation/improvement-workflow.md:To request a post-merge review, [create an issue for one using the Doc Review template](https://gitlab.com/gitlab-org/gitlab-foss/issues/new?issuable_template=Doc%20Review) and link it from the MR that makes the doc change.
./development/documentation/improvement-workflow.md:1. After merging, if there has not been a technical writer review and an issue for a follow-up review was not already created and linked from the MR, [create the issue using the Doc Review template](https://gitlab.com/gitlab-org/gitlab-foss/issues/new?issuable_template=Doc%20Review) and link it from the MR.
./development/documentation/improvement-workflow.md:considered/handled by technical writers, devs, and other SMEs, please [create an issue](https://gitlab.com/gitlab-org/gitlab-foss/issues/new?issuable_template=Documentation)
./development/documentation/styleguide.md:For more information, see the [confidential issue](../../user/project/issues/confidential_issues.md) `https://gitlab.com/gitlab-org/gitlab-foss/issues/<issue_number>`.
./development/documentation/styleguide.md:  ([Introduced](https://gitlab.com/gitlab-org/gitlab-foss/issues/61027) in GitLab 12.1.)
./development/documentation/styleguide.md:[ce-1242]: https://gitlab.com/gitlab-org/gitlab-foss/issues/1242
./development/architecture.md:[Alert manager](https://prometheus.io/docs/alerting/alertmanager/) is a tool provided by Prometheus that _"handles alerts sent by client applications such as the Prometheus server. It takes care of deduplicating, grouping, and routing them to the correct receiver integration such as email, PagerDuty, or OpsGenie. It also takes care of silencing and inhibition of alerts."_ You can read more in [issue #45740](https://gitlab.com/gitlab-org/gitlab-foss/issues/45740) about what we will be alerting on.
./development/background_migrations.md:[issue-rspec-hooks]: https://gitlab.com/gitlab-org/gitlab-foss/issues/35351
./development/background_migrations.md:[reliable-sidekiq]: https://gitlab.com/gitlab-org/gitlab-foss/issues/36791
./development/filtering_by_label.md:[issue #15557](https://gitlab.com/gitlab-org/gitlab-foss/issues/15557)).
./development/filtering_by_label.md:In [issue #37137](https://gitlab.com/gitlab-org/gitlab-foss/issues/37137)
./development/filtering_by_label.md:[issue #49651](https://gitlab.com/gitlab-org/gitlab-foss/issues/49651),
./development/filtering_by_label.md:And our [tests in issue #49651](https://gitlab.com/gitlab-org/gitlab-foss/issues/49651#note_188777346)
./development/changelog.md:[started brainstorming]: https://gitlab.com/gitlab-org/gitlab-foss/issues/17826
./development/migration_style_guide.md:treats it as an SQL literal. It's also a required deprecation for [Rails 6](https://gitlab.com/gitlab-org/gitlab-foss/issues/61451).
./development/contributing/issue_workflow.md:**[Search the issue tracker](https://gitlab.com/gitlab-org/gitlab-foss/issues)** for similar entries before
./development/contributing/issue_workflow.md:We also organize [issue bash events](https://gitlab.com/gitlab-org/gitlab-foss/issues/17815)
./development/contributing/issue_workflow.md:[bringing the time tracking API to GitLab CE](https://gitlab.com/gitlab-org/gitlab-foss/issues/25517#note_20019084).
./development/contributing/issue_workflow.md:[issue tracker of CE](https://gitlab.com/gitlab-org/gitlab-foss/issues).
./development/contributing/issue_workflow.md:[`feature`](https://gitlab.com/gitlab-org/gitlab-foss/issues?label_name=feature) label. For the time being, users that are not members
./development/contributing/issue_workflow.md:[8.3 Regressions]: https://gitlab.com/gitlab-org/gitlab-foss/issues/4127
./development/contributing/issue_workflow.md:we use the ~"technical debt" label in [GitLab's issue tracker](https://gitlab.com/gitlab-org/gitlab-foss/issues).
./development/shell_scripting_guide/index.md:It is an [ongoing effort](https://gitlab.com/gitlab-org/gitlab-foss/issues/64016) to evaluate different tools for the
./development/polling.md:- [ETag proposal](https://gitlab.com/gitlab-org/gitlab-foss/issues/26926)
./development/module_with_instance_variables.md:https://gitlab.com/gitlab-org/gitlab-foss/issues/23786)
./development/module_with_instance_variables.md:https://gitlab.com/gitlab-org/gitlab-foss/issues/13484)
./development/performance.md:[#15607]: https://gitlab.com/gitlab-org/gitlab-foss/issues/15607
./development/namespaces_storage_statistics.md:[database queries transactions on production](https://gitlab.com/gitlab-org/gitlab-foss/issues/62488)
./development/namespaces_storage_statistics.md:   - Keeping in mind the length of the transaction that involves updating `project_statistics`(<https://gitlab.com/gitlab-org/gitlab-foss/issues/62488>), the insertion should be done in a different transaction and through a Sidekiq Job.
./development/namespaces_storage_statistics.md:[enforcing storage limits](https://gitlab.com/gitlab-org/gitlab-foss/issues/30421), this is not a major problem.
./development/namespaces_storage_statistics.md:- <https://gitlab.com/gitlab-org/gitlab-foss/issues/62214>
./development/namespaces_storage_statistics.md:on <https://gitlab.com/gitlab-org/gitlab-foss/issues/64092>: No problem has been reported so far.
./development/go_guide/index.md:Once [recursive includes](https://gitlab.com/gitlab-org/gitlab-foss/issues/56836)
./development/testing_guide/flaky_tests.md:- [`rspec-retry` is bitting us when some API specs fail](https://gitlab.com/gitlab-org/gitlab-foss/issues/29242): <https://gitlab.com/gitlab-org/gitlab-foss/merge_requests/9825>
./development/testing_guide/flaky_tests.md:- [Sporadic RSpec failures due to `PG::UniqueViolation`](https://gitlab.com/gitlab-org/gitlab-foss/issues/28307#note_24958837): <https://gitlab.com/gitlab-org/gitlab-foss/merge_requests/9846>
./development/testing_guide/flaky_tests.md:  - [Capybara.reset_session! should be called before requests are blocked](https://gitlab.com/gitlab-org/gitlab-foss/issues/33779): <https://gitlab.com/gitlab-org/gitlab-foss/merge_requests/12224>
./development/testing_guide/flaky_tests.md:  - [Make `spec/mailers/notify_spec.rb` more robust](https://gitlab.com/gitlab-org/gitlab-foss/issues/20121): <https://gitlab.com/gitlab-org/gitlab-foss/merge_requests/10015>
./development/testing_guide/flaky_tests.md:  - [Transient failure in spec/requests/api/commits_spec.rb](https://gitlab.com/gitlab-org/gitlab-foss/issues/27988#note_25342521): <https://gitlab.com/gitlab-org/gitlab-foss/merge_requests/9944>
./development/testing_guide/flaky_tests.md:  - [Replace FFaker factory data with sequences](https://gitlab.com/gitlab-org/gitlab-foss/issues/29643): <https://gitlab.com/gitlab-org/gitlab-foss/merge_requests/10184>
./development/testing_guide/flaky_tests.md:  - [Transient failure in spec/finders/issues_finder_spec.rb](https://gitlab.com/gitlab-org/gitlab-foss/issues/30211#note_26707685): <https://gitlab.com/gitlab-org/gitlab-foss/merge_requests/10404>
./development/testing_guide/flaky_tests.md:- [Be sure to create all the data the test need before starting exercize](https://gitlab.com/gitlab-org/gitlab-foss/issues/32622#note_31128195): <https://gitlab.com/gitlab-org/gitlab-foss/merge_requests/12059>
./development/testing_guide/flaky_tests.md:- [Bis](https://gitlab.com/gitlab-org/gitlab-foss/issues/34609#note_34048715): <https://gitlab.com/gitlab-org/gitlab-foss/merge_requests/12604>
./development/testing_guide/flaky_tests.md:- [Bis](https://gitlab.com/gitlab-org/gitlab-foss/issues/34698#note_34276286): <https://gitlab.com/gitlab-org/gitlab-foss/merge_requests/12664>
./development/testing_guide/flaky_tests.md:- [Assert against the underlying database state instead of against a page's content](https://gitlab.com/gitlab-org/gitlab-foss/issues/31437): <https://gitlab.com/gitlab-org/gitlab-foss/merge_requests/10934>
./development/testing_guide/flaky_tests.md:- [Transient failure of spec/features/issues/filtered_search/filter_issues_spec.rb](https://gitlab.com/gitlab-org/gitlab-foss/issues/29241#note_26743936): <https://gitlab.com/gitlab-org/gitlab-foss/merge_requests/10411>
./development/testing_guide/flaky_tests.md:- [Don't wait for AJAX when no AJAX request is fired](https://gitlab.com/gitlab-org/gitlab-foss/issues/30461): <https://gitlab.com/gitlab-org/gitlab-foss/merge_requests/10454>
./development/testing_guide/flaky_tests.md:- [Bis](https://gitlab.com/gitlab-org/gitlab-foss/issues/34647): <https://gitlab.com/gitlab-org/gitlab-foss/merge_requests/12626>
./development/testing_guide/review_apps.md:[In the past](https://gitlab.com/gitlab-org/gitlab-foss/issues/62834), it happened
./development/testing_guide/review_apps.md:[password-bug]: https://gitlab.com/gitlab-org/gitlab-foss/issues/53621
./development/testing_guide/testing_levels.md:[#23768]: https://gitlab.com/gitlab-org/gitlab-foss/issues/23768
./development/testing_guide/frontend_testing.md:- Jest runs in a Node.js environment, not in a browser. Support for running Jest tests in a browser [is planned](https://gitlab.com/gitlab-org/gitlab-foss/issues/58205).
./development/testing_guide/frontend_testing.md:See also the issue for [support running Jest tests in browsers](https://gitlab.com/gitlab-org/gitlab-foss/issues/58205).
./development/testing_guide/frontend_testing.md:All tests in `spec/javascripts/` will eventually be migrated to `spec/frontend/` (see also [#52483](https://gitlab.com/gitlab-org/gitlab-foss/issues/52483)).
./development/testing_guide/frontend_testing.md:These were removed from the codebase in May 2018 ([#23036](https://gitlab.com/gitlab-org/gitlab-foss/issues/23036)).
./development/gitaly.md:issue](https://gitlab.com/gitlab-org/gitlab-foss/issues/57317) for more
./development/i18n/translation.md:[open an issue](https://gitlab.com/gitlab-org/gitlab-foss/issues).
./development/i18n/merging_translations.md:[issue](https://gitlab.com/gitlab-org/gitlab-foss/issues/49208)
./development/fe_guide/style_guide_js.md:[#34371]: https://gitlab.com/gitlab-org/gitlab-foss/issues/34371
./development/fe_guide/performance.md:For example, if you were to visit [gitlab.com/gitlab-org/gitlab-foss/issues](https://gitlab.com/gitlab-org/gitlab-foss/issues),
./development/fe_guide/development_process.md:  - [ ] **Architecture plan:** Create a plan aligned with GitLab's architecture, how you are going to do the implementation, for example Vue application setup and its components (through [onion skinning](https://gitlab.com/gitlab-org/gitlab-foss/issues/35873#note_39994091)), Store structure and data flow, which existing Vue components can you reuse. It's a good idea to go through your plan with another engineer to refine it.
./development/import_export.md:| [Slow JSON](https://gitlab.com/gitlab-org/gitlab-foss/issues/54084) loading/dumping models from the database | [split the worker](https://gitlab.com/gitlab-org/gitlab-foss/issues/54085) |
./development/import_export.md:| High memory usage (see also some [analysis](https://gitlab.com/gitlab-org/gitlab-foss/issues/35389) | DB Commit sweet spot that uses less memory |
./development/import_export.md:the code hasn't been refactored in a long time. We should perform a [code audit](https://gitlab.com/gitlab-org/gitlab-foss/issues/42135)
./ci/ci_cd_for_external_repos/index.md:> [Introduced](https://gitlab.com/gitlab-org/gitlab-foss/issues/65139) in GitLab Premium 12.3.
./ci/docker/using_kaniko.md:> [Introduced](https://gitlab.com/gitlab-org/gitlab-foss/issues/45512) in GitLab 11.2.
./ci/docker/using_docker_build.md:  #41227](https://gitlab.com/gitlab-org/gitlab-foss/issues/41227)):
./ci/pipelines.md:> [Introduced](https://gitlab.com/gitlab-org/gitlab-foss/issues/14664) in GitLab
./ci/junit_test_reports.md:> [Introduced](https://gitlab.com/gitlab-org/gitlab-foss/issues/45318) in GitLab 11.2.
./ci/junit_test_reports.md:|`<testcase>` does not have `classname` attribute|ESlint, sass-lint|<https://gitlab.com/gitlab-org/gitlab-foss/issues/50964>|
./ci/interactive_web_terminal/index.md:> [Introduced](https://gitlab.com/gitlab-org/gitlab-foss/issues/50144) in GitLab 11.3.
./ci/interactive_web_terminal/index.md:issue](https://gitlab.com/gitlab-org/gitlab-foss/issues/52611) for progress on
./ci/variables/README.md:> [Introduced](https://gitlab.com/gitlab-org/gitlab-foss/issues/46806) in GitLab 11.11.
./ci/variables/README.md:> [Introduced](https://gitlab.com/gitlab-org/gitlab-foss/issues/13784) in GitLab 11.10
./ci/variables/README.md:  [In GitLab 12.2](https://gitlab.com/gitlab-org/gitlab-foss/issues/63043)
./ci/variables/README.md:> [Introduced](https://gitlab.com/gitlab-org/gitlab-foss/issues/49056) in GitLab 11.7.
./ci/variables/README.md:> [Introduced](https://gitlab.com/gitlab-org/gitlab-foss/issues/44059) in GitLab 10.8.
./ci/variables/README.md:[ce-13784]: https://gitlab.com/gitlab-org/gitlab-foss/issues/13784 "Simple protection of CI variables"
./ci/yaml/README.md:> - [Introduced](https://gitlab.com/gitlab-org/gitlab-foss/issues/47063) in GitLab 12.2.
./ci/yaml/README.md:  in the first stage (see [issue #65504](https://gitlab.com/gitlab-org/gitlab-foss/issues/65504)).
./ci/yaml/README.md:  dependencies or depend on jobs in the current stage (see [issue #65505](https://gitlab.com/gitlab-org/gitlab-foss/issues/65505)).
./ci/yaml/README.md:> [Introduced](https://gitlab.com/gitlab-org/gitlab-foss/issues/53903) in GitLab 11.7.
./ci/yaml/README.md:> [Introduced](https://gitlab.com/gitlab-org/gitlab-foss/issues/53445) in GitLab 11.7.
./ci/yaml/README.md:> [Introduced](https://gitlab.com/gitlab-org/gitlab-foss/issues/56836) in GitLab 11.9.
./ci/yaml/README.md:[ce-19232]: https://gitlab.com/gitlab-org/gitlab-foss/issues/19232
./ci/merge_request_pipelines/index.md:> [Introduced](https://gitlab.com/gitlab-org/gitlab-foss/issues/15310) in GitLab 11.6.
./ci/merge_request_pipelines/index.md:see [the issue about the permission extension](https://gitlab.com/gitlab-org/gitlab-foss/issues/23902).
./ci/merge_request_pipelines/pipelines_for_merged_results/index.md:  To follow progress, see [#58226](https://gitlab.com/gitlab-org/gitlab-foss/issues/58226).
./ci/directed_acyclic_graph/index.md:> [Introduced](https://gitlab.com/gitlab-org/gitlab-foss/issues/47063) in GitLab 12.2 (enabled by `ci_dag_support` feature flag).
./ci/jenkins/index.md:  to allow certain jobs to break this sequencing as needed with our [directed acyclic graph](https://gitlab.com/gitlab-org/gitlab-foss/issues/47063)
./ci/multi_project_pipelines.md:[status attribution](https://gitlab.com/gitlab-org/gitlab-foss/issues/39640).
./ci/review_apps/index.md:> - [Introduced](https://gitlab.com/gitlab-org/gitlab-foss/issues/21971) in GitLab 8.12. Further additions were made in GitLab 8.13 and 8.14.
./ci/caching/index.md:  [https://gitlab.com/gitlab-org/gitlab-foss/issues/15530](https://gitlab.com/gitlab-org/gitlab-foss/issues/15530)
./ci/caching/index.md:> [Introduced](https://gitlab.com/gitlab-org/gitlab-foss/issues/41249) in GitLab 10.4.
./integration/gmail_action_buttons_for_gitlab.md:You can check how it looks going through all the steps laid out in the "Registering with Google" doc in [this GitLab.com issue](https://gitlab.com/gitlab-org/gitlab-foss/issues/1517).
./integration/saml.md:> [Introduced](https://gitlab.com/gitlab-org/gitlab-foss/issues/43806) in GitLab 10.7.
./articles/index.md:The list of technical articles was [deprecated](https://gitlab.com/gitlab-org/gitlab-foss/issues/41138) in favor of having them linked from their topic-related documentation:
./user/admin_area/settings/usage_statistics.md:[ce-23361]: https://gitlab.com/gitlab-org/gitlab-foss/issues/23361
./user/snippets.md:> [Introduced](https://gitlab.com/gitlab-org/gitlab-foss/issues/12910) in GitLab 9.2.
./user/discussions/index.md:> [Introduced](https://gitlab.com/gitlab-org/gitlab-foss/issues/26723) in GitLab 11.5.
./user/discussions/index.md:> [Introduced](https://gitlab.com/gitlab-org/gitlab-foss/issues/18008) in GitLab 11.6.
./user/discussions/index.md:[#54404](https://gitlab.com/gitlab-org/gitlab-foss/issues/54404).
./user/discussions/index.md:> [Introduced](https://gitlab.com/gitlab-org/gitlab-foss/issues/53310) in GitLab 11.10.
./user/discussions/index.md:> [Introduced](https://gitlab.com/gitlab-org/gitlab-foss/issues/30299) in GitLab 11.9
./user/discussions/index.md:[ce-31847]: https://gitlab.com/gitlab-org/gitlab-foss/issues/31847
./user/group/subgroups/index.md:[ce-2772]: https://gitlab.com/gitlab-org/gitlab-foss/issues/2772
./user/group/subgroups/index.md:[issue]: https://gitlab.com/gitlab-org/gitlab-foss/issues/30472#note_27747600
./user/group/clusters/index.md:> [Introduced](https://gitlab.com/gitlab-org/gitlab-foss/issues/34758) in GitLab 11.6.
./user/group/clusters/index.md:[GitLab 11.4](https://gitlab.com/gitlab-org/gitlab-foss/issues/29398), and
./user/group/clusters/index.md:[GitLab 11.5](https://gitlab.com/gitlab-org/gitlab-foss/issues/51716).
./user/group/index.md:> The **Groups** dropdown in the top navigation was [introduced](https://gitlab.com/gitlab-org/gitlab-foss/issues/36234) in [GitLab 11.1](https://about.gitlab.com/2018/07/22/gitlab-11-1-released/#groups-dropdown-in-navigation).
./user/instance_statistics/user_cohorts.md:> [Introduced](https://gitlab.com/gitlab-org/gitlab-foss/issues/23361)
./user/instance_statistics/user_cohorts.md:- The user visits pages related to Dashboards, Projects, Issues and Merge Requests ([introduced](https://gitlab.com/gitlab-org/gitlab-foss/issues/54947) in GitLab 11.8).
./user/instance_statistics/convdev.md:> [Introduced](https://gitlab.com/gitlab-org/gitlab-foss/issues/30469) in GitLab 9.3.
./user/instance_statistics/index.md:> [Introduced](https://gitlab.com/gitlab-org/gitlab-foss/issues/41416)
./user/clusters/environments.md:[planned](https://gitlab.com/gitlab-org/gitlab-foss/issues/63985).
./user/clusters/applications.md:progress](https://gitlab.com/gitlab-org/gitlab-foss/issues/51989).
./user/clusters/applications.md:> [Introduced](https://gitlab.com/gitlab-org/gitlab-foss/issues/65192) in GitLab 12.3 (enabled using `ingress_modsecurity` [feature flag](../../development/feature_flags/development.md#enabling-a-feature-flag-in-development)).
./user/clusters/applications.md:> [Introduced](https://gitlab.com/gitlab-org/gitlab-foss/issues/60665) in GitLab 11.11.
./user/project/settings/import_export.md:> - [Introduced](https://gitlab.com/gitlab-org/gitlab-foss/issues/3050) in GitLab 8.9.
./user/project/releases/index.md:> [Introduced](https://gitlab.com/gitlab-org/gitlab-foss/issues/41766) in GitLab 11.7.
./user/project/repository/reducing_the_repo_size_using_git.md:> [Introduced](https://gitlab.com/gitlab-org/gitlab-foss/issues/19376) in GitLab 11.6.
./user/project/repository/index.md:> [Introduced](https://gitlab.com/gitlab-org/gitlab-foss/issues/2508) in GitLab 9.1
./user/project/repository/index.md:> [Introduced](https://gitlab.com/gitlab-org/gitlab-foss/issues/45820) in GitLab 11.0
./user/project/repository/index.md:> Support for directory download was [introduced](https://gitlab.com/gitlab-org/gitlab-foss/issues/24704) in GitLab 11.11.
./user/project/badges.md:> [Introduced](https://gitlab.com/gitlab-org/gitlab-foss/issues/41174)
./user/project/web_ide/index.md:> [Brought to GitLab Core](https://gitlab.com/gitlab-org/gitlab-foss/issues/44157) in 10.7.
./user/project/web_ide/index.md:Shared Runners [do not yet support Interactive Web Terminals](https://gitlab.com/gitlab-org/gitlab-foss/issues/52611),
./user/project/issue_board.md:> - Multiple Issue Boards per project [moved](https://gitlab.com/gitlab-org/gitlab-foss/issues/53811) to [GitLab Core](https://about.gitlab.com/pricing/) in GitLab 12.1.
./user/project/clusters/serverless/index.md:> [Introduced](https://gitlab.com/gitlab-org/gitlab-foss/issues/58941) in GitLab 12.0.
./user/project/clusters/runbooks/index.md:> [Introduced](https://gitlab.com/gitlab-org/gitlab-foss/issues/45912) in GitLab 11.4.
./user/project/clusters/index.md:> - [Introduced](https://gitlab.com/gitlab-org/gitlab-foss/issues/35954) in GitLab 10.1 for projects.
./user/project/clusters/index.md:> - [Introduced](https://gitlab.com/gitlab-org/gitlab-foss/issues/34758) in
./user/project/clusters/index.md:> - [Introduced](https://gitlab.com/gitlab-org/gitlab-foss/issues/39840) in
./user/project/clusters/index.md:11.10](https://gitlab.com/gitlab-org/gitlab-foss/issues/58208), the cluster
./user/project/clusters/index.md:Starting from [GitLab 12.1](https://gitlab.com/gitlab-org/gitlab-foss/issues/55902), all GKE clusters created by GitLab are RBAC enabled. Take a look at the [RBAC section](#rbac-cluster-resources) for more information.
./user/project/clusters/index.md:Kubernetes integration is not supported for arm64 clusters. See the issue [Helm Tiller fails to install on arm64 cluster](https://gitlab.com/gitlab-org/gitlab-foss/issues/64044) for details.
./user/project/clusters/index.md:  Restricted service account for deployment was [introduced](https://gitlab.com/gitlab-org/gitlab-foss/issues/51716) in GitLab 11.5.
./user/project/wiki/index.md:> [Introduced](https://gitlab.com/gitlab-org/gitlab-foss/issues/33475) in GitLab 11.3.
./user/project/pipelines/settings.md:> [Introduced](https://gitlab.com/gitlab-org/gitlab-foss/issues/30120) in GitLab 11.8.
./user/project/merge_requests/merge_when_pipeline_succeeds.md:Users that expect to be able to merge a merge request in this scenario should ensure that [there is always a pipeline](https://gitlab.com/gitlab-org/gitlab-foss/issues/54226) and that it's succesful.
./user/project/merge_requests/index.md:> [Introduced](https://gitlab.com/gitlab-org/gitlab-foss/issues/13950) in GitLab 11.5.
./user/project/merge_requests/index.md:> [Introduced](https://gitlab.com/gitlab-org/gitlab-foss/issues/18008) in GitLab 11.6.
./user/project/merge_requests/index.md:> [Introduced](https://gitlab.com/gitlab-org/gitlab-foss/issues/64320) in GitLab 12.2.
./user/project/merge_requests/index.md:> [Introduced](https://gitlab.com/gitlab-org/gitlab-foss/issues/64320) in GitLab 12.2.
./user/project/merge_requests/index.md:> [Introduced](https://gitlab.com/gitlab-org/gitlab-foss/issues/64320) in GitLab 12.2.
./user/project/merge_requests/index.md:> [Introduced](https://gitlab.com/gitlab-org/gitlab-foss/issues/2383) in GitLab 10.5.
./user/project/operations/linking_to_an_external_dashboard.md:> [Introduced](https://gitlab.com/gitlab-org/gitlab-foss/issues/57171) in GitLab 12.0.
./user/project/integrations/prometheus.md:> [Introduced](https://gitlab.com/gitlab-org/gitlab-foss/issues/28916) in GitLab 10.5.
./user/project/integrations/prometheus.md:> [Introduced](https://gitlab.com/gitlab-org/gitlab-foss/issues/59974) in GitLab 12.1.
./user/project/integrations/prometheus.md:| `id` | string | no | Used for associating dashboard metrics with database records. Must be unique across dashboard configuration files. Required for [alerting](#setting-up-alerts-for-prometheus-metrics-ultimate) (support not yet enabled, see [relevant issue](https://gitlab.com/gitlab-org/gitlab-foss/issues/60319)). |
./user/project/integrations/prometheus.md:Since [version 12.2](https://gitlab.com/gitlab-org/gitlab-foss/issues/63373), GitLab will tag each incident issue with the `incident` label automatically. If the label does not yet exist, it will be created automatically as well.
./user/project/integrations/prometheus.md:> - GitLab 9.3 added the [numeric comparison](https://gitlab.com/gitlab-org/gitlab-foss/issues/27439) of the 30 minute averages.
./user/project/integrations/webhooks.md:> [Introduced](https://gitlab.com/gitlab-org/gitlab-foss/issues/20338) in GitLab 11.3.
./user/project/integrations/hangouts_chat.md:> [Introduced](https://gitlab.com/gitlab-org/gitlab-foss/issues/43756) in GitLab 11.2.
./user/project/protected_branches.md:> [Introduced](https://gitlab.com/gitlab-org/gitlab-foss/issues/53361) in GitLab 11.9.
./user/project/protected_branches.md:> [Introduced](https://gitlab.com/gitlab-org/gitlab-foss/issues/21393) in GitLab 9.3.
./user/project/protected_branches.md:- [Allow protected branches to be created](https://gitlab.com/gitlab-org/gitlab-foss/issues/53361) by Developers (and users with higher permission levels) through the API and the user interface.
./user/project/protected_branches.md:- Allow deletion of protected branches via the web interface ([issue #21393](https://gitlab.com/gitlab-org/gitlab-foss/issues/21393)).
./user/project/index.md:> [Introduced](https://gitlab.com/gitlab-org/gitlab-foss/issues/53671) in GitLab 11.8.
./user/project/new_ci_build_permissions_model.md:[#18994](https://gitlab.com/gitlab-org/gitlab-foss/issues/18994).
./user/project/new_ci_build_permissions_model.md:is a [proposal to add support](https://gitlab.com/gitlab-org/gitlab-foss/issues/18106).
./user/project/new_ci_build_permissions_model.md:GitLab API cannot be used via `CI_JOB_TOKEN` but there is a [proposal](https://gitlab.com/gitlab-org/gitlab-foss/issues/29566)
./user/project/new_ci_build_permissions_model.md:[comment]: https://gitlab.com/gitlab-org/gitlab-foss/issues/22484#note_16648302
./user/project/code_owners.md:> - [Support for group namespaces](https://gitlab.com/gitlab-org/gitlab-foss/issues/53182) added in GitLab Starter 12.1.
./user/project/labels.md:> - Priority sorting is based on the highest priority label only. [This discussion](https://gitlab.com/gitlab-org/gitlab-foss/issues/18554) considers changing this.
./user/project/labels.md:in an object, and not any of the lower prioritized labels. [This discussion](https://gitlab.com/gitlab-org/gitlab-foss/issues/18554)
./user/project/import/phabricator.md:> [Introduced](https://gitlab.com/gitlab-org/gitlab-foss/issues/60562) in
./user/project/import/manifest.md:> [Introduced](https://gitlab.com/gitlab-org/gitlab-foss/issues/28811) in GitLab 11.2.
./user/project/issues/sorting_issue_lists.md:> [Introduced](https://gitlab.com/gitlab-org/gitlab-foss/issues/62178) in GitLab 12.2.
./user/project/issues/managing_issues.md:  and a pre-filled description, the URL would be `https://gitlab.com/gitlab-org/gitlab-foss/issues/new?issue[title]=Validate%20new%20concept&issue[description]=Research%20idea`
./user/project/issues/managing_issues.md:  and a pre-filled description template, the URL would be `https://gitlab.com/gitlab-org/gitlab-foss/issues/new?issue[title]=Validate%20new%20concept&issuable_template=Research%20proposal`
./user/project/issues/confidential_issues.md:> [Introduced](https://gitlab.com/gitlab-org/gitlab-foss/issues/58583) in GitLab 12.1.
./user/project/pages/introduction.md:> [Introduced](https://gitlab.com/gitlab-org/gitlab-foss/issues/33422) in GitLab 11.5.
./user/project/pages/introduction.md:[public issue tracker]: https://gitlab.com/gitlab-org/gitlab-foss/issues?label_name=pages
./user/project/pages/index.md:> - [Ported](https://gitlab.com/gitlab-org/gitlab-foss/issues/14605) to GitLab Community Edition in GitLab 8.17.
./user/project/pages/index.md:> - Support for subgroup project's websites was [introduced](https://gitlab.com/gitlab-org/gitlab-foss/issues/30548) in GitLab 11.8.
./user/project/pages/index.md:> - Bundled project templates were [introduced](https://gitlab.com/gitlab-org/gitlab-foss/issues/47857) in GitLab 11.8.
./user/project/pages/custom_domains_ssl_tls_certification/lets_encrypt_integration.md:> [Introduced](https://gitlab.com/gitlab-org/gitlab-foss/issues/28996) in GitLab 12.1.
./user/project/pages/custom_domains_ssl_tls_certification/lets_encrypt_integration.md:such as [#64870](https://gitlab.com/gitlab-org/gitlab-foss/issues/64870).
./user/project/pages/custom_domains_ssl_tls_certification/lets_encrypt_integration.md:See all the related issues linked from this [issue's description](https://gitlab.com/gitlab-org/gitlab-foss/issues/28996)
./user/project/pages/custom_domains_ssl_tls_certification/index.md:> [Introduced](https://gitlab.com/gitlab-org/gitlab-foss/issues/28857) in GitLab 10.7.
./user/project/pages/getting_started_part_two.md:> [Introduced](https://gitlab.com/gitlab-org/gitlab-foss/issues/47857)
./user/profile/index.md:> [Introduced](https://gitlab.com/gitlab-org/gitlab-foss/issues/14078) in GitLab 11.3.
./user/instance/clusters/index.md:> [Introduced](https://gitlab.com/gitlab-org/gitlab-foss/issues/39840) in GitLab 11.11.
./user/analytics/cycle_analytics.md:[ce-20975]: https://gitlab.com/gitlab-org/gitlab-foss/issues/20975
./university/README.md:[evaluate](https://gitlab.com/gitlab-org/gitlab-foss/issues/41064) it.
./university/support/README.md:- Add [customer labels](https://gitlab.com/gitlab-org/gitlab-foss/issues?label_name%5B%5D=customer) for those issues relevant to our subscribers
./subscriptions/index.md:[environment specific variables not being passed](https://gitlab.com/gitlab-org/gitlab-foss/issues/52825).
./subscriptions/index.md:- [GitLab CE](https://gitlab.com/gitlab-org/gitlab-foss/issues/) for features
./raketasks/backup_restore.md:This is a [known issue](https://gitlab.com/gitlab-org/gitlab-foss/issues/62759). On GitLab 12.2 or newer, you can
./raketasks/backup_restore.md:This is a [known issue](https://gitlab.com/gitlab-org/gitlab-foss/issues/62759). On GitLab 12.2 or newer, you can
./raketasks/backup_restore.md:([issue 62759](https://gitlab.com/gitlab-org/gitlab-foss/issues/62759 "Incorrect permissions on registry filesystem after restore")).
./raketasks/import.md:importable](https://gitlab.com/gitlab-org/gitlab-foss/issues/41776).
./workflow/notifications.md:Further implementation is [being discussed](https://gitlab.com/gitlab-org/gitlab-foss/issues/42062).
./workflow/timezone.md:Currently, this rake task does not list timezones in TZInfo format required by GitLab Omnibus during a reconfigure: [#58672](https://gitlab.com/gitlab-org/gitlab-foss/issues/58672).
./workflow/lfs/manage_large_binaries_with_git_lfs.md:> [Introduced](https://gitlab.com/gitlab-org/gitlab-foss/issues/35856) in GitLab 10.5.
./api/project_snippets.md:[ce-29508]: https://gitlab.com/gitlab-org/gitlab-foss/issues/29508
./api/search.md:[ce-41763]: https://gitlab.com/gitlab-org/gitlab-foss/issues/41763
./api/releases/index.md:> - [Introduced](https://gitlab.com/gitlab-org/gitlab-foss/issues/41766) in GitLab 11.7.
./api/releases/index.md:> [Introduced](https://gitlab.com/gitlab-org/gitlab-foss/issues/38105) in GitLab 12.1.
./api/releases/links.md:> [Introduced](https://gitlab.com/gitlab-org/gitlab-foss/issues/41766) in GitLab 11.7.
./api/v3_to_v4.md:22, 2017. API v3 was removed in [GitLab 11.0](https://gitlab.com/gitlab-org/gitlab-foss/issues/36819).
./api/container_registry.md:> [Introduced](https://gitlab.com/gitlab-org/gitlab-foss/issues/55978) in GitLab 11.8.
./api/pipeline_schedules.md:> [Introduced](https://gitlab.com/gitlab-org/gitlab-foss/issues/34518) in GitLab 10.0.
./api/repository_submodules.md:> [Introduced](https://gitlab.com/gitlab-org/gitlab-foss/issues/41213) in GitLab 11.5
./api/README.md:[GitLab 11.0](https://gitlab.com/gitlab-org/gitlab-foss/issues/36819).
./api/README.md:> [Introduced](https://gitlab.com/gitlab-org/gitlab-foss/issues/40385) in GitLab
./api/project_import_export.md:[ce-41899]: https://gitlab.com/gitlab-org/gitlab-foss/issues/41899
./api/users.md:- User visiting pages related to Dashboards, Projects, Issues and Merge Requests ([introduced](https://gitlab.com/gitlab-org/gitlab-foss/issues/54947) in GitLab 11.8)
./api/members.md:**Note:** We plan to [change](https://gitlab.com/gitlab-org/gitlab-foss/issues/62284) this behavior to return highest access_level instead.
./api/tags.md:> Support for `search` was [introduced](https://gitlab.com/gitlab-org/gitlab-foss/issues/54401) in GitLab 11.8.
./api/group_level_variables.md:[ce-34519]: https://gitlab.com/gitlab-org/gitlab-foss/issues/34519
./api/milestones.md:> [Introduced](https://gitlab.com/gitlab-org/gitlab-foss/issues/53861) in GitLab 11.9
./gitlab-basics/create-project.md:> [Introduced](https://gitlab.com/gitlab-org/gitlab-foss/issues/26388) in GitLab 10.5.
./administration/logs.md:From [%12.1](https://gitlab.com/gitlab-org/gitlab-foss/issues/62756), user id and username are available on this log.
./administration/logs.md:> [Introduced](https://gitlab.com/gitlab-org/gitlab-foss/issues/59587) in GitLab 12.0.
./administration/git_protocol.md:> [Introduced](https://gitlab.com/gitlab-org/gitlab-foss/issues/46555) in GitLab 11.4.
./administration/git_protocol.md:> `https://gitlab.com/gitlab-org/gitlab-foss/issues/55769`) in GitLab 11.5.8, 11.6.6, 11.7.1, and 11.8+.
./administration/git_protocol.md:`https://gitlab.com/gitlab-org/gitlab-foss/issues/55769`.
./administration/high_availability/nfs.md:messages](https://gitlab.com/gitlab-org/gitlab-foss/issues/52017). This is
./administration/high_availability/README.md:- **Known Issues:** While validating the reference architecture, slow endpoints were discovered and are being investigated. [See issue #64335](https://gitlab.com/gitlab-org/gitlab-foss/issues/64335)
./administration/auth/google_secure_ldap.md:> [Introduced](https://gitlab.com/gitlab-org/gitlab-foss/issues/46391) in GitLab 11.9.
./administration/geo/replication/security_review.md:- See also: [more granular access control](https://gitlab.com/gitlab-org/gitlab-foss/issues/32730)
./administration/geo/replication/index.md:| Version-controlled personal snippets ([unsupported](https://gitlab.com/gitlab-org/gitlab-foss/issues/13426)) | No | No |
./administration/geo/replication/index.md:| Version-controlled project snippets ([unsupported](https://gitlab.com/gitlab-org/gitlab-foss/issues/13426)) | No | No |
./administration/geo/disaster_recovery/planned_failover.md:[ce-19739]: https://gitlab.com/gitlab-org/gitlab-foss/issues/19739
./administration/incoming_email.md:See GitLab issue [#30366](https://gitlab.com/gitlab-org/gitlab-foss/issues/30366)
./administration/merge_request_diffs.md:> [Introduced](https://gitlab.com/gitlab-org/gitlab-foss/issues/52568) in GitLab 11.8.
./administration/troubleshooting/debug.md:   [1] pry(main)> app.get 'https://gitlab.com/gitlab-org/gitlab-foss/issues/1?private_token=123456'
./administration/troubleshooting/gitlab_rails_cheat_sheet.md:See <https://gitlab.com/gitlab-org/gitlab-foss/issues/41758#note_54828133>.
./administration/troubleshooting/gitlab_rails_cheat_sheet.md:See <https://gitlab.com/gitlab-org/gitlab-foss/issues/41111>.
./administration/repository_storage_types.md:[ce-28283]: https://gitlab.com/gitlab-org/gitlab-foss/issues/28283
./administration/operations/ssh_certificates.md:adding it](https://gitlab.com/gitlab-org/gitlab-foss/issues/49218).
./administration/raketasks/uploads/sanitize.md:[report](https://gitlab.com/gitlab-org/gitlab-foss/issues/new) any issues at `gitlab.com` and use
./administration/raketasks/project_import_export.md:[ce-3050]: https://gitlab.com/gitlab-org/gitlab-foss/issues/3050
./administration/packages/container_registry.md:Additional information about this: [issue 18239](https://gitlab.com/gitlab-org/gitlab-foss/issues/18239).
./administration/job_traces.md:[ce-46097]: https://gitlab.com/gitlab-org/gitlab-foss/issues/46097
./administration/monitoring/gitlab_instance_administration_project/index.md:> [Introduced](https://gitlab.com/gitlab-org/gitlab-foss/issues/56883) in GitLab 12.2.
./administration/monitoring/prometheus/gitlab_metrics.md:Available since [Omnibus GitLab 9.3](https://gitlab.com/gitlab-org/gitlab-foss/issues/29118). For
./administration/monitoring/performance/grafana_configuration.md:> [Introduced](https://gitlab.com/gitlab-org/gitlab-foss/issues/61005) in GitLab 12.1.
./administration/pages/source.md:> [Introduced](https://gitlab.com/gitlab-org/gitlab-foss/issues/33422) in GitLab 11.5.
./administration/pages/index.md:>   [introduced](https://gitlab.com/gitlab-org/gitlab-foss/issues/30548) in GitLab 11.8.
./administration/pages/index.md:> [Introduced](https://gitlab.com/gitlab-org/gitlab-foss/issues/28996) in GitLab 12.1.
./administration/pages/index.md:> [Introduced](https://gitlab.com/gitlab-org/gitlab-foss/issues/33422) in GitLab 11.5.
./administration/pages/index.md:[ce-14605]: https://gitlab.com/gitlab-org/gitlab-foss/issues/14605
./topics/autodevops/index.md:[is scheduled to be removed](https://gitlab.com/gitlab-org/gitlab-foss/issues/56959).
./topics/autodevops/index.md:12.0](https://gitlab.com/gitlab-org/gitlab-foss/issues/56959).
./topics/autodevops/index.md:> [Introduced](https://gitlab.com/gitlab-org/gitlab-foss/issues/52447) in GitLab 11.10.
./topics/autodevops/index.md:> [Introduced](https://gitlab.com/gitlab-org/gitlab-foss/issues/38542) in GitLab 11.0.
./topics/autodevops/index.md:> [Introduced](https://gitlab.com/gitlab-org/gitlab-foss/issues/49056) in GitLab 11.7.
./topics/autodevops/index.md:[ce-37115]: https://gitlab.com/gitlab-org/gitlab-foss/issues/37115
Omnibus = 4 links 
./settings/nginx.md:  [GitLab CE Issue #30619](https://gitlab.com/gitlab-org/gitlab-foss/issues/30619).
./settings/nginx.md:in [this user comment](https://gitlab.com/gitlab-org/gitlab-foss/issues/624#note_299061).
./settings/configuration.md:yet](https://gitlab.com/gitlab-org/gitlab-foss/issues/65675).  An example
./settings/unicorn.md:NOTE: **Note:** Minimum required `worker_processes` is 2 in order for the web editor to work correctly, see [GitLab CE issue #18771](https://gitlab.com/gitlab-org/gitlab-foss/issues/18771) for details.
Edited by Ray Paik