[Feature Request] Milestone Labels #7941

New Issue

GiteaMirror · 2025-11-02T07:42:18-06:00

GiteaMirror commented

2025-11-02 07:42:18 -06:00

Originally created by @chriseaton on GitHub (Oct 7, 2021).

Originally assigned to: @techknowlogick, @TKDev7 on GitHub.

Feature Description

I think it would be super helpful for milestones (and the associated APIs) to support labels. They help quite a bit organizing issues, and on large projects it would be nice to be able to categorize the milestones as well.

Right now in our projects we have to resort to using special keywords in the titles which isn't super-efficient or clear like you see with the labels in issues.

Screenshots

1. Labels could appear below the description in the milestone listing.

2. Leverage the same type of dropdown when creating/editing, just show labels in a horizontal stack.

)

3. Bonus ask: Would probably also be good to see (likely not edit) the milestone labels on any assigned issue.

.

Originally created by @chriseaton on GitHub (Oct 7, 2021). Originally assigned to: @techknowlogick, @TKDev7 on GitHub. ### Feature Description I think it would be super helpful for milestones (and the associated APIs) to support labels. They help quite a bit organizing issues, and on large projects it would be nice to be able to categorize the milestones as well. Right now in our projects we have to resort to using special keywords in the titles which isn't super-efficient or clear like you see with the labels in issues. ### Screenshots **1.** Labels could appear below the description in the milestone listing. ![Screenshot](https://user-images.githubusercontent.com/5247568/136300292-c8840bea-a7b7-4547-998e-b2dcffdffdbc.png) **2.** Leverage the same type of dropdown when creating/editing, just show labels in a horizontal stack. ![Screenshot2](https://user-images.githubusercontent.com/5247568/136300238-7f7ac5d1-f6ed-4bb8-9b97-4347a5e3655a.png) ) **3.** Bonus ask: Would probably also be good to *see* (likely not edit) the milestone labels on any assigned issue. ![Screenshot3](https://user-images.githubusercontent.com/5247568/136302063-9c56edb1-9870-47f5-aad1-6c717c10debe.png) .

GiteaMirror added the type/proposal proposal/accepted labels 2025-11-02 07:42:18 -06:00

GiteaMirror commented

2025-11-02 07:42:19 -06:00

@chriseaton commented on GitHub (Oct 7, 2021):

APIs that would need to be created to support milestone labels (if following the same convention as issues):

GET /repos/{owner}/{repo}/milestones/{id}/labels Get an milestones's labels
PUT /repos/{owner}/{repo}/milestones/{id}/labels -Replace an issue's labels
POST /repos/{owner}/{repo}/milestones/{id}/labels Add a label to an issue
DELETE /repos/{owner}/{repo}/milestones/{id}/labels Remove all labels from an issue
DELETE /repos/{owner}/{repo}/milestones/{id}/labels/{id} Remove a label from an issue

An {id} would be given for the milestone as it doesn't have an index like issues. If you wanted use an index you would also have to update the following to provide them:

GET /repos/{owner}/{repo}/milestones Get all of a repository's opened milestones

@chriseaton commented on GitHub (Oct 7, 2021): APIs that would need to be created to support milestone labels (if following the same convention as issues): - GET `/repos/{owner}/{repo}/milestones/{id}/labels` Get an milestones's labels - PUT `/repos/{owner}/{repo}/milestones/{id}/labels` -Replace an issue's labels - POST `/repos/{owner}/{repo}/milestones/{id}/labels` Add a label to an issue - DELETE `/repos/{owner}/{repo}/milestones/{id}/labels` Remove all labels from an issue - DELETE `/repos/{owner}/{repo}/milestones/{id}/labels/{id}` Remove a label from an issue An {id} would be given for the milestone as it doesn't have an index like issues. If you wanted use an index you would also have to update the following to provide them: - GET `/repos/{owner}/{repo}/milestones` Get all of a repository's opened milestones

GiteaMirror commented

2025-11-02 07:42:19 -06:00

@chriseaton commented on GitHub (Oct 8, 2021):

My employer would love this feature and has posted a bounty on it if you are interested.

