Retiring Phabricator - Migrating tasks to Gitlab
david.hurka at mailbox.org
Tue May 23 14:28:30 BST 2023
> > Also, in Phabricator, Tasks have no real "home"; they just have project
> > tags, and they can have multiple such tags to be able to belong to
> > multiple projects. For example "VDG" and also "Plasma". Such a Task
> > shows up in both projects' workboards. But in GitLab, Issues need to
> > live in one place and only one place. So for such Phab tasks, we would
> > need a way to determine the single new home of the Task in GitLab, and
> > perhaps tag them with global-scope labels or something?
> Yes, we would need to do a deconflicting process there.
> Any thoughts on the best approach to that?
> The simplest would be to consider some projects to be the natural "home"
> for tasks (likely the app in question) while meta groups (such as VDG /
> Windows / Flatpak / etc) would only get a task if it was the only project
> on a task.
For Phabricator tasks or Bugzilla tickets, it is obvious how to move them to another issue.
Their numbers are also counted globally.
I learned that it is also not difficult to move issues in Gitlab:
More information about the kde-devel