Several teams are requesting enhancements to Phabricator in order to boost productivity. This Epic serves as the umbrella for the tasks that request those features. It may eventually be limited, in scope, to specific teams (i.e. Apps).
The idea is that we don't want to add a Point field to all tasks, since most users and most tasks will not need them. Points are related to sprints, so it made sense to restrict them to Is Sprint projects.
@DStrine @MBinder_WMF this thread in the TPG public list archives may be of interest re: you requirements gathering effort: https://lists.wikimedia.org/pipermail/teampractices/2014-October/000475.html
@Qgil Thanks for that reasoning. The main issue some teams are having is that they would like to estimate items in their backlogs and then pull into sprints those items, sometimes based on their point value. What's happening now is that teams are making backlog boards into "sprints" in order to achieve the functionality. The downside to this is that is takes up a huge amount of space visually, which interrupts the main purpose of the backlog boards: high level overview, so when this process is done, they switch it back. It's a lot of drag.
There are certainly ways to get around this process-wise, but it's bad practice to adjust process to tools, rather than the other way around. :)
What do you guys think about umbrella-ing existing requests that are related to this epic (that is, ones that are already on the Phabricator project board)? I'd like an easy way to prevent creation of redundant tickets, and seeing them all in one place here might help.