@Fjalapeno Do you have any other Phab-upgrade tickets that could fit under here?

@DStrine @JAufrecht Do any of these existing tasks, to your knowledge, cover the issue of story points only being allowed when "Is Sprint" is checked?

In T105404#1499075, @MBinder_WMF wrote:

@DStrine @JAufrecht Do any of these existing tasks, to your knowledge, cover the issue of story points only being allowed when "Is Sprint" is checked?

See T78361; related: T96954, T96953.

In T105404#1499075, @MBinder_WMF wrote:

@DStrine @JAufrecht Do any of these existing tasks, to your knowledge, cover the issue of story points only being allowed when "Is Sprint" is checked?

I can't see any mention of that issue. It's worth documenting if you really want it.

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.

In T105404#1499436, @Qgil wrote:

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.

In textbook scrum, Story points are used in the backlog for long term planning. Scrum strongly recommends that teams use hour estimation inside a sprint.

@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. :)

@KLans_WMF thanks for that link

@DStrine have we compared this list to existing, already-upstreamed (already on Phabricator project board) tasks?

@KLans_WMF @DStrine @JAufrecht

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.

I think it would be useful, and I don't think it would cause any harm.

After chatting in our "How to drive Phab" meeting, we decided that this should remain a wishlist, as opposed to umbrella'ing hundreds of tasks.