Announcing sunset of Bitbucket Issues and Wikis

[padmanabha_kamath]

Not a good move. "Issues" is THE way to track Tech debt related to a repo. It is also empowering for non-dev users of the repo - SDETs, testers, PMs to suggest changes and best practices. Gitlab has this and this is something I have ALWAYS used to track suggestions for improvements and track tech debt - i.e. missing tests, missing features etc. 

How will I communicate things like - this repo needs a Changelog, tests need a separate folder, need to move package a to version x.y.z .... Opening tickets in JIRA, putting it in a backlog, etc. will be giving this to non-technical folks who may not judge the items with the same urgency/consideration.   

[Yana]

Hi @padmanabha_kamath  

There are a few ways you could accomplish that: 

- using Bitbucket readme and link to a Confluence or a Jira project 

- using Jira task tracking 

- integrate your Bitbucket workspace with Jira software and enable Smart Commits

- by assigning Jira work items to individuals, in which case they would be notified by email when a new item is assigned to them. 

Thank you

[tshatrov]

The issues for my repo tshatrov/ichiran-web have completely disappeared. I have been tracking TODO items and had literally hundreds of them. I never received a notification of them being removed and now apparently it's impossible to retrieve them? Makes me really not want to use Atlassian products in the future if one day you're just going to delete hundreds of hours of work in an instant.

[Yana]

@tshatrov 

Hi there, the sunset warning message was implemented in the BB UI across multiple screens for the last 6 months with the message that the feature is going away on August 20, 2026. We wanted to make sure that customers take the time and export the content or migrate before the deadline. 
I'll have our Support team reach out to you to help.

[tshatrov]

@Yana 

1. 6 months is a ridiculously short timeframe for such a drastic decision. ichi.moe releases once a year, usually around New Year's, so I have never seen the announcement of the decision. Only because someone suggested a new feature, and I was about to log it in my Issues, that's how I found that it was removed.

2. Putting it on multiple screens assumes I visit the website when it's not time to prepare a new release. Instead you should've been sending me an email every day since I was about to lose so much work. Instead there were zero (0) emails from Atlassian in this time period.

[Yana]

@tshatrov 

Apologies that you had missed the announcement. 

We used multiple notification channels: 

- direct email to all Admins of workspaces where features are being used

- persistent UI messaging across multiple relevant Bitbucket screens 

- API announcements and relevant response messages

[tshatrov]

@Yana 

Direct email (singular)? That's very easy to miss among all the promo emails coming from Atlassian every day. That email was on Mar 25. Why hasn't there been an email sent close to the deadline, especially to the users who are affected by the deadline, such as the ones who have hundreds of issues logged, like me? I have honestly never seen such an incompetent sunsetting of a feature and I have been a user of Google Reader.

[Alan Gray]

@tshatrov Agree - very poor. It has cost me a lot of time I did not really have free in the last few months but moving to GitHub has been a good step. I will not be recommending Atlassian to anyone after this.