~james-w/launchpad-work-items-tracker/spec-group-completion-by-priority

Viewing all changes in revision 239.

  • Committer: Andy Whitcroft
  • Date: 2010-11-22 14:04:30 UTC
  • Revision ID: apw@canonical.com-20101122140430-2im08u1ar3u233u3
report_tools: workitems_over_time descriptions are not unique

Currently when calculating how many work items of each status there are
for the purposes of graphing we flatten common descriptions.  However
it is entirly reasonable to have the same work item on two blueprints,
or indeed on the same blueprint:

  [apw] upstream your patches:TODO
  [cking] upstream your patches:TODO

When we generate the work items tables we actually assume a work item is
unique if it is on a different blueprint, description, assignee, milestone,
or status:

  SELECT DISTINCT w.spec, w.description, w.assignee, w.milestone, w.status

Move to the same system when flattening items for the graphs.  This way
the counts in the burn-down charts will match the totals in the tables
below them.

Signed-off-by: Andy Whitcroft <apw@canonical.com>

expand all expand all

Show diffs side-by-side

added added

removed removed

Lines of Context: