Done: User Dashboard project counts include archived projects, which aren't listed (#374700) · Issues · GitLab.org / GitLab · GitLab. One of 44305 open issues, yikes.
In fact, in the course of reporting I created an example-of-problem project under my own account, as requested, and discovered that the bug affects “Your Projects” as well. So the report expanded a bit.
In an ideal world, perhaps. But since the most common reason for abandoning/archiving a project is “no time” (as was the case here), unless there was a one-click method of doing that, realistically I don’t see that happening. Or if it were an automatic part of the archiving process, I suppose
Well, that project actually was taken over (by Jason Oickle / OpenWeather · GitLab), but that repo was started fresh, not as a fork. Unless the original repo had been transferred over (in which case it wouldn’t be archived), I think having their issues/MRs migrated to some other project without their say-so would upset some users.
And that’s kind of the thing, isn’t it, about the read-only archival?: It breaks the user-controlled model for submitters’ content.
When a project is live, a user who submits an issue or MR is still in control of it. They can choose to close/withdraw it at any time, they can edit the details or push new commits… it’s still their issue, or their MR, despite being in another project.
But archival throws that all out the window, and says, “Sorry, you no longer have any control over this content you created.” (Though, I suppose I could still push to or even delete my project branch associated with the MR, so it’s not a total loss of control.)