Skip to main content

Public

Project privacy set to public. By default, its content is available to everyone (authenticated or not). Please note that more restrictive permissions might exist on some items.

    •  
      request #9594 Folders display artifact twice when it also a child
    Infos
    #9594
    Manuel Vacelet (vaceletm)
    2016-11-18 16:03
    2016-10-19 17:23
    9873
    Details
    Folders display artifact twice when it also a child

    Attached a project that show the issue, if you go to Planning folder tracker "Product 1" artifact you will see:

    • Epic Two
      • Story Three
      • Story Four
      • Story bellow 2
    • Epic Four
    • Epic Five
    • Story bellow 2

    Story bellow 2 is listed twice whereas it should only be bellow "Epic Two"

     

    Trackers
    9.0
    Empty
    • [ ] enhancement
    • [ ] internal improvement
    Empty
    Stage
    Empty
    Closed
    2016-11-16
    Attachments
    By Manuel Vacelet (vaceletm)
    (10 kB)
    folder.zip
    References
    Referencing request #9594

    Artifact

    request #9593 Folders doesn't list things that are not directly connected to it

    Git commit

    tuleap/tuleap/stable

    Merge commit 'refs/changes/21/6821/4' of ssh://gerrit.tuleap.net:29418/tuleap into HEAD dfddba594d
    User avatar Yannis ROSSETTO (rossettoy) , 2016-11-16 17:22
    request #9594: Folders display artifact twice when it also a child 2b8406148c
    User avatar Thomas Gerbet (tgerbet) , 2016-11-08 12:38
    Display settings

    Follow-ups

    User avatar
    Yannis ROSSETTO (rossettoy)2016-11-16 17:23
    Integrated into Tuleap 9.1.99.12
    • Status changed from Under review to Closed
    • Close date set to 2016-11-16
    User avatar
    Manuel Vacelet (vaceletm)2016-10-31 15:35

    Yes, the implementation corresponds to the original spec.

    However the behaviour described by this spec is not the expected one, hence the 2 bugs raised.

    User avatar
    Thomas Gerbet (tgerbet)2016-10-31 15:09
    Hello,

    I'm a bit confused by this issue. The acceptance criteria of the story #9468 said we should load only the first level of directly connected artifacts without inspecting children.
    In the example "Story bellow 2" is directly connected to "Product 1" (aka Story bellow 2 is in folder Product 1) but is also a child of Epic Two. Without inspecting children (which would mean construct a complete hierarchy tree) we are not able to determine if Story bellow 2 should or should not appear in the first level.

    This bug seems to conflict with the original acceptance criteria and in the current state I'm not sure if we can fix it without impacting performances.

    What should we do?
    • Status changed from New to Waiting for information