Introduction of burndown charts on milestones #4927

New Issue

GiteaMirror · 2025-11-02T06:07:49-06:00

GiteaMirror commented

2025-11-02 06:07:49 -06:00

Originally created by @JaneX8 on GitHub (Feb 24, 2020).

As just requested at https://github.com/gogs/gogs/issues/5938. I suppose this feature request applies to both Gogs and Gitea. Maybe one or both teams could work out some solution that fits both projects, as they are quite similar. Saving some time.

Describe the feature
Having a more details view of progress, planning of tasks under a milestone using Burndown charts.

Describe the solution you'd like
Burndown charts. It should be easy to implement as Gitea currently already has Milestone support with a due date, issues can already be linked to Milestones. It is only a matter of adding a "start date" on the milestone. Then you can draw two lines in a chart with the dates from start-date to end-date on the x-axis and the amount of open issues on the y-axis. The lines would be as follows:

one line with an "expected progress" line straight down from number of issues (left) to 0 (right)
one line with the "actual progress" line with open issues per date

The following screenshot illustrates this feature in Gitlab.com:

Describe alternatives you've considered
Using another tool entirely or partially for this functionality.

Additional context
The Line charts from the open-source project chartsjs (or any other chart library) could be used for this. https://www.chartjs.org/docs/latest/charts/line.html

Firstly, the introduction of this simple feature would be a major benefit. Secondly, an additional feature and chart could be introduced which requires a bit more of work. It could be adding "issue weight" on every issue and calculating not only the burndown of total issues but the apply the weight. Gitlab.com can be used as an example of this feature. Also see the image above in which there are two buttons above the chart: issues and issue weight. The weight should be optional on issues and without a weight defined I'd suggest to weight it simply as 1.

Originally created by @JaneX8 on GitHub (Feb 24, 2020). _As just requested at https://github.com/gogs/gogs/issues/5938. I suppose this feature request applies to both Gogs and Gitea. Maybe one or both teams could work out some solution that fits both projects, as they are quite similar. Saving some time._ **Describe the feature** Having a more details view of progress, planning of tasks under a milestone using Burndown charts. **Describe the solution you'd like** Burndown charts. It should be easy to implement as Gitea currently already has Milestone support with a due date, issues can already be linked to Milestones. It is only a matter of adding a "start date" on the milestone. Then you can draw two lines in a chart with the dates from start-date to end-date on the x-axis and the amount of open issues on the y-axis. The lines would be as follows: - one line with an "expected progress" line straight down from **number of issues** (left) to 0 (right) - one line with the "actual progress" line with open issues per date The following screenshot illustrates this feature in Gitlab.com: ![image](https://user-images.githubusercontent.com/5116641/75143422-4e5e4a80-56f5-11ea-8eb3-aff275aeb1d3.png) **Describe alternatives you've considered** Using another tool entirely or partially for this functionality. **Additional context** The Line charts from the open-source project chartsjs (or any other chart library) could be used for this. https://www.chartjs.org/docs/latest/charts/line.html _Firstly, the introduction of this simple feature would be a major benefit. Secondly, an additional feature and chart could be introduced which requires a bit more of work. It could be adding "issue weight" on every issue and calculating not only the burndown of total issues but the apply the weight. Gitlab.com can be used as an example of this feature. Also see the image above in which there are two buttons above the chart: issues and issue weight. The weight should be optional on issues and without a weight defined I'd suggest to weight it simply as 1._

GiteaMirror added the type/proposal label 2025-11-02 06:07:49 -06:00

GiteaMirror commented

2025-11-02 06:07:50 -06:00

@joa77 commented on GitHub (Apr 4, 2023):

Any news on this feature?

@joa77 commented on GitHub (Apr 4, 2023): Any news on this feature?

GiteaMirror commented

2025-11-02 06:07:50 -06:00

@kantholy commented on GitHub (Dec 6, 2023):

I really would like to see this implemented for milestones in Gitea - any news on this feature?

For this to work, I think milestones would need to have a "start date" in addition to the already existing due date (Deadline).

With this present, we can draw the "guideline" in the graph.
next thing would be to select the count per day of all issues where issue.created > milestone.start and issue.closed is not null grouped by day
this data can then the pushed to any javascript charting library to draw a chart with two series (guideline + progress)

@kantholy commented on GitHub (Dec 6, 2023): I really would like to see this implemented for milestones in Gitea - any news on this feature? For this to work, I think milestones would need to have a "start date" in addition to the already existing due date (`Deadline`). - With this present, we can draw the "guideline" in the graph. - next thing would be to select the count per day of all issues `where issue.created > milestone.start and issue.closed is not null grouped by day` - this data can then the pushed to any javascript charting library to draw a chart with two series (guideline + progress)

GiteaMirror referenced this issue

2025-11-02 14:00:13 -06:00

[PR #4927] [MERGED] Backport: Fix bug when repo remained bare if multiple branches pushed #17551

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#4927