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.

    •  
      story #9096 Define comment as mandatory in a tracker workflow transition
    Actions
    Summary
    Empty
    Define comment as mandatory in a tracker workflow transition
    A transition cannot occurs if a follow-up comment is not provided

    Information

    • A tracker administrator will be able to set a comment as mandatory for a given transition in the same screen where he is able to set fileds as mandatory. (no mock-up for now)
    • This information will be taken into account in XML import and export
    • This information will be duplicated on project creation and on trakcer creation with template

    Issues

    /!\ A mandatory comment will not be set for a new artifact (no comment in new artifact form)

    Empty
    Empty
    Status
    Empty
    Done
    Development
    • [ ] Does it involves User Interface? 
    • [ ] Are there any mockups?
    • [x] Are permissions checked?
    • [x] Does it need Javascript development?
    • [x] Does it need a forge upgrade bucket?
    • [ ] Does it need to execute things in system events?
    • [x] Does it impact project creation (templates)?
    • [ ] Is it exploratory?
    Empty
    Details
    #9096
    Yannis ROSSETTO (rossettoy)
    2016-08-08 10:11
    2016-04-22 09:56
    4619

    References
    Referencing story #9096

    Artifact Tracker v5

    rel #9211 8.18

    Git commit

    tuleap/tuleap/stable

    A transition cannot occurs if a follow-up comment is not provided 3edfc29aab
    User avatar Nicolas Terray (nterray) , 2016-08-05 08:34
    Do not raise perms error when the transition is not valid b11b9e97fa
    User avatar Nicolas Terray (nterray) , 2016-08-08 09:30
    Referenced by story #9096

    Other

    gerrit #6285
    gerrit #6296
    Display settings

    Follow-ups