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 #18487 Artifacts from deleted trackers must not be retrieved in hierarchy
    Actions
    Infos
    #18487
    Yannis ROSSETTO (rossettoy)
    2021-01-19 14:26
    2020-12-29 14:09
    20035
    Details
    Artifacts from deleted trackers must not be retrieved in hierarchy
    If you define two trackers (A and B), with tracker A parent of tracker B (per hierarchy).
    We create two artifacts (A1 and B1), and link A1 with B1. This link will have the type _is_child because of the hierarchy.

    When we delete tracker A, A1 is still displayed as the parent of B1, which must not be the case.

    This kind of check was added in SQL queries that checks artifact links across services.
    Trackers
    All
    Empty
    • [ ] enhancement
    • [ ] internal improvement
    Empty
    Stage
    Yannis ROSSETTO (rossettoy)
    Closed
    2020-12-30
    Attachments
    Artifact links
    Empty
    Empty
    References
    Referencing request #18487

    Artifact Tracker v5

    request #18837 Unable to create project from another one

    Git commit

    tuleap/tuleap/stable

    Merge commit 'refs/changes/64/21164/3' of ssh://gerrit.tuleap.net:29418/tuleap into HEAD c3cb615fbd
    User avatar Lorentz Romain (lorentzr) , 2020-12-30 11:18
    request #18487 Artifacts from deleted trackers must not be retrieved in hierarchy 7354dc36f9
    User avatar Yannis ROSSETTO (rossettoy) , 2020-12-29 16:56
    Remove _is_child at tracker deletion 477e4bd713
    User avatar Yannis ROSSETTO (rossettoy) , 2020-12-30 14:59
    Referenced by request #18487

    Other

    gerrit #21164
    gerrit #21197
    Display settings

    Follow-ups