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 #10465 Not able to add an artifact link when parent artifact have required permission on artifact field
    Actions
    Infos
    #10465
    marouane baini (bainim)
    2017-10-17 17:27
    2017-07-17 16:54
    10708
    Details
    Not able to add an artifact link when parent artifact have required permission on artifact field
    Not able to add an artifact link when the fields permissions on artifact are mandatory. To reproduce the issue you need to follow these steps.
    1. Set an hierarchy between 2 tracker (parent-child)
    2. Make the Field "Permissions on artifact" mandatory in the 2 trackers.
    3. Create parent and child artifacts making sure that you set a value in the artifact permission fields.
    4. Add an artifact link between an artifact from the child tracker to the parent tracker.
    This is the error :
    The field Permissions on artifact (permissions_on_artifact) is required.
    Fields are not valid
    Trackers
    Empty
    Empty
    • [ ] enhancement
    • [ ] internal improvement
    Empty
    Stage
    marouane baini (bainim)
    Closed
    2017-10-17
    Attachments
    Artifact links

    Releases

    Fixed in

    Artifact ID Project Tracker Summary Status Last Update Date Submitted By Assigned to
    rel #10587 Tuleap Releases 9.14 Delivered 2017-12-07 16:58 Manuel Vacelet (vaceletm)
    By marouane baini (bainim)
    (41 kB)
    child_father_link_error.png
    References
    Referencing request #10465

    Git commit

    tuleap/tuleap/stable

    Merge commit 'refs/changes/94/9494/8' of ssh://gerrit.tuleap.net:29418/tuleap 5a6caef140
    User avatar Manuel Vacelet (vaceletm) , 2017-10-17 17:24
    request #10465 Not able to add an artifact link 53e599c755
    User avatar Mohamed Hammami (hammamim) , 2017-10-17 11:55
    Display settings

    Follow-ups

    User avatar
    Manuel Vacelet (vaceletm)2017-10-17 17:27

    Integrated in 9.13.99.17. Thanks for the contribution !

    • Summary
      -Not able to add an artifact link 
      +Not able to add an artifact link when parent artifact have required permission on artifact field 
    • Status changed from Verified to Closed
    • Connected artifacts
    • Close date set to 2017-10-17
    User avatar
    Seif Eddine Gamoudi (gamoudis)2017-09-07 13:26
    last edited by: Seif Eddine Gamoudi (gamoudis) 2017-09-07 13:26
    Hi,
    It looks like the problem is surfacing when the parent tracker has a "permission on artifact field" set as required (child field doesn t matter).
    When linking an artifact from the "child" tracker to an artifact in the "parent" tracker it looks like the "permission on artifact field" in the parent artifact is not being provided therefore we get a nice "plugin_tracker_common_artifact err_required The field $1 is required."
    I think the solution would be:
    Providing the parent artifact missing "permission on artifact field" value when linking the artifacts.

    Any thought on how to proceed?
    User avatar
    marouane baini (bainim)2017-07-18 15:43
    Hello,
    I set the value of artifact permissions field when creating it.
    However when updating the child artifact by adding a reference to the parent artifact i get the error mentioned in the description of this artifact.
    • Summary
      -Changed Artifact Link field usage 
      +Not able to add an artifact link 
    • 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
    User avatar
    Thomas Gerbet (tgerbet)2017-07-18 08:49
    Hello,

    Does the permission on artifact field is filled or not?

    Not sure on how what you describe is related to the artifact link field, from your description it looks like you are expecting the field to work as it was before the fixes introduced by request #9893.
    • Status changed from New to Waiting for information