Simplify label management by allow to grant edit access for labels

Feature Discussion
1

At the moment, only the creator of a label may manage its properties, like title, color and description. However, considering a medium sized project with ~10 people, quite a few of which have create labels to aid organizing the project, it becomes quite hard to maintain these – like redoing a consistent color scheme, naming scheme or descriptions for a set of labels used by a team within a project.

The easiest way to solve this would probably be able to allow sharing label management with other users or teams, by which they would obtain the same level of access as the owner.
Also I would suggest that if project labels get implemented at some point (Labels local to a namespace (or even a list), but no gitea/github/roadmap entry seems to exist), each project admin gets full access to the per-project labels.

By the way, what happens to a label when its owner’s account is deleted? I think there is no warning involving labels, and in the code I do not find any event handler for that. Does this just leave unmanagable labels behind? I guess one could in practice get rid of it by replacing it everywhere, but still not quite ideal.

2

I think the best way would be to have labels attached to projects instead of what they’re doing now. That would allow you to manage the labels when you have permission to do things in the project. It would also be simpler as we won’t need to do the whole sharing a label thing.

1 Like
3

To have this option would certainly good, however it also raises other questions regarding how to handle those when moving tasks between projects, or when creating saved filters which filter by label.