Skip to content
代码片段 群组 项目
提交 04b4da1c 编辑于 作者: Achilleas Pipinellis's avatar Achilleas Pipinellis
浏览文件

Merge branch 'remove-jira-github-enterprise-dvcs-connector' into 'master'

Remove Jira GitHub Enterprise DVCS connector

See merge request https://gitlab.com/gitlab-org/gitlab/-/merge_requests/119889



Merged-by: default avatarAchilleas Pipinellis <axil@gitlab.com>
Co-authored-by: default avatarMagdalena Frankiewicz <mfrankiewicz@gitlab.com>
Co-authored-by: default avatarLuke Duncalfe <lduncalfe@gitlab.com>
Co-authored-by: default avatarAshraf Khamis <akhamis@gitlab.com>
No related branches found
No related tags found
无相关合并请求
- title: "Jira DVCS connector for Jira Cloud and Jira 8.13 and earlier"
announcement_milestone: "15.1"
removal_milestone: "16.0"
breaking_change: true
reporter: m_frankiewicz
stage: Manage
issue_url: https://gitlab.com/gitlab-org/gitlab/-/issues/362168
body: |
The [Jira DVCS connector](https://docs.gitlab.com/ee/integration/jira/dvcs/) for Jira Cloud was deprecated in GitLab 15.1 and has been removed in 16.0. Use the [GitLab for Jira Cloud app](https://docs.gitlab.com/ee/integration/jira/connect-app.html) instead. The Jira DVCS connector was also deprecated for Jira 8.13 and earlier. You can only use the Jira DVCS connector with Jira Data Center or Jira Server in Jira 8.14 and later. Upgrade your Jira instance to Jira 8.14 or later, and reconfigure the Jira integration in your GitLab instance.
If you cannot upgrade your Jira instance in time and are on GitLab self-managed version, we offer a workaround until GitLab 16.6. This breaking change is deployed in GitLab 16.0 behind a feature flag named `jira_dvcs_end_of_life_amnesty`. The flag is disabled by default, but you can ask an administrator to enable the flag at any time. For questions related to this announcement, see the [feedback issue](https://gitlab.com/gitlab-org/gitlab/-/issues/408185).
...@@ -217,6 +217,15 @@ In GitLab 16.0 and later, the GraphQL query for runners will no longer return th ...@@ -217,6 +217,15 @@ In GitLab 16.0 and later, the GraphQL query for runners will no longer return th
- `PAUSED` has been replaced with the field, `paused: true`. - `PAUSED` has been replaced with the field, `paused: true`.
- `ACTIVE` has been replaced with the field, `paused: false`. - `ACTIVE` has been replaced with the field, `paused: false`.
### Jira DVCS connector for Jira Cloud and Jira 8.13 and earlier
WARNING:
This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/).
Review the details carefully before upgrading.
The [Jira DVCS connector](https://docs.gitlab.com/ee/integration/jira/dvcs/) for Jira Cloud was deprecated in GitLab 15.1 and has been removed in 16.0. Use the [GitLab for Jira Cloud app](https://docs.gitlab.com/ee/integration/jira/connect-app.html) instead. The Jira DVCS connector was also deprecated for Jira 8.13 and earlier. You can only use the Jira DVCS connector with Jira Data Center or Jira Server in Jira 8.14 and later. Upgrade your Jira instance to Jira 8.14 or later, and reconfigure the Jira integration in your GitLab instance.
If you cannot upgrade your Jira instance in time and are on GitLab self-managed version, we offer a workaround until GitLab 16.6. This breaking change is deployed in GitLab 16.0 behind a feature flag named `jira_dvcs_end_of_life_amnesty`. The flag is disabled by default, but you can ask an administrator to enable the flag at any time. For questions related to this announcement, see the [feedback issue](https://gitlab.com/gitlab-org/gitlab/-/issues/408185).
### License-Check and the Policies tab on the License Compliance page ### License-Check and the Policies tab on the License Compliance page
WARNING: WARNING:
......
0% 加载中 .
You are about to add 0 people to the discussion. Proceed with caution.
先完成此消息的编辑!
想要评论请 注册