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 #10649 Cannot update a FRS release
    Actions
    Infos
    #10649
    Nicolas Terray (nterray)
    2017-09-15 09:45
    2017-09-14 11:22
    10885
    Details
    Cannot update a FRS release
    On a release in the FRS, I try to remove a file, and when I submit the form nothing happen.

    In the web console:

    Uncaught ReferenceError: release_mode is not defined
    at checkParametersOnServer (frs.js:402)
    at checkFileUploadSize (frs.js:376)
    at HTMLInputElement.check_parameters (frs.js:431)
    at HTMLInputElement.responder (tuleap-eceb6106f1.js:6234)
    Delivery/File release system
    All
    Empty
    • [ ] enhancement
    • [ ] internal improvement
    Empty
    Stage
    Empty
    Closed
    2017-09-15
    Attachments
    Artifact links

    Releases

    Fixed in

    Artifact ID Project Tracker Summary Status Last Update Date Submitted By Assigned to
    rel #10571 Tuleap Releases 9.12 Delivered 2017-09-18 11:43 Yannis ROSSETTO (rossettoy)
    Empty
    References
    Referencing request #10649

    Git commit

    tuleap/tuleap/stable

    Merge commit 'refs/changes/07/9507/1' of ssh://gerrit.tuleap.net:29418/tuleap into HEAD 6a69e40db7
    User avatar Yannis ROSSETTO (rossettoy) , 2017-09-15 09:44
    request #10649: Cannot update a FRS release when a user group set in the permission field 2abff42df3
    User avatar Thomas Gerbet (tgerbet) , 2017-09-14 13:39
    Referenced by request #10649

    Artifact Tracker v5

    rel #10571 9.12

    Other

    gerrit #9507
    Display settings

    Follow-ups

    User avatar
    Yannis ROSSETTO (rossettoy)2017-09-15 09:45
    Integrated into Tuleap 9.11.99.148
    • Status changed from Under review to Closed
    • Connected artifacts
    • Close date set to 2017-09-15
    User avatar
    Thomas Gerbet (tgerbet)2017-09-14 13:37
    We have not been able to reproduce the issue when we create new releases. It looks like it only impact old releases before work has been done on the permissions.

    A contribution is coming to be sure we do not break the page.
    • Status changed from New to Under implementation
    • Reported in version changed from development to All