•  
      request #11058 Burndown - today computation can be different that the cached one
    Infos
    #11058
    Marie Ange Garnier (marieange)
    2020-06-09 16:19
    2018-01-30 17:04
    11388
    Details
    Burndown - today computation can be different that the cached one
    The easiest way to reproduce is to use the xml in attachment for AD configuration.
    It occurs on complex computed field imbrication (tree of computed must have a deep > to 2)

    Example given following AD structure:
    Release R1 => remaining effort => autocomputed
    |
    Sprint S1 => remaining effort => autocomputed
    |
    US 1 => remaining effort => manual, let's tell 1,5

    When you open the burndown of the release:
    -> the effort for today is correct and displayed to 1,5
    -> the effort for yesterday compute twice the remaining effort of US1 and display 3

    Error is not present at sprint level.
    Trackers
    All
    Empty
    • [ ] enhancement
    • [ ] internal improvement
    Empty
    Stage
    Marie Ange Garnier (marieange)
    Closed
    2020-06-09
    Attachments
    References

    Follow-ups

    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
    • Category set to Trackers
    • Status changed from New to Under implementation
    • Assigned to changed from None to Marie Ange Garnier (marieange)
    • Attachments computed-bug.zip removed; agile_dashboard_template.xml added
    • Reported in version set to All
    User avatar
    • Summary
      -Burndown - today computation is not the same that the cached one 
      +Burndown - today computation can be different that the cached one