•  
     
    story #10670 a BurnUp chart based on Done stories
Summary
Empty
a BurnUp chart based on Done stories

I can track development effort vs. budget

BurnUp will be a new field of an artifact (like burndown) with 3 fields to configure:

  • start_date: when to start computation
  • duration: how long should it last
  • capacity: how much effort is targeted (for ideal burn-up line)

Difference with burndown:

  • Rendering is done with D3js lib (instead of EOL jpgraph)
    • REST route /artifacts/:id (or equivalent) must return the values
    • Need to implement the rendering with the new lib. We cannot re-use directly what's already present for agile dashboard home page because it lacks of
      • abscissa and ordinates legend
      • abscissa scale (days)
      • labels for each line
    • Rendering must use the same style (colors, fonts…) as the Kanban's cumulative flow chart
  • Computation is done like:
    • The elements linked to the current artifact
    • Within this list, only artifacts that are declared "Done" (story #10631) are taken into account
    • For those items, we sum the value of the field declared in "initial_effort" semantic

Things that's need to be verified / sorted-out during implementation:

  • What about several burn-up fields on 1 artifact (with different target_fields tought). Verify it's possible and it doesn't mess the global computation. If it's not easly possible, ensure it's not possible to configure 2 burn-up fields.
  • Ensure fixes made for Timezone handling on burndown are present

Things to test:

  • Verify behaviour with a burndown and a burn-up field
  • Verify that deletion of field (tracker, project) means no longer any computation for this field

New field check list:

  • Tracker Field Structure
    • Specific properties
      • Yes configuration based on other fields TBC...
    • Field can be switch to another type (only sb/msb)
      • No
    • Shared Fields
      • No
    • Import/Export XML
      • Yes
    • Field is duplicated on tracker inheritance (both tracker and project creation)
      • Yes
    • Definition is NOT given through SOAP @deprecated
      • Correct  
    • Definition is given through REST (representations)
      • Yes
    • Migrate field from TV3 (if not done)
      • No
    • Does new field can be used for burndown?
      • No
    • Can the field be required
      • No
  • Artifacts
    • Export/import CSV
      • No
    • What does ‘None’ mean for this field?
      • No
    • Default value
      • No
    • Field is involved in notifications
      • Yes (<img src="">)
    • New value is sent in notifications
      • See notif
    • Diff of the field appears in changesets
      • No
    • Get/create/update NOT through SOAP @deprecated
      • Correct
    • New value is Copyed on Artifact copy
      • No
    • New value can be used in semantic
      • No
    • New value can be updated on masschanges
      • No
    • On an artifact with artifact links, on creating directly a child the field can be used
      • No
  • Reports
    • Field is searchable through criteria
      • No
    • Field is displayed as a column in table
      • No
    • Field is used to sort
      • No
    • Field is used for aggregates
      • No
    • Field is used to build charts
      • No
    • Field is used to build cardwall
      • No
  • Angular
    • Create/ edit modal
      • No
    • Cardwall edit in place
      • No
    • Card field in planning v2
      • No
    • Card field in kanban + filter + highlight
      • No
    • Does field can be directly updated in Cardwall
      • No
    • Modal edit Release
      • No
    • Modal add a Task
      • No
  • User documentation is accurate
    • Yes

Technical points:

  • System event for daily burndown computation can be re-used to add the burn-up computation
  • A new system event is needed to re-compute 1 burn-up in case of error
Empty
Empty
Status
Done
Development
Empty
Empty
Details
#10670
Manuel Vacelet (vaceletm)
2018-01-19 09:53
2017-09-20 14:35
3270

References

List of items referenced by or referencing this item.

Git commit

Follow-ups

  • User avatar
    gerrit #10382 integrated into Tuleap 9.16.99.102

    • Status changed from On going to Done
  • User avatar
    gerrit #10383 integrated into Tuleap 9.16.99.101.
  • User avatar

    gerrit #10376 integrated into Tuleap 9.16.99.97

  • User avatar
    gerrit #10368 integrated into Tuleap 9.16.99.96.
  • User avatar
    gerrit #10380 integrated into Tuleap 9.16.99.95
  • User avatar
    gerrit #10377 integrated into Tuleap 9.16.99.94
  • User avatar
    gerrit #10367 integrated into Tuleap 9.16.99.90.
  • User avatar
    gerrit #10363 integrated into Tuleap 9.16.99.83
  • User avatar
    gerrit #10292 integrated into Tuleap 9.16.99.68
  • User avatar
    gerrit #10345 integrated into Tuleap 9.16.99.67
  • User avatar
    gerrit #10322 integrated into Tuleap 9.16.99.48.
  • User avatar
    gerrit #10316 integrated into Tuleap 9.16.99.46
  • User avatar
    gerrit #10306 integrated into Tuleap 9.16.99.35
  • User avatar
    gerrit #10290 integrated into Tuleap 9.16.99.29
  • User avatar
    gerrit #10294 integrated into Tuleap 9.16.99.22
  • User avatar
    gerrit #10245 integrated into Tuleap 9.16.99.19
  • User avatar
    gerrit #10291 integrated into Tuleap 9.16.99.18
  • User avatar
    gerrit #10250 integrated into Tuleap 9.16.99.13.
  • User avatar
    gerrit #10253 integrated into Tuleap 9.16.99.12.
  • User avatar
    gerrit #10282 integrated into Tuleap 9.16.99.10.
  • User avatar
    gerrit #10248 integrated into Tuleap 9.15.99.106.
  • User avatar
    gerrit #10226 integrated into Tuleap 9.15.99.93
  • User avatar
    gerrit #10228 integrated into Tuleap 9.15.99.92
  • User avatar
    gerrit #10225 integrated into Tuleap 9.15.99.91
  • User avatar
    gerrit #10223 integrated into Tuleap 9.15.99.89
  • User avatar
    A "Force cache regeneration" button might still be useful if the semantic initial effort or done have been modified somewhere in the hierarchy of the burnup artifacts. Users might not want to have their burnups completely changed every-time someone change something in another tracker. The button to refresh the burnup is probably enough for this case.

    • Acceptance criteria
  • User avatar
    gerrit #10222 integrated into Tuleap 9.15.99.88
  • User avatar
    gerrit #10211 integrated into Tuleap 9.15.99.87
  • User avatar
    gerrit #10219 integrated into Tuleap 9.15.99.85.
  • User avatar
    gerrit #10217 integrated into Tuleap 9.15.99.84
  • User avatar
    gerrit #10218 integrated into Tuleap 9.15.99.83.
  • User avatar
    gerrit #10216 integrated into Tuleap 9.15.99.82
  • User avatar
    gerrit #10212 integrated into Tuleap 9.15.99.78.
  • User avatar
    gerrit #10199 integrated into Tuleap 9.15.99.74.
  • User avatar
    gerrit #10208 integrated into Tuleap 9.15.99.73
  • User avatar
    gerrit #10188 integrated into Tuleap 9.15.99.71.
  • User avatar
    gerrit #10196 integrated into Tuleap 9.15.99.63.
  • User avatar
    gerrit #10187 integrated into Tuleap 9.15.99.51
  • User avatar
    gerrit #10156 integrated into Tuleap 9.15.99.47.
  • User avatar
    gerrit #10153 integrated into Tuleap 9.15.99.32.
  • User avatar
    gerrit #10168 integrated into Tuleap 9.15.99.31.
  • User avatar
    gerrit #10167 integrated into the artifact-modal
  • User avatar
    gerrit #10149 integrated into Tuleap 9.15.99.27.
  • User avatar
    gerrit #10162 integrated into Tuleap 9.15.99.26.
  • User avatar
    gerrit #10161 integrated into Tuleap 9.15.99.25.
  • User avatar
    gerrit #10135 integrated into Tuleap 9.15.99.19.
  • User avatar
    gerrit #10136 integrated into Tuleap 9.15.99.4.
  • User avatar
    • Status changed from To be done to On going
  • User avatar
    • Acceptance criteria
  • User avatar
    • I want to
      -a BurnUp chart based on actual effort 
      +a BurnUp chart based on Done stories 
    • So that
    • Acceptance criteria
    • Permissions set to