Move issues from www.drupal.org to git.drupalcode.org

Just curious: if it , what is the purpose in doing it at all ?

It's not just issues, we will also get kanban boards, gitlabci integration and many more features that come out of the box by using gitlab...
Also, the management of issues (and comments) will be in gitlab, which will make drupal.org "lighter" (and faster too?) and we won't need to migrate these to the new version of d.o.

The new credit system has been mostly rebuilt already and is being tested.

I guess there are pros and cons no matter how you look at it tho.

Thanks for the answer. I guess I'm most worried by the issue stats and sparklines going away, as discussed on Slack.

For many years now, these have been amongst the most important indicator to site builders evaluating modules about the state of an extension they envision for their site, and losing those means losing a lot of value for that segment of the Drupal users/evaluators/auditors.