Import BugZilla bugs as GitLab Issues

Is there an automatic procedure to do that?

We have not investigated migrating Bugzilla yet. Gnome has a migration tool here, that we will look at first: https://gitlab.gnome.org/federico/bugzilla-to-gitlab-migrator

mentioned in issue eclipse/chess/chess#3 (closed)

added Migration label

assigned to @droy

Based on work from gnome and freedesktop.org: https://gitlab.gnome.org/World/bztogl

I have something running. Witness this ancient bug, with comments and one attachment: https://bugs.eclipse.org/bugs/show_bug.cgi?id=22147

Witness the imported issue: https://gitlab-test.eclipse.org/droy/awesome-sauce/-/issues/10

Noteworthy and caveats:

1. I am not logged into Bugzilla, so there is no 'ping' on the original BZ bug to mention that it has been migrated. The script has provisions for that, so the original bug will have a comment on it. I will test this soon.

2. The Gitlab API key belongs to my user account on the test GL instance. Since the imported issue and all its comments are attributed to the user owning the API key, we'll need to use a Genie or Migration account. Which brings me to 3...

3. Everything is performed as the migration user. I don't think there's a way around this, since these old accounts are not in Gitlab (nor do we necessarily want them to be). I've noticed that, if the migration script detects an existing GL account, they are @cc'd . See the last comment of https://gitlab-test.eclipse.org/droy/awesome-sauce/-/issues/9, which was made by me in 2009.

4. Labels. The migration script creates some labels, like 5. Projectname and "bugzilla". I'll remove the "5." but ... can we think of other labels we'd want?

5. This import won't be picture perfect. But it will provide a mechanism to create issues with comments and attachments from open bugs. I think that's probably 95%+ of what is needed here.

6. Open Bugs only. Closed/Resolved bugs are not migrated. I think we should keep it that way, as it prunes lots of unnecessary baggage from some of the mature projects.

Thoughts?

@webmaster

6. We should migrate closed bugs, too. History of resolved bugs is something I often lookup, and it would be painful and confusing to always switch between BZ and GL.

mentioned in issue #5 (closed)

We'll look at how we can import closed bugs and offer the option to those projects who wish to migrate.

We can import resolved and closed bugs now. The first project to undergo such a migration is the Eclipse Handbook: https://gitlab.eclipse.org/eclipse/dash/org.eclipse.dash.handbook

closed

@droy Could we import resolved and closed bugs for CHESS?

We could; did we import only the open bugs?

reopened

Reopening; importing Resolved/Closed bugs imports them as opened bugs.

Thanks @droy! So now in GitLab we have to close the imported bugs right? Should be possible to import also the open bugs?

I thought we had already. I'll do that now. Yes, indeed, please triage your imported Issues in Gitlab to close those that need to be closed.

Attributing everything to "Eclipse Webmaster" is highly destructive. Since this instance is hosted by the foundation and you have complete access, please try to preserve as much information as possible.

Higher quality import is one of the few benefits self-hosted Gitlab has over Github.

To be clear, an import from Github is of very high quality. Only Bugzilla needs some work.

I do agree that we need to at least try. I'll close this issue since we do have a mechanism, but I'll create a new one for this specific element.

closed

mentioned in issue #30 (closed)

mentioned in issue #55 (closed)

mentioned in issue #1987 (closed)

mentioned in issue #2550 (closed)