Announcing sunset of Bitbucket Issues and Wikis

Hello Bitbucket Community,

In continued efforts to improve performance, reliability, and consistency across Atlassian apps, Bitbucket Cloud will be sunsetting native Issues and Wikis features.

This post explains what’s changing, why we’re making this change, and what you need to do if you currently use Bitbucket Issues or Wikis.

What’s changing?

Starting in April 2026, Issues and Wikis will no longer be available to turn on for repositories where these features are not currently used.
Existing Issues and Wikis will be fully sunset and removed from Bitbucket in mid-August, 2026.

Why we’re making this change?

Bitbucket’s native Issues and Wikis are legacy features that have a much better modern alternative with existing Atlassian apps like Jira and Confluence.

By sunsetting these features, Bitbucket will be able to offer a unified experience for our customers for centralized user management and billing, upcoming EU Data Residency, organization context-aware insights powered by Rovo search, Rovo chat and Atlassian Teamwork graph.

What you need to do?

If your team is using Bitbucket repository Issues tracker or Wikis today, we recommend you do the following before August 2026:

Export Bitbucket Issues to preserve them, or migrate them to Jira Software: Export or import issue data | Bitbucket Cloud | Atlassian Support.
Clone Wiki locally to preserve them and migrate the content to Confluence Clone a wiki | Bitbucket Cloud | Atlassian Support.
Benefit from native integration between Bitbucket Cloud and Jira Software Cloud
Connect Bitbucket Cloud to Jira Cloud | Bitbucket Cloud | Atlassian Support. With this integration, your teams can
- View Jira issues directly from Bitbucket repositories.
- See linked branches, commits, pull requests, and build status in Jira Software.
- Continue to keep your team’s work planning and development tightly connected.

How we’ll support you?

We recognize that any change can be disruptive, and we’re committed to making this as smooth as possible. To do this we will:

Provide clear timeline so you can plan export and migration to alternative apps.
Provide a list of repositories where these features are enabled within your workspace, upon request only.
Implement in‑product notices where Issues/Wikis are currently used.
Send direct email communications to workspace admins with feature usage in the last 6 months.
Provide access to help via our Support and Community teams.

Thank you for your partnership.