Issue Labels Unnecessarily Copied to Projects On Project Transfer

Description of the problem

I recently created a sub-group called open-source under my top-level group called hyper-expanse.

Upon creating the sub-group I proceeded to migrate all JavaScript projects from the hyper-expanse group to the open-source sub-group.

The top-level group has the following labels (the screenshot is only a few of the labels that are available in that group):

Screenshot_20180622_195456

When I migrated the semantic-release-gitlab project, all labels associated with issues, or merge requests, on that project were copied into project labels.

Therefore, the project now has the following project-level labels:

Screenshot_20180622_201413

Since semantic-release-gitlab is in a sub-group under the hyper-expanse top-level group, semantic-release-gitlab has access to the labels under hyper-expanse, making the project-level labels unnecessary.

To correct the issue I now have to go through each project under the open-source sub-group, delete their project-level labels, and then re-label all issues and merge requests with the hyper-expanse group labels.

So in summary:

  • Creating project-level labels when moving a project into a sub-group is unnecessary.
  • Is there a way to correct the duplication without needing to delete project-level labels, and then re-label all issues and merge requests?

Which Group/Project (with full path) is experiencing the issue?

https://gitlab.com/hyper-expanse/open-source

Approximate date/time when the error occurred.

June 15th is when I believe I created the open-source sub-group.

Edited by Ghost User