@chriseaton commented on GitHub (Oct 8, 2021): My employer would love this feature and has [posted a bounty on it if you are interested](https://www.bountysource.com/issues/102795591-feature-request-milestone-labels).

GiteaMirror commented

2025-11-02 07:42:20 -06:00

@techknowlogick commented on GitHub (Oct 8, 2021):

@chriseaton whoa, that's huge!! I will get started on this PR right away. Thank you for funding open source development <3

@techknowlogick commented on GitHub (Oct 8, 2021): @chriseaton whoa, that's huge!! I will get started on this PR right away. Thank you for funding open source development <3

GiteaMirror commented

2025-11-02 07:42:20 -06:00

@TKDev7 commented on GitHub (Dec 29, 2021):

@chriseaton Can I work on this?

@TKDev7 commented on GitHub (Dec 29, 2021): @chriseaton Can I work on this?

GiteaMirror commented

2025-11-02 07:42:20 -06:00

@chriseaton commented on GitHub (Dec 29, 2021):

@chriseaton Can I work on this?

it's open-source, anyone can!

@chriseaton commented on GitHub (Dec 29, 2021): > @chriseaton Can I work on this? it's open-source, anyone can!

GiteaMirror commented

2025-11-02 07:42:20 -06:00

@eduardbeutel commented on GitHub (Apr 12, 2022):

Hi, I am interested in implementing this feature and would like to clarify some finer points with @chriseaton and the gitea developers @lunny:

New entity MilestoneLabel or mixed-use Label ?

My question is if we want A: to implement a new/second MilestoneLabel entity to hold the labels for milestones or B: reuse the existing Label entity to hold both issue and milestone labels. Solution A would have the consequence of having to develop a new user interface admin "area" for the new MilestoneLabel.

Label.Type ?

If B is the preferred solution then do we want to add a new property Label.Type = Issue|Milestone to the Label entity for differentiation? If we don't, when applying labels to a new milestone (as seen in screenshot 2) the dropdown list will also contain the labels used for issues.

Best regards,
Eduard

@eduardbeutel commented on GitHub (Apr 12, 2022): Hi, I am interested in implementing this feature and would like to clarify some finer points with @chriseaton and the gitea developers @lunny: 1. New entity MilestoneLabel or mixed-use Label ? My question is if we want A: to implement a new/second MilestoneLabel entity to hold the labels for milestones or B: reuse the existing Label entity to hold both issue and milestone labels. Solution A would have the consequence of having to develop a new user interface admin "area" for the new MilestoneLabel. 2. Label.Type ? If B is the preferred solution then do we want to add a new property Label.Type = Issue|Milestone to the Label entity for differentiation? If we don't, when applying labels to a new milestone (as seen in screenshot 2) the dropdown list will also contain the labels used for issues. Best regards, Eduard

GiteaMirror commented

2025-11-02 07:42:21 -06:00

@techknowlogick commented on GitHub (Apr 12, 2022):

Same labels for both milestones and issues, you can see my linked PR above for how I was able to achieve that

@techknowlogick commented on GitHub (Apr 12, 2022): Same labels for both milestones and issues, you can see my linked PR above for how I was able to achieve that

GiteaMirror commented

2025-11-02 07:42:21 -06:00

@bryanpedini commented on GitHub (Jul 20, 2022):

how I was able to achieve that

Is this FR still considered and WIP?
Thanks!

@bryanpedini commented on GitHub (Jul 20, 2022): > how I was able to achieve that Is this FR still considered and WIP? Thanks!

GiteaMirror commented

2025-11-02 07:42:21 -06:00

@eduardbeutel commented on GitHub (Jul 25, 2022):

@bryanpedini Hi, I'm not part of the project team here but regarding WIP I wasn't able to dedicate the time to implement the feature, so feel free to have a go at it.

@eduardbeutel commented on GitHub (Jul 25, 2022): @bryanpedini Hi, I'm not part of the project team here but regarding WIP I wasn't able to dedicate the time to implement the feature, so feel free to have a go at it.

GiteaMirror commented

2025-11-02 07:42:21 -06:00

@bryanpedini commented on GitHub (Jul 25, 2022):

@eduardbeutel I quoted @techknowlogick's message since they referred to their linked PR, not yours 😅

PS: I'm by no means a Go expert, only a couple of lines of code put here and there, so I can't really talk about implementing stuff in a project big as Gitea, tho as one can grasp by my previous question, I'm very much interested in this feature :)

@bryanpedini commented on GitHub (Jul 25, 2022): @eduardbeutel I quoted @techknowlogick's message since they referred to their linked PR, not yours 😅 PS: I'm by no means a Go expert, only a couple of lines of code put here and there, so I can't really talk about implementing stuff in a project big as Gitea, tho as one can grasp by my previous question, I'm very much interested in this feature :)

GiteaMirror commented

2025-11-02 07:42:21 -06:00

@maxbol commented on GitHub (Jul 29, 2022):

I'd gladly have a look at this

@maxbol commented on GitHub (Jul 29, 2022): I'd gladly have a look at this

Sign in to join this conversation.

Branches Tags

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/gitea#7941