### Deprecation Summary Bitbucket Cloud issue and wiki import is deprecated in GitLab 19.1 and will be removed in GitLab 19.5. Atlassian is [sunsetting native Bitbucket Cloud Issues and Wikis](https://community.atlassian.com/forums/Bitbucket-articles/Announcing-sunset-of-Bitbucket-Issues-and-Wikis/ba-p/3193882) on August 20, 2026. The underlying API endpoints will be removed, making it impossible for GitLab to import these items. [Bitbucket Cloud import documentation](https://docs.gitlab.com/ee/user/import/bitbucket_cloud.html) #### Migration guidelines **Before August 20, 2026:** The GitLab Bitbucket Cloud importer continues to import issues and wikis normally. Users should complete any imports that include issues or wikis before this date. **After August 20, 2026:** Atlassian will have removed the Issues and Wikis APIs. The GitLab importer will skip issues and wikis automatically. Users who need their Bitbucket issue data should: - For issues: Export from Bitbucket using [Bitbucket's export tool](https://support.atlassian.com/bitbucket-cloud/docs/export-or-import-issue-data/), then import into GitLab using the [Jira migration options](https://docs.gitlab.com/ee/user/project/import/jira_migration_options.html) or [CSV import](https://docs.gitlab.com/ee/user/project/issues/csv_import.html). - For wikis: Clone the Bitbucket wiki repository locally using [Bitbucket's instructions](https://support.atlassian.com/bitbucket-cloud/docs/clone-a-wiki/). No automated migration is planned. #### Background Atlassian announced on February 18, 2026 that native Bitbucket Cloud Issues and Wikis are being removed. Starting April 2026, these features can no longer be enabled on new repositories. The API endpoints and features will be fully removed on August 20, 2026. This is a third-party dependency change per our [deprecation terminology](https://docs.gitlab.com/update/terminology/#third-party-dependencies). The Bitbucket Cloud importer will continue to import repositories, pull requests, pull request comments, milestones, labels, and LFS objects. ### Breaking Change? Does this deprecation contain a breaking change? `Yes` This breaking change is driven by a third-party dependency removal (Atlassian removing Bitbucket Issues and Wikis APIs) and is outside GitLab's control. Per our [third-party dependency policy](https://docs.gitlab.com/update/terminology/#third-party-dependencies), these changes follow the dependency's own lifecycle. ### Affected Customers Who is affected by this deprecation: GitLab.com users, Self-managed users, or Dedicated users? (choose all that apply) - [x] GitLab.com - [x] Self-managed - [x] Dedicated What pricing tiers are impacted? - [x] GitLab Free - [x] GitLab Premium - [x] GitLab Ultimate ### Deprecation Milestone This deprecation is being announced in milestone: `19.1` ### Planned Removal Milestone The feature / functionality will be removed in milestone: `19.5` #### Rollout Plan - DRI Engineers: `@thiagocsf` - DRI Engineering Manager: TBD - [x] No feature flag needed. The upstream API is being removed by Atlassian. - [ ] Graceful error handling will be added in 19.2/19.3 so the import pipeline continues to work when the API returns errors. - [ ] Dead code removal in 19.5 after confirming Atlassian has completed the API removal. #### Communication Plan - DRI Product Manager: TBD **Internal Communication Plan** No Breaking Change Exception issue filed. This is a third-party dependency change per [our policy](https://internal.gitlab.com/handbook/engineering/r-and-d-pmo/knowledge-base/all-articles/breaking-changes/) and [terminology](https://docs.gitlab.com/update/terminology/#third-party-dependencies). - [ ] Support Preparedness issue created - [ ] Guidance for Engineering, Product, Security, Customer Success, and Sales created **External Communication Plan** - [ ] Customer announcement plan - [ ] Document the migration plan for users, clearly outlining the actions they need to take to mitigate the impact of the breaking change. - [ ] A deprecation announcement entry has been created so the deprecation will appear in release posts and on the general deprecation page. - [ ] Documentation has been updated to mark the feature as deprecated. - [ ] On the removal milestone: - [ ] The deprecated item has been removed. - [ ] If the removal of the deprecated item is a breaking change, the merge request is labeled ~"breaking change". #### Labels - [x] This issue is labeled ~deprecation, and with the relevant `~devops::`, `~group::`, and `~Category:` labels. - [x] This issue is labeled ~"breaking change" if the removal of the deprecated item will be a breaking change.