===What reports are needed?===
** Use case
** Which data?
** How is it presented?
** design notes, algorithms, business logic
* "How long is it taking to close tasks?"
** As a data center engineer, I want to know how old my tasks are, so that I can know if I'm meeting commitments (SLO).
** Phabricator data:
*** scope: all tasks for one project? For one data center? Per assignee?
*** fields: name, date opened, date resolved, date stalled, tags
*** simplest: one number on a page, with label.
**** "Average age of DC-Ops tasks upon completion: 47 working days"
*** better: bar chart with different value for each data range. Monthly? Quarterly?
**** Calendar Age = Date Resolved minus Date Opened
**** Working Time Age = Calendar Age minus Stalled Time
**** Could include open tasks as well by using 'today' as the [minimum possible] close time. Keep separate from closed tasks to avoid generating misleading data.
* "What should I work on next?"
** Use: As a data center engineer, I want to know what I should work on next, so that my customers' needs are met as well as possible.
** Use: As a customer, I want to know when my request is going to be worked on, so that I can decide whether to escalate my request.
*** probably will be met with SLO plan.
** stack-rank all DC-Ops tasks per data center.
* where is the data hosted?
* how is the report generated?
** where would a script live?