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 #6903 Can submit a new artifact even if I doesn't have "can submit" rights on all fields
    Actions
    Infos
    #6903
    Benjamin Dauton (bdauton_enalean)
    2014-07-08 11:50
    2014-05-19 14:10
    6937
    Details
    Can submit a new artifact even if I doesn't have "can submit" rights on all fields

    Behaviour should be as follows:

    - if user can't submit all required fields, user cannot submit artifact

    - if user can't submit fields with default value, fields are given default value on creation,

    - if user can submit fields with default value but leaves them blank/ null, the fields are not set to default value.

    - the behaviour is the same on UI/ REST/ SOAP

    Trackers
    development
    Empty
    • [ ] enhancement
    • [ ] internal improvement
    Emilio Palmiero (empa)
    Stage
    Benjamin Dauton (bdauton_enalean)
    Closed
    2014-06-09
    Attachments
    Artifact links

    Releases

    Empty
    References
    Referencing request #6903

    Artifact Tracker v5

    request #7455 Default values are not submitted a new artifact with SOAP and REST

    Git commit

    tuleap/tuleap/dev

    Merge commit 'refs/changes/59/2459/9' of ssh://gerrit.tuleap.net:29418/tuleap into HEAD 77ad467237
    User avatar Sandra Echinard (sechinard) , 2014-06-09 18:08
    request #6903: Can submit a new artifact even if I doesn't have "can submit" right on all fields c4ea6ec710
    User avatar Benjamin Dauton (bdauton_enalean) , 2014-06-05 17:39

    tuleap/tuleap/stable

    Merge commit 'refs/changes/59/2459/9' of ssh://gerrit.tuleap.net:29418/tuleap into HEAD 77ad467237
    User avatar Sandra Echinard (sechinard) , 2014-06-09 18:08
    request #6903: Can submit a new artifact even if I doesn't have "can submit" right on all fields c4ea6ec710
    User avatar Benjamin Dauton (bdauton_enalean) , 2014-06-05 17:39
    request #6903: Can submit a new artifact even if I doesn't have "can submit" right on all fields 82715f0035
    User avatar Benjamin Dauton (bdauton_enalean) , 2014-06-19 11:45

    tuleap/u/vaceletm/tuleap/dev

    Merge commit 'refs/changes/59/2459/9' of ssh://gerrit.tuleap.net:29418/tuleap into HEAD 77ad467237
    User avatar Sandra Echinard (sechinard) , 2014-06-09 18:08
    request #6903: Can submit a new artifact even if I doesn't have "can submit" right on all fields c4ea6ec710
    User avatar Benjamin Dauton (bdauton_enalean) , 2014-06-05 17:39
    request #6903: Can submit a new artifact even if I doesn't have "can submit" right on all fields 82715f0035
    User avatar Benjamin Dauton (bdauton_enalean) , 2014-06-19 11:45

    Release

    release #85
    Referenced by request #6903

    Artifact Tracker v5

    rel #6687 7.2
    Display settings

    Follow-ups

    User avatar
    dylan bowden (dylan)2014-07-08 11:50
    Hi, that condition was altered because it created big regressions for existing usage. I should have updated the artifact.

    In fact, the logic is slightly more subtle and goes like this:
    "required fields are required ONLY for those who can see them".

    Thus, if a user can't submit all required fields THAT THEY CAN SEE, user cannot submit artifact.
    User avatar
    Patricia Carrasco (pcar)2014-07-07 22:55
    Hi, we have installed 7.2 but the first condition described by Dylan is failing:

    - if user can't submit all required fields, user cannot submit artifact
    • CC list set to Emilio Palmiero (empa)
    User avatar
    dylan bowden (dylan)2014-06-06 11:55
    • 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
    dylan bowden (dylan)2014-06-06 11:54
    Behaviour is as follows:

    - if user can't submit all required fields, user cannot submit artifact
    - if user can't submit fields with default value, fields are given default value on creation,
    - if user can submit fields with default value but leaves them blank/ null, the fields are not set to default value.

    The behaviour is the same on UI/ REST/ SOAP