Direct Transfer status, dead for too long

Hi all,

we’re in the process of consolidating several self-hosted repositories and some groups from private repos on gitlab.com into one self-hosted instance. Now, we have managed to direct-transfer all groups and projects from self-hosted repos but trying to do the same (prerequisites have been met) does not work on gitlab.com, gives 404.

I see on Gitlab status page that “Migration by direct transfer and importing with GitHub, Bitbucket Server, and Gitea importer is offline”, since June 6. So it is probably the cause. However, no updated have been made on this Service Disruption since June 7 (three weeks ago). I also cannot find any issue in Gitlab source repo that would explain this.

So, what is going on? Is this service going to be fixed/released and when?

I mean, I can always push the local repo into new server, but we want to preserve objects, issues and the whole story. If direct transfer will not be fixed any time soon, what are my options of making a 1-1 copy of the private repo?

Another discussion on this can be found here: Github Import Button Missing - #7 by xdh

Probably better would be to search open issues to see if an issue is open on this, or to open one and find out when the Gitlab Devs will fix it: Issues · GitLab.org / GitLab · GitLab

But yes, the fact it has been down for so long doesn’t look good at all and I don’t know why Gitlab is taking so long to fix it.

I tried searching the Gitlab issues, but couldn’t find anything fresh and related to direct transfers. Maybe I just didn’t use the proper keywords, there are a lot of issues there.

Ok, I’ll just go and create one, I wanted to avoid it as I am not really reporting a new bug or issue, but it is what it is.

At least I got them to update the status.