epic #5578 Complete Planning REST API

story #5588 /backlog_item/:id

Artifact

Summary

As a

user

I want to *

/backlog_item/:id

So that

Methods: OPTIONS, GET, PUT

Acceptance criteriaEmpty

AttachmentsEmpty

CC listEmpty

Status

CategoryEmpty

StatusCanceled

Development

Checklist

[ ] 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?

Technical informationsEmpty

Details

Artifact ID#5588

Submitted ByNicolas Terray (nterray)

Last Modified On2014-07-24 11:19

Submitted On2013-11-18 15:17

Rank5714

Permissions

Restrict access to this artifact for the following user groups:

References

Is related to

Artifact links

Empty

Reverse artifact links

Epics

Parent

Artifact ID	Project	Tracker	Summary	Status	Last Update Date	Submitted By	Assigned to
epic #5578	Tuleap	Epics	Complete Planning REST API	Closed	2014-02-26 10:57	Nicolas Terray (nterray)

Cross References

Referencing story #5588

Artifact Tracker v5

epic #5578 Complete Planning REST API

Follow-ups

Manuel Vacelet (vaceletm)

2014-07-24 11:19

Canceled stories should not have effort

Category set to

Nicolas Terray (nterray)

2013-11-18 15:19

Canceled as it is not needed for a first version of the planning api. The info of a backlog item is given in the collections (eg: /milestone/:id/backlog) and the creation of a backlog item is possible by SOAP tracker API.

Status changed from Ready (stalled) to Canceled

Public