Some of my project managers have expressed a desire to have some sort of burn down chart for sprints/workboards.
From brief experiments, I think the necessary data can be extracted from the API, but would like to have a go at doing this properly.
Description
Description
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Resolved | • mmodell | T253090 Virtual Offsite: Phabricator hacking session | |||
| Declined | None | T253109 Extract data for burn down charts |
Event Timeline
Comment Actions
Burndown charts already exist. Random unmaintained external stuff parsing weird data dumps also exists. Other stuff pulling the API also exists (that's Will's, I think).
@dom_walden: Maybe you could elaborate what problem you'd like to solve, and also which solution (API data) you have in mind, not to reinvent wheels? :)
Comment Actions
Sure, I was really just using this as an excuse to learn more about the Phab API during the Hackathon, rather than produce some useful software.
As things have turned out, I will be participating in T252704 instead, so I will probably not be able to get involved in the Phab hacking session. Happy to close this task.
Comment Actions
@dom_walden: Feel free to do so if you don't plan to follow up on this task (plus this task lacks an assignee anyway?).