Global system to manage "labels" #1028

New Issue

GiteaMirror · 2025-11-02T03:45:50-06:00

GiteaMirror commented

2025-11-02 03:45:50 -06:00

Originally created by @lcges on GitHub (Aug 31, 2017).

Hello.
My suggestion is to add to your account the ability to create labels.
Now there is poor control over labels, should be more control.
This will make it easier to work with future projects in Gitea. This will make it easier to manage the color of your labels. It will also make it easier to keep your label in order.

Originally created by @lcges on GitHub (Aug 31, 2017). Hello. My suggestion is to add to your account the ability to create labels. Now there is poor control over labels, should be more control. This will make it easier to work with future projects in Gitea. This will make it easier to manage the color of your labels. It will also make it easier to keep your label in order.

GiteaMirror added the type/feature issue/confirmed labels 2025-11-02 03:45:50 -06:00

GiteaMirror closed this issue

2025-11-02 03:45:50 -06:00

GiteaMirror commented

2025-11-02 03:45:51 -06:00

@lafriks commented on GitHub (Aug 31, 2017):

You can already add additional system-wide predefined label sets in custom directory

@lafriks commented on GitHub (Aug 31, 2017): You can already add additional system-wide predefined label sets in custom directory

GiteaMirror commented

2025-11-02 03:45:51 -06:00

@lcges commented on GitHub (Aug 31, 2017):

I know, but there is little control over it.
How to add your own labels?

@lcges commented on GitHub (Aug 31, 2017): I know, but there is little control over it. How to add your own labels?

GiteaMirror commented

2025-11-02 03:45:51 -06:00

@lafriks commented on GitHub (Aug 31, 2017):

You can add additional labels one by one in repository

@lafriks commented on GitHub (Aug 31, 2017): You can add additional labels one by one in repository

GiteaMirror commented

2025-11-02 03:45:52 -06:00

@lcges commented on GitHub (Aug 31, 2017):

I know exactly. But I'm about to have the option to change all the labels in one place.
For example, I want to synchronize several projects. I do not have to enter them one by one, just do it globally.

@lcges commented on GitHub (Aug 31, 2017): I know exactly. But I'm about to have the option to change all the labels in one place. For example, I want to synchronize several projects. I do not have to enter them one by one, just do it globally.

GiteaMirror commented

2025-11-02 03:45:52 -06:00

@kifirkin commented on GitHub (Aug 31, 2017):

It's a good idea to manage organisation-wide label set somewhere inside org interface.
the main purpose of this not to initialise predefined label set, but bulk edit it inside of many repositories

@kifirkin commented on GitHub (Aug 31, 2017): It's a good idea to manage organisation-wide label set somewhere inside org interface. the main purpose of this not to initialise predefined label set, but bulk edit it inside of many repositories

GiteaMirror commented

2025-11-02 03:45:52 -06:00

@lafriks commented on GitHub (Aug 31, 2017):

sure, it just was not clear what exactly you wanted that's why I asked 👍

@lafriks commented on GitHub (Aug 31, 2017): sure, it just was not clear what exactly you wanted that's why I asked 👍

GiteaMirror commented

2025-11-02 03:45:52 -06:00

@lcges commented on GitHub (Aug 31, 2017):

cool.
I will try to draft next week

@lcges commented on GitHub (Aug 31, 2017): cool. I will try to draft next week

GiteaMirror commented

2025-11-02 03:45:52 -06:00

@lunny commented on GitHub (Sep 1, 2017):

organisation-wide labels maybe usable.

@lunny commented on GitHub (Sep 1, 2017): organisation-wide labels maybe usable.

GiteaMirror commented

2025-11-02 03:45:52 -06:00

@xak2000 commented on GitHub (Feb 8, 2018):

Also org-wide labels feature is usable because you can filter issues from several projects using these labels.

For example you want to concentrate on bugs now, and you don't care what project these bugs belong. These projects are related anyway. So you just click on Bug label and voila - you have all issues from all projects of selected org, labeled with this label, on one screen!

Or you have some subsystem (module) which span several projects in your org. You create a label for it and assign this label to all issues realted to this functionality. Then when you want to see all issues for this functionality (no matter what project they from) - voila.

@xak2000 commented on GitHub (Feb 8, 2018): Also org-wide labels feature is usable because you can filter issues from several projects using these labels. For example you want to concentrate on bugs now, and you don't care what project these bugs belong. These projects are related anyway. So you just click on `Bug` label and voila - you have all issues from all projects of selected org, labeled with this label, on one screen! Or you have some subsystem (module) which span several projects in your org. You create a label for it and assign this label to all issues realted to this functionality. Then when you want to see all issues for this functionality (no matter what project they from) - voila.

GiteaMirror commented

2025-11-02 03:45:53 -06:00

@stale[bot] commented on GitHub (Feb 8, 2019):

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions.

@stale[bot] commented on GitHub (Feb 8, 2019): This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions.

GiteaMirror commented

2025-11-02 03:45:53 -06:00

@mrsdizzie commented on GitHub (Sep 7, 2020):

There are organization wide labels in Gitea now

@mrsdizzie commented on GitHub (Sep 7, 2020): There are organization wide labels in Gitea now

GiteaMirror referenced this issue

2025-11-02 11:53:01 -06:00

[PR #1028] [CLOSED] Added back unmerged update command on #1006 #15718

GiteaMirror referenced this issue

2025-11-02 11:53:02 -06:00

[PR #1030] [MERGED] Move push update to post-receive and protected branch check to pre-receive #15719

Sign in to join this conversation.