Can't see progress towards a milestone, so people use burndown charts elsewhere

Bug #914835 reported by Matthew Paul Thomas on 2012-01-11
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Launchpad itself

Bug Description

Often a milestone is targeted at a particular date, but it is not easy to see whether targeted tasks are on schedule for that date.

To work around this, Ubuntu and Linaro teams both use burndown charts hosted outside of Launchpad. <> <>

Unfortunately, this causes a lot of bureaucracy in copying or linking issues from bug reports to blueprints. To the extent that developers don't get around to doing that copying or linking, bug fixes are implicitly deprioritized in favor of features, lowering the software's quality. And time is lost when people don't know about the burndown chart, or have trouble finding it.

This could be fixed in Launchpad by providing a Burndown view of bug reports, as a toggle with the existing List view. (See also bug 914854, about providing a Kanban view for a team.)

Implementing this would require first implementing a bug listing for milestones. <>

description: updated
Curtis Hovey (sinzui) wrote :

We considered this two years ago. There were performance issues that needed, and still need to be solved. I believe the asyc list/table loader can help to collection the data needed to present a burndown view.

tags: added: milestones
tags: added: lp-registry
Curtis Hovey (sinzui) on 2012-01-16
Changed in launchpad:
status: New → Triaged
importance: Undecided → Low
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers