Milestone should have an Index field #128

Closed
opened 2025-11-02 03:10:04 -06:00 by GiteaMirror · 2 comments
Owner

Originally created by @rymai on GitHub (Dec 16, 2016).

Description

In order to be 100% GitHub-compatible, Milestone should have an Index field (it currently only has ID: https://github.com/go-gitea/gitea/blob/master/models/issue.go#L1366), similarly to Issue: https://github.com/go-gitea/gitea/blob/master/models/issue.go#L36.

This Index field should then be exposed as number in the Milestone API format.

Reference:

--- Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/40132826-milestone-should-have-an-index-field?utm_campaign=plugin&utm_content=tracker%2F47456670&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F47456670&utm_medium=issues&utm_source=github).
Originally created by @rymai on GitHub (Dec 16, 2016). ## Description In order to be 100% GitHub-compatible, Milestone should have an `Index` field (it currently only has `ID`: https://github.com/go-gitea/gitea/blob/master/models/issue.go#L1366), similarly to Issue: https://github.com/go-gitea/gitea/blob/master/models/issue.go#L36. This `Index` field should then be exposed as `number` in the [Milestone API format](https://github.com/go-gitea/gitea/blob/master/models/issue.go#L1434-L1450). Reference: - GitHub milestone API: https://developer.github.com/v3/issues/milestones/#get-a-single-milestone <bountysource-plugin> --- Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/40132826-milestone-should-have-an-index-field?utm_campaign=plugin&utm_content=tracker%2F47456670&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F47456670&utm_medium=issues&utm_source=github). </bountysource-plugin>
GiteaMirror added the type/enhancementissue/stale labels 2025-11-02 03:10:04 -06:00
Author
Owner

@stale[bot] commented on GitHub (Feb 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 (Feb 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

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

This issue has been automatically closed because of inactivity. You can re-open it if needed.

@stale[bot] commented on GitHub (Feb 25, 2019): This issue has been automatically closed because of inactivity. You can re-open it if needed.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/gitea#128