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 #5912 PUT /milestones/:id/milestones
    Actions
    Summary
    User
    PUT /milestones/:id/milestones
    I can add an existing submilestone to a milestone.
    • Given I have:
      GET /milestones/101/milestones
-> [ { id: 123, …}, { id: 124, …}, { id: 125, …} ]
      When I call:
      PUT /milestones/101/milestones
[ 123, 125, 126 ]
      Then the submilestone 124 is unlinked and the submilestone 126 is linked.
    • This is integration tested (like other REST developments)
    • The mess of error codes (4xx vs 5xx) is cleared
    • What if I send in the PUT an id of an artifact that is not a "milestone" (nor a potential child of the current milestone) ?
    Empty
    Empty
    Status
    Empty
    Done
    Development
    • [ ] Does it involves User Interface? 
    • [ ] Are there any mockups?
    • [x] Are permissions checked?
    • [ ] Does it need Javascript development?
    • [ ] Does it need a forge upgrade bucket?
    • [ ] Does it need to execute things in system events?
    • [ ] Does it impact project creation (templates)?
    • [ ] Is it exploratory?
    Empty
    Details
    #5912
    Nicolas Terray (nterray)
    2014-01-24 11:05
    2014-01-17 12:14
    3174

    References
    Artifact links
    Referencing story #5912

    Artifact Tracker v5

    rel #5801 6.10

    Release

    release #72
    Referenced by story #5912

    Artifact

    art #5922
    art #5923
    Display settings

    Follow-ups