Ticket types included in the Phabricator configuration are currently biased toward always being relevant to Kolab in some or the other extent.

This creates a very large global product backlog, with tasks for potential external contributors (consumers of software development projects for which we are upstream, with itches to scratch different then our own, looking for things to do) and skewed prioritization.

This may, in part, be addressed in T1039, but doesn't allow a distinction to be drawn between "tracking" tickets (such as the ones on the Architecture & Design workboard), "reminder" tickets (not yet tasks, just placeholders) and actual tasks (eligible for inclusion in sprints), etc.