Announcing sunset of Bitbucket Issues and Wikis

[barried]

We were already considering moving to Github for awhile now (since it has pages which is much nicer than paying for a 3rd party like readthedocs, and we already pay for github copilot which is better than Rovo for reviews); I guess this just forces us to relocate to github repos sooner.  It is a shame to see the end of Atlassian.

[Campbell Brown]

Will we lose images that we've attached to Bitbucket issues? E.g. https://bitbucket.org/repo/XYZ/images/foo.PNG

[Gonzalo_AC3E]

I received the email about this change a month ago, and I’m genuinely disappointed by it. Wikis were an important feature of Bitbucket repositories for me, and now we will need to seek other services to host that information online.

The issue tracker was also a simple and effective way to organize our development projects, so its removal will be a loss for me as well.

I wonder whether there will be any reduction in Bitbucket pricing to reflect the diminished service offering. Instead, Atlassian will likely charge us again if we migrate this information to Confluence or Jira to keep it available online in the future.

I now have a strong reason to ask my company to move to another repository service, especially since younger colleagues already ask why we use Bitbucket in the first place.

It is unfortunate when companies acquire another business only to gradually eliminate the valuable features that made the original service worthwhile in the first place.

[Yana]

 @aldocaruso 

There is no automatic tool to migrate Wiki to Confluence. 

Since Wikis are just pages, you will need to copy the content and paste into a new Confluence page, organizing them in any format you see fit. 

After that you can create a Readme file in your BB repo https://support.atlassian.com/bitbucket-cloud/docs/readme-content/ 

that will contain a link to a Confluence page relevant to the repo for updates. The Confluence editor is designed for collaboration, so your users will then use that to make changes vs their local pages. You will just need to make sure you grant them access. Please review this document for managing permissions: https://www.atlassian.com/software/confluence/resources/guides/get-started/manage-permissions#set-up-and-manage-space-permissions 

Thank you 

[Yana]

@Campbell Brown 

You can export the issues to preserve them in JSON format. 

With the export functionality or migration to Jira the images attached to issues are not preserved, only their original name is with the URL.  

To preserve images, you will need to download them and re-upload to either Jira or keep locally for backup.

[Eyke]

Can you please add a path to export the images from issues as well?

[Campbell Brown]

A while ago we used the Bitbucket-to-Jira migration tool, but it didn't work very well. It failed often, and when it did eventually work it skipped issues, it didn't preserve issue formatting, and it excluded attachments and images. I am not sure if the tool has been made more reliable since then, but to avoid frustration and wasting time, we developed our own migration tool in Python.

We also developed a tool to save all issues as static HTML, for those who don't want to migrate to Jira but want to keep their issues for reference.

We can make these scripts open source if others are interested.

[Eyke]

@Campbell Brown  yes please :)

[vovarpd]

Bad decision. You should improve your billing, but not drop the existing features )

I used Wiki & Issues, because it was really great (simple to use) on small projects.

JIRA is way too complex.  I will consider other solutions.

[Alan Gray]

I feel like I am getting dragged into a swamp quite frankly!

1) Bitbucket issues was simple and worked well for the small projects (1-3 people) that I am working on. So having it suddenly sent into the sunset was a bit of a pain. More time wasted on something outside my control.

2) Just spent hours and hours learning about Jira. Seems OK - will take me some more time to get used to the jargon - Epics, Stories, Spaces, etc along with cluttered interface that can be quite confusing when changes don't seem to happen like you expect. Perhaps I can get used to it - others must have.

3) OK, I will try to copy a bunch of issues from a repo (qty 51). Migrate or Export? AI suggests export is a more complete and safe way. Exports OK to ZIP file. Was expecting CSV somewhere but JSON and attachments folder. Looks reasonable.

4) Import into Jira. OH-OH - Bitbucket is not listed in the new import - DUH. Switch to old way - NO that is expecting CSV. AI finally admits that the Export-Import is not feasible - GREAT!!

5) Migrate then. Process seems simple. Succeeded with 354 warnings. Not able to download the log file for some reason - wonderful!! Now I realise that all my comments are there OK but comments from the other user have been dropped. Also there are no attachments. Well that means the migration is basically useless.

6) I add the other user (I assume that sends him an invitation - the system didn't seem to say that). Turns out that it did. Yes - he is now listed in my Jira Space. I'll delete the useless/half migrated Jira Space and try again.

7) OH NO YOU WON'T!!! Now I cannot RE-MIGRATE the issues from BitBucket. It keeps offering to take me to the Jira project which no longer exists. What on earth do I do now?

- Undelete in Jira (apparently I have 30 days)

- Wait until it fully deletes and then hope I can re-migrate

- Re-import into BitBucket from my export file I did

- Try re-importing into another repo and then migrate from that

- Document my woes to warn others (that I can do!)

[Campbell Brown]

Our custom migration tools (to a Jira site or a static HTML site) are available in this repository: https://github.com/bduncanltd/bitbucket-issues-migration
These tools were generated with AI assistance. Review the configuration and mappings carefully before running against a production Jira project, and use at your own risk. I hope this helps others!

[Alan Gray]

That looks quite a lot better than the half-hearted attempt from Atlassian to support long-time users @Campbell Brown - well done!! 

Thanks to assistance from AI, I did manage to "re-migrate" using their process but that still leaves the issue of users and attachments which you have handled much better as well as the concept of mapping a number of properties which looks to be very useful.

Given that a Jira "Space" is essentially a "Project", I would like to move BitBucket repository issues to a Jira "Epic" so that I have multiple "Epics" within a single "Space". This would better align with how I currently have my BitBucket repositories arranged within Projects and Workspaces.

What would be the best way to do this?

[Atiq]

"git clone repo/wiki" on bitbucket is broken. I am able to clone the repo but not able clone repo/wiki. Broken for both git/ssh and HTTPS access (and with scoped API keys).

Please check. This is blocking the migration of wikis that has a sunset deadline on May 15th.

@Yana  please check

[Yana]

@Atiq 

I tested the Wiki clone with SSH, everything seems to be working for me. If you are having issues, please either submit a support ticket, or create a new Community post asking for help and our Community support team will help you get this sorted. 

To clarify, we added UI messaging for Issues and Wikis stating the removal date as August 20, 2026.  You will have access to both features until August 20, 2026, we are not removing them before that date. Thank you

[Atiq]

Hi Yana, 
Ben provided some updated instructions here: https://community.atlassian.com/forums/Bitbucket-questions/Which-scope-I-need-to-clone-a-repository-s-wiki/qaq-p/2427821#M124638

After following that, it's working. Thank you for taking care of it.