Adam Rouman Atlassian Team

Thank you to everyone who has engaged with this post so far. Based on the feedback we have received, I wanted to provide a clear update (also pinned to the top of this post) on what is happening with forked repositories to other workspaces: This post/update only applies to cross workspace forked repositories. Forked…

Hi Everyone, Thanks for the feedback. We understand this is an adjustment to your development processes. Therefore, we wanted to let you know we are listening and will have more updates to share in January. This will include additional details about your options for managing existing cross workspace forks and the timeline…

Hi Folks - there are some great questions here that I will do my best to answer: Q: Why am I seeing this message on my fork that is in the same workspace? A: We initially wanted to give all users who rely on forking workflows advanced notice of the upcoming changes. Only forks to other workspaces are in scope. Based on the…

Hi Deo - I recommend choosing * Security Concern* Security Incident From here you can copy/paste the issue/context and should get you to the right folks ASAP.

Hi there - I'm a product manager with the Bitbucket team. I understand your situation. I recommend filing a support ticket as soon as possible here https://support.atlassian.com/contact/#/ so we can triage your request to the best support team and provide the information you mentioned so we figure out next steps. Thanks,…

@Jim - As Mary said, we're sorry that you have not been able to check out Team Central yet. This is our fault, but rest assured, we're actively triaging this bug and figuring out a way to resolve it soon. Thanks for your patience.