•  
      request #9551 Burndown improvement
    Infos
    #9551
    Marie Ange Garnier (marieange)
    2016-12-20 13:16
    2016-10-06 11:28
    9769
    Details
    Burndown improvement

    With the introduction of manual values in burdown, the previous way to calculate burndown value don't work anymore. If in a burndown, at children level we mix computed and manual values, the burndown is broken.

    Solution:

    • We want to use cached values table.
    • The table already exists, we want to improve way to store data inside
      • With system event
        • root_daily
        • first display of burndown (generate mising entries in cache)
        • last access if root_daily failed or not run ... (previous point not calculated)
      • The event do the calcul for a given timestamp and the duration+1
      • Duration or start date changed, it procceses an event
      • Feedback to user in all cases when the event is launched
      • Performances can be a little degraded
      • Log
      • Be able to regenerate cache for a given burndown
    • For the day "today", the dot is not stored in database, it's calculated with standard computed calculation
    • Burndown is not displayed until the data are available in the table cache
    Empty
    Empty
    Empty
    • [ ] enhancement
    • [ ] internal improvement
    Empty
    Stage
    Empty
    Closed
    2016-12-20
    Attachments
    Empty
    References
    Referencing request #9551

    Git commit

    tuleap/tuleap/stable

    Cache yesterday values at root daily 08d1910c70
    Correct field_id saved in database and correct timestamp saved a6c4f12fbe
    Generate full burndown at first display or when missing cached data 35599d80b0
    When start date has changed, burndown always ask to generate cache 02e463bbab
    End date for burndown calculation is wrong 58bf185523
    Force burndown generation when update duration or start_date 7629d21959
    When an artifact is updated it should not raise exception 2e498f451f
    Computed cache should be base on remaining effort_field instead of burndown field 3d9cb1a1e7
    Display message to inform that burndown is currently under calcul 0487215401
    Fatal error while displaying system event BURNDOWN_DAILY 2416d75821
    Correct burndown request for burndown generation 297d53231c
    When burndown doesn't have a start_date set, it should not ask cache generation bc68114f9d
    New burndown calculation 13ece851ef
    When last day of burndown is inferior to today, bdffc891fd
    Burndown refactoring - First part 9301d960be
    Add Unit tests for burndown 3a8cc341d6
    button force cache generation 7db3be2096
    Burndown refactoring - Second part 80a534e192
    REST tests for burndown 7dc98f01c6
    Burndown button for cache generation should not be displayed if burndown isn't calculable 6738c25e94
    Fix REST tests for trafficlights f228a81216

    Follow-ups

    User avatar
    Thomas Gerbet (tgerbet)2016-11-24 14:11
    • Original Submission
      Something went wrong, the follow up content couldn't be loaded
      Only formatting have been changed, you should switch to markup to see the changes
    User avatar
    • Original Submission
      Something went wrong, the follow up content couldn't be loaded
      Only formatting have been changed, you should switch to markup to see the changes
    User avatar
    • Original Submission
      Something went wrong, the follow up content couldn't be loaded
      Only formatting have been changed, you should switch to markup to see the changes
    User avatar
    • Original Submission
      Something went wrong, the follow up content couldn't be loaded
      Only formatting have been changed, you should switch to markup to see the changes