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

[Mark Fortner]

How will this affect the costs of our projects?

[noahk]

Since there is no simple interface to actually list which projects have the Wiki/Issues enabled (no, I'm not bothering a support person for this when it should be automatic) I prepared a PowerShell snippet to list repo information, including which projects have these now-deprecated features enabled.

Here's the code:

https://gist.github.com/xenago/c684e74e4eed652d586fdff3e0dde731

And here's a direct copy (replace ORGNAMEHERE in the $url variable with your namespace, and email@domain.com:apikey in the $creds variable with your credentials - output is repos.csv in homedir).

& {
  $creds = "email@domain.com:apikey"
  $url = "https://api.bitbucket.org/2.0/repositories/ORGNAMEHERE?pagelen=100"
  $all = @()
  do {
    $r = curl.exe -s -X GET --user $creds $url | ConvertFrom-Json
    $all += $r.values | Select-Object name, slug, language, updated_on, has_wiki, has_issues,
      @{N="project"; E={$_.project.name}},
      @{N="url"; E={$_.links.html.href}}
    $url = $r.next
  } while ($url)
  $all | Export-Csv -Path "$HOME\repos.csv" -NoTypeInformation
}

[Di Zou]

Are you all actively trying to push people to GitHub or what?

[Roman Haag]

thanks for inspiration. made a bash script similar to it (runs on mac/linux):
https://gist.github.com/thetoaster/156aa77c53bdf98a585a0d006278c559

[Eyke]

very sad. can someone recommend a simple path to migrate repo issues to github?

[Yatish Madhav]

Thanks for this @Yana  - i have never used wiki or issues in BB. TBH havent use BB much either but as we are moving towards merging Gitlab and BB (not sure to which one), this seems helpful.

I also, as admin searched and made use of this by Rob Williams https://bitbucket.org/rwillia2/bitbucket-scan/src/main/ - it helped check if we are impacted or not. Thanks @Roman Haag  too - saw that one before the comments :)

Thanks

[Yana]

@Adam Setch 

There is no immediate solution that exists today to accommodate your request, I have created a feature request for it to track customers interest: 

https://jira.atlassian.com/browse/BCLOUD-24056

encourage you to vote for it. 

Thank you

[Yana]

@Mark Fortner 

There is no change to cost and if you are new to Jira, you can get a Jira instance free for up to 10 users. 

https://www.atlassian.com/software/free

[Ovidiu Gabriel]

@Yana this is not good. It's the 3rd big mistake that Atlassian made in the last year.

I think this decision is pushing people to GitHub. I don't understand why you want to do this.

I like Atlassian Issues, it is a perfectly fine system and I don't like JIRA, it's too complex for my needs.

[Friedrich Müller]

Hello,

@Yana , @all

i don't get it - what issue tracker and wiki you are talking about?

Will this be affected of this announcement?:

https://bitbucket.org/geowerkstatt-hamburg/masterportal/issues?status=new&status=open&status=submitted&is_spam=!spam 

https://bitbucket.org/geowerkstatt-hamburg/masterportal/wiki/Home 

Thanks,

[Yana]

Hi @Friedrich Müller 

Yes, those are the features that are being sunset and will be fully removed from Bitbucket on August 20, 2026. 

[Yana]

@Ovidiu Gabriel 

Thank you for your feedback. We know changes like this are hard. We’re retiring Bitbucket Issues and Wikis to improve reliability and bring Bitbucket onto Atlassian platform. This means offering unified billing and user management, and including Bitbucket data in Rovo.  I understand Jira can feel complex, but small teams can use it for free (up to 10 users), and we offer migration tools to make the move as smooth as possible.

[Eyke]

Are there any special plans for open source projects or do you simply prefer them to leave ?

[Yana]

@Eyke 

Thank you for your question. With open source, you can still have your repositories set to public and with Jira you can enable Public forms to allow users to submit a feature request that then is turned into a Jira work Item, please see more details here: 

https://support.atlassian.com/jira-software-cloud/docs/share-your-form/

This feature is available in all Jira plans: 

https://www.atlassian.com/software/jira/pricing

[Friedrich Müller]

@Yana Thanks for your reply. These are no good news for our project. Issue tracker and Wiki are both key features in our work process. 😪

[Eyke]

I am confused. A feature request is something different than an issue tracker. For example for cpython there are 68k issues with deep technical discussions, see https://github.com/python/cpython/issues

Is this compatible with your plans? 

[marat]

That's really decrease the value of this service. 

[Brian Bucklew]

Ditching features because of your billing system is not a good idea. Nobody is paying you for your billing system.

Maybe eventually you can get rid of all your features an have only a billing system. The ultimate profit center!