•  
     
    story #5579 /projects/:id/backlog
Summary
user
/projects/:id/backlog
Methods: OPTIONS, GET, PUT

Returns a collection of backlog items[1] that are not planned and plannable in a top milestone (top milestone = milestone that has no parent).

Please note that the PUT method is only here to change the order of the elements in the collection. [ <id>, <id>, … ]

[1] https://tuleap.net/wiki/index.php?pagename=REST%20API%2FPlanning&group_id=101#Backlog_Item
Empty
Empty
Empty
Status
Empty
Done
Development
  • [ ] Does it involves User Interface? 
  • [ ] Are there any mockups?
  • [ ] 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
#5579
Nicolas Terray (nterray)
2013-12-06 10:31
2013-11-18 14:58
3164

References
Referencing story #5579
Referenced by story #5579

Follow-ups

User avatar
last edited by: Stéphane Bégaudeau (begaudeaus) 2013-12-06 10:35

When we try to use PUT /projects/{id}/backlog on https:tuleap.net (6.7.99.27) or on our own Tuleap instance (6.7.99.28) we have the following error:

{ "error": { "code": 500, "message": "Internal Server Error: There are duplicated ids" }, "debug": { "source": "MilestoneResourceValidator.class.php:179 at call stage", "stages": { "success": [ "get", "route", "negotiate", "authenticate", "validate" ], "failure": [ "call", "message" ] } } }

 

We did not have any duplicated ids in the data sent to the server.

By the way, on the Tuleap API Explorer, the description of the message to send uses "property" instead of "id": https://tuleap.net/api/explorer/#!/projects/updateBacklog_put


  • Category set to
User avatar
  • So that
    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