Access is granted. Please let me know if you get stuck on gaps in the documentation.
Can you say more about what kind of report? Phlogiston can be complicated to work with; would you like to meet with me or @MBinder_WMF to discuss what you need and set it up together?
Tue, Sep 4
Aug 24 2018
@MBinder_WMF this is one of the known, unfixed data quality bugs
Aug 14 2018
Tasks that are Done at the start of the status report and Done at the end of the status report are omitted (or else all resolved tasks would be on every status report). This includes tasks that are open in the middle of the report period but not the start or end.
Aug 9 2018
works on dev and prod.
Aug 8 2018
Categorize as Toolhub Milestone 2 all tasks that are:in project FY2018-19 and that are descendents of a task tagged Category whose title includes the text Toolhub Milestone 2
Is it safe to assume this is a unique data error? Not sure what else to do.
New board for FY19 milestones: https://phabricator.wikimedia.org/project/view/3256/
The first rule was catching everything, I think, and not leaving any tasks for the "Doing Test T174183" rule to operate on. I moved that rule (and the "Tracking" rule) higher, and it appears to work.
Aug 7 2018
Aug 6 2018
Jul 31 2018
Jul 30 2018
shrunk README to point to wiki instructions
Jul 27 2018
was handled at centralized level.
This is by design. There is a "last quarter" link that goes back 3 months further. See T175621: Phlogiston "show hidden" report should go back as far as possible for a feature request to address going back even further.
No requirements to use WorkType, so no need to complete this.
Jul 25 2018
Updated table list and definitions.
One hypothesis for why one of the counts (either the burnup line or the backlog areas) is wrong is that the recently_closed table may be mixing data. It has one column for date, one column for (first day of) week, one column for (first day of) month, and one column for (first day of) quarter, plus two dependent data fields. However, the week, month, and quarter should each have a separate row, since they each represent different time periods and presumably have different aggregade data. So, there could be mingling of week, month, and quarter data, which would explain variation in the discrepency.
Implemented on dev, tested with vec, and rolled to production. Documented here: