•  
      request #33634 Discrepancies in computed value computing between field and burndown
    Infos
    #33634
    Martin GOYOT (goyotm)
    2023-07-26 17:24
    2023-07-26 17:23
    35233
    Details
    Discrepancies in computed value computing between field and burndown

    Given:

    • 3 artifacts (Feature, Story, Task) linked this way (without considering any specific type): ProgramIncrement, Feature, Task
    • Task has a Remaining Effort numeric field with value 3
    • Feature Does not have any Remaining Effort field whatsoever.
    • ProgramIncrement has a Remaining Effort computed value field and a Burndown Chart

    I get:

    • ProgramIncrement value for Remaining Effort is 3 although Feature does not have such a field
    • ProgramIncrement BurndownChart is not functionning, showing "nk" as remaining effort, although it is computed in the Remaining Effort field

    If:

    • A field Remaining Effort of type computed value is added to Feature

    Then:

    • ProgramIncrement value for Remaining Effort is still 3 (as expected)
    • ProgramIncrement BurndownChart is working showing "3" as remaining effort (as expected)

    A guess would be that checks are different on BurndownChart and Computed Value field when it comes to the computation, the former stopping when the directly linked artifact don't have the targeted field while the latter does continue to browse the links graph in search of the field in farther artifacts.

    Trackers
    Empty
    Empty
    • [ ] enhancement
    • [ ] internal improvement
    Empty
    Stage
    Empty
    New
    Empty
    Attachments
    Empty
    References
    References list is empty

    Follow-ups

    User avatar
    Martin GOYOT (goyotm)2023-07-26 17:24
    • 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