Currently, Phlogiston does not count Milestones against themselves, but instead counts the milestone task itself, and its points, in the Other category. This is accidental behavior. Proposal: filter out all Milestones from counting either as count or points.

Reasons to filter:
If the Milestone task counts, all burnups and all forecasts will show some result (typically, a 1 week forecast, based on the minimum calculated velocity of 1 task/week). It's probably more helpful for the Product Owners to see an empty backlog and a blank forecast if there are no sub-tasks assigned.

Reasons not to filter:
The Milestone task itself may have some points accounting for tracking or integration, and if that's intentional then, with filtering, extra work is required work to spin that into a subtask.

Leaning strongly to filter, looking for other opinions.