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 #6936 REST Know which type of children a backlog item can have
Actions
Summary
Empty
REST Know which type of children a backlog item can have
Empty

Similar to the milestones story #6771

 

On backlog item representation:
/milestones/:id/backlog GET

...
 "accept" : {"trackers": [{"id" : "41", "uri" : "/trackers/41"}, {"id" : "42", "uri" : "/trackers/42"}], ...}

....

Empty
Laurent Delaigue (ldelaigue)
Status
Empty
Canceled
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
#6936
dylan bowden (dylan)
2015-07-22 11:33
2014-05-23 16:41
4866

References
Artifact links
Empty
Referencing story #6936

Artifact Tracker v5

epic #4952 REST API
Referenced by story #6936

Artifact Tracker v5

story #6771 have backlog and milestone types in /v1/milestones/{id}
Display settings

Follow-ups

User avatar
Laurent Delaigue (ldelaigue)2014-10-13 09:38
For the moment we rely on the tracker hierarchy to get this info.
So no, we don't need this implemented, as long as the tracker hierarchy remains as it is.