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 #7088 Cannot update artifact when a field is mandatory and empty: JS error
    Actions
    Infos
    #7088
    Manuel Vacelet (vaceletm)
    2016-01-13 14:59
    2014-06-23 09:16
    7104
    Details
    Cannot update artifact when a field is mandatory and empty: JS error
    I changed a value in a string field + a comment and when I click submit,

    In Chrome, I get the following JS error:
    An invalid form control with name='artifact[5378][content]' is not focusable.

    In FF, I have a popup that tells me that I need to fill a given field (at the wrong place)

    It seems related to the fact that a field was turned to mandatory and when I update the artifact, the field is empty to it should be highlighted but the highlight fails
    Trackers
    development
    Empty
    • [ ] enhancement
    • [ ] internal improvement
    Empty
    Stage
    Benjamin Dauton (bdauton_enalean)
    Closed
    2016-01-13
    Attachments
    Artifact links
    Empty
    Empty
    References
    Referencing request #7088

    Artifact Tracker v5

    rel #6687 7.2
    request #7117 Problem updating story - required field is not highlighted properly

    Git commit

    tuleap/tuleap/stable

    Merge commit 'refs/changes/71/2671/1' of ssh://gerrit.tuleap.net:29418/tuleap into stable 60f9b72985
    User avatar Nicolas Terray (nterray) , 2014-06-23 14:07
    request #7088: Cannot update artifact when a field is mandatory and empty: JS error 0958df5331
    User avatar Benjamin Dauton (bdauton_enalean) , 2014-06-23 11:00
    Display settings

    Follow-ups

    User avatar
    Manuel Vacelet (vaceletm)2014-06-23 09:22
    • Summary
      -Cannot update artifact: JS error 
      +Cannot update artifact when a field is mandatory and empty: JS error 
    • 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