Label sets don't make sense to a new user #3760

Closed
opened 2025-11-02 05:24:23 -06:00 by GiteaMirror · 4 comments
Owner

Originally created by @Mikaela on GitHub (Aug 10, 2019).

Description

I have recently moved some repositories to Gitea and started using the issue tracker. When I first enter the labels menu, I see the first screenshot.

With the first repository I just created a new label as I assumed that the Label Set means that I am given a single label called "Default" which is not going to help me. With another repository I did accept the Default label set and was surprised that I was given actually useful labels (screenshot 2).

Request: could more information be added between the label set dropdown and the "Use Label Set" button? I wish it would have told me instead something like "This will create 7 labels; bug, duplicate, enhancement, help wanted, invalid, question and wontfix". I think having the label explanations visible wouldn't hurt either, but even without them, just the label names would be more helpful to know.

I am also wondering if I can return to this screen somehow with the repositories where I opted to not use a label set and import a label set regardless.

Screenshots

bildo

bildo


Edit: potentially related https://github.com/go-gitea/gitea/issues/6055 ?

Originally created by @Mikaela on GitHub (Aug 10, 2019). - Gitea version (or commit ref): (gitea.blesmrt.net) 1.9.0 and (try.gitea.io) 1.10.0+dev-154-gcde95f992 - Can you reproduce the bug at https://try.gitea.io: - [x] Yes (provide example URL) - https://try.gitea.io/Mikaela/labeltest/labels - [ ] No - [ ] Not relevant ## Description I have recently moved some repositories to Gitea and started using the issue tracker. When I first enter the labels menu, I see the first screenshot. With the first repository I just created a new label as I assumed that the Label Set means that I am given a single label called "Default" which is not going to help me. With another repository I did accept the Default label set and was surprised that I was given actually useful labels (screenshot 2). Request: could more information be added between the label set dropdown and the "Use Label Set" button? I wish it would have told me instead something like "*This will create 7 labels; bug, duplicate, enhancement, help wanted, invalid, question and wontfix*". I think having the label explanations visible wouldn't hurt either, but even without them, just the label names would be more helpful to know. I am also wondering if I can return to this screen somehow with the repositories where I opted to not use a label set and import a label set regardless. ## Screenshots ![bildo](https://user-images.githubusercontent.com/831184/62823235-bf397d00-bb7e-11e9-980d-fa6b2fe998a9.png) ![bildo](https://user-images.githubusercontent.com/831184/62823269-ff98fb00-bb7e-11e9-8599-6037f4c78c08.png) * * * * * Edit: potentially related https://github.com/go-gitea/gitea/issues/6055 ?
GiteaMirror added the type/enhancementtype/docs labels 2025-11-02 05:24:23 -06:00
Author
Owner

@oscarlofwenhamn commented on GitHub (Aug 12, 2019):

Not a bad idea, maybe simply list underneath the dropdown a list of labels in a set. "This will create 7 labels; bug, duplicate, enhancement, help wanted, invalid, question and wontfix" feels maybe a bit verbose, but simply something like:

| Default |
(bug, duplicate, enhancement, help wanted, invalid, question, wontfix)

or even, if length is an issue:

| Default |
(bug, duplicate, enhancement, +4)

@oscarlofwenhamn commented on GitHub (Aug 12, 2019): Not a bad idea, maybe simply list underneath the dropdown a list of labels in a set. "This will create 7 labels; bug, duplicate, enhancement, help wanted, invalid, question and wontfix" feels maybe a bit verbose, but simply something like: | Default | *(bug, duplicate, enhancement, help wanted, invalid, question, wontfix)* or even, if length is an issue: | Default | *(bug, duplicate, enhancement, +4)*
Author
Owner

@stale[bot] commented on GitHub (Oct 11, 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 (Oct 11, 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.
Author
Owner

@Mikaela commented on GitHub (Oct 11, 2019):

I am able to reproduce at https://try.gitea.io/repo/create.

@Mikaela commented on GitHub (Oct 11, 2019): I am able to reproduce at https://try.gitea.io/repo/create.
Author
Owner

@oscarlofwenhamn commented on GitHub (Oct 11, 2019):

Definately still a relevant issue

@oscarlofwenhamn commented on GitHub (Oct 11, 2019): Definately still a relevant issue
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/gitea#3760