Bitbucket issues and Jira

[Ed McDonagh]

We develop our code using Bitbucket as a central repository, and for automated testing  and recording and working against issues.

Unfortunately, the organisation behind Bitbucket, Atlassian, has decided to enforce use of one of their other products - Jira - and is deprecating the use of Bitbucket issues.

I have therefore started the process of trying to migrate the issues function to Jira. At the present time, I am in a situation where I have closed access to issues (so that there aren't further updates post migration), but Jira is not yet configured correctly.

Please bear with me!

Kind regards

Ed

[Alan Chamberlain]

Hi Ed

When I went into my fork of openrem on BitBucket I received the following message:

Cross workspace forks are being deprecated

This is a repository forked from a different workspace. The parent repository is openrem/openrem. On July 1, 2026, the forking relationship of this repository will be broken. In addition, the ability to create new repository forks will be limited to the same workspace. Pull request functionality for all existing forks, including those to other workspaces, will continue to function as normal. We are making this update to improve reliability, support enterprise controls, and enable data residency. Learn more about this change here.

I'm not sure what this means for the future of open source collaboration on BitBucket, but maybe now is the time to look at an alternative platform.

Regards

Alan

[Ed McDonagh]

Oh why does it have to change all the time!

Thanks for letting us know Alan. With that, and the changes to issues, it really looks like Atlassian want to just cater to the commercial development market. 

Very sadly, I think you might be right that we need to look elsewhere. Having had a quick look, it would seem that GitLab are probably our best bet - we can get their 'ultimate' offering on gitlab.com as an open source project.

Does anyone have any expertise in this? Or want to help with the migration and rebuilding all the continuous integration scripts etc...?

Kind regards

Ed

--
You received this message because you are subscribed to a topic in the Google Groups "OpenREM" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/openrem/euA-dHZb3No/unsubscribe.
To unsubscribe from this group and all its topics, send an email to openrem+u...@googlegroups.com.
To view this discussion, visit https://groups.google.com/d/msgid/openrem/029cdbd7-3835-417f-aa08-e472e18b17dan%40googlegroups.com.