•  
     
    story #6771 have backlog and milestone types in /v1/milestones/{id}
Summary
Empty
have backlog and milestone types in /v1/milestones/{id}
Empty
On tracker:
Add parent tracker info in /tracker/:id route

On milestone:
"resources" : {
        "milestones" : {
            "uri" : "/milestones/666/milestones",
            "accept" : {"trackers" : [{"id" : "21", "uri" : "/trackers/21"}], ...}
        },
        "backlog" : {
            "uri" : "/milestones/666/backlog",
            "accept" : {"trackers": [{"id" : "41", "uri" : "/trackers/41"}, {"id" : "42", "uri" : "/trackers/42"}], ...}
        },
        "content" : {
            "uri" : "/milestones/666/content",
            "accept" : {"trackers": [{"id" : "41", "uri" : "/trackers/41"}, {"id" : "42", "uri" : "/trackers/42"}], ...}
        },
        "cardwall" : "/milestones/666/cardwall", // we could imagine "valid_types" here to list the trackers of the cards that can be in the cardwall
        "burndown" : null
    }
}
Empty
Laurent Delaigue (ldelaigue)
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
#6771
Manuel Vacelet (vaceletm)
2014-05-07 15:20
2014-04-25 10:22
3177

References

Follow-ups

User avatar
  • I want to
    -have backlog and milestone types in /v1/projects/{id}/plannings 
    +have backlog and milestone types in /v1/milestones/{id} 
  • Acceptance criteria
    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
User avatar
Just to be clear, because I think the title of the ticket is misleading.
This new structure of data "resources" : {...} should be available not on plannings but on milestones via

GET /milestones/{id}

Putting this info on plannings would be more sensitive to possible future changes (heterogeneous sub-milestones for instance)
User avatar
  • Acceptance criteria
    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
  • Permissions set to