Phlogiston/Configuring

Phlogiston has a stable labs server for WMF use, here. This downloads data from Phabricator every night, reconstructs all data, and generates reports.

Report Settings
Each team should use a separate Phlogiston report. Each report must have a configuration file, in the main phlogiston directory, named using the pattern:. The  should be a short (2-3 characters, hard limit of 6) unique identifier for this project.

Required Variables
The configuration file must contain these variables:

This is the report title displayed on the report page and charts. It should reflect the scope of tasks in the report, which is usually the name of the team responsible for the tasks.

This is a comma-separated list of Phabricator project names. Spaces in names don't need to be quoted or escaped.

This is the starting date for Phlogiston to import data from Phabricator. All data (tasks, transactions, projects, etc) before this date will be ignored.

Optional Variables
Default_points are assigned to all unpointed stories. If not present, unpointed stories remain unpointed.

If True, then after all tasks are categorized, Phlogiston will rewrite the history of all tasks so that they appear to always have been in whatever category they are in on the most recent day. For example, if task 100 was categorized as Category A on March 10th, and changed to Category B on April 15th, and the report is run on May 1, task 100 will appear to always have been in Category B. Defaults to false.

If True, then Phlogiston will rewrite the history of all tasks so that they appear to always have had the point value that they have on the most recent day. Defaults to false.

If set, burnup charts will show resolved tasks at zero on this date. This is to show progress from a recent point, such as the beginning of the quarter. Otherwise, a team that already has 500 resolved tasks at the beginning of the quarter will see their progress during the quarter rising from 500 (instead of 0), making it difficult to see recent progress.

These two variables determine which charts should be displayed, charts based on task count, charts based on task points, or both. Both default to True, so the configuration file should have neither (to get both count and points), or one of them set to False (to hide that type of chart).

Report Category Settings
With the default configuration, Phlogiston will create one category for each combination of Project and Projectcolumn. This list of categories can be manually retitled, re-ordered, and consolidated with the optional file, which can be edited in a spreadsheet. See col_recategorization.csv for an example. If this file is not present, Phlogiston will generate a list of categories based on Phabricator projects and project columns, ordered alphabetically.

Required Columns
This is an integer sort sequence that determines the relative priority of categories and the order categories are displayed in the report. If a task matches two or more different categories, it will be counted in the category with the lowest sort_order.

If True, this category will be displayed in the report. If False, the category will be omitted from the Forecast and Burnup charts, but will be present in the "Unzoomed" versions of charts and in Velocity charts.

Required. The display label of the category.

,

These are Phabricator project IDs. If present, Phabricator will categorize all tasks that belong to both of these projects in this category.

A text string used to categorize tasks. Phlogiston compares this to the raw category string of each task (which is a compound of the project title, project column, and titles of all parent tasks tagged with the category Phabricator project) to determine if the task belongs to this category. If both t1/t2 and matchstring are specified, Phlogiston will ignore matchstring. PhlogOther is a magic word that will match everything else.

Custom data processing
If your Phabricator projects do not follow these conventions, or have data by multiple configurations over time which you wish to preserve, you can write custom SQL code to replace the default conversion of reconstructed data into Phlogiston reporting data. A file called, if present, will be run instead of generic_make_history.sql. See also ve_make_history.sql for an example.

Adding new projects
Contact the Phlogiston administrator Joel A to get your project added to the batch script so that it runs every night.