Announcing sunset of Bitbucket Issues and Wikis

[#1]

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.

[Adam Setch]

Hi Yana

I'm on of the main contributors for Bitbucket Cloud support in Renovate.

We make use of Bitbucket Issues exclusively for Renovate to maintain a Dependency Dashboard for each repository: https://docs.renovatebot.com/key-concepts/dashboard/

As part of the sunset, is there plans to enhance the public Bitbucket REST APIs to support

- retrieve Jira Projects linked to a Bitbucket repository

- create / update jira work item for a Bitbucket repository (via it's associated project)

I believe in the current state these are internal / private endpoints.

Regards

Adam

[Tim Eddelbüttel]

I really loved Bitbucket Issues due to it's simplicity. It was perfect for cases where a Jira project was too much overhead. Having simple issues beside your code (and it might me just an e.g. Ansible Role) is sometimes enough as a reminder, to do list, etc.

Wikis also still have it's use-cases also when static site hosting was never implemented.

Issues and Wikis was one of these differentiators between Bitbucket Data Center. 

From a product point-of-view, all competitors have such features.

[Adam Setch]

related: https://jira.atlassian.com/browse/BCLOUD-22491

[Adam Setch]

Ideally, I'd love to have Bitbucket REST APIs that are in the context of a repository (repo_slug) which allow us to
- Search for existing Jira work items for a repository (filter by work item summary/title and status)
- Create new work items for a repository
- Update existing work item for a repository

This would allow us to refactor the Renovate OSS code to continue generating Dependency Dashboards

One gotcha might be the fact that a Bitbucket Repository can have Jira work items from any Jira projects for the linked Jira site. 

To work around/through this, my thought is that a organizations could have a single Jira Project setup for `Renovate`, and this project id / project key is configured globally in the Renovate CLI.  That would mean that all work items would ultimately reside in the same Jira project, but, when viewed via Bitbucket Cloud's `Jira work items tab`, it would only show those associated to the repository