Page MenuHomePhabricator

Manually setting sprint start/end date not intuitive, easy to forget
Closed, ResolvedPublic1 Estimated Story Points

Description

It's really easy to forget to set the sprint start/end dates, which will result in errors. Since setting the dates is required for the extension to behave correctly, can this be made more intuitive/impossible to forget? Perhaps set defaults, prompt the user for them when creating the sprint, etc etc.

Event Timeline

Awjrichards raised the priority of this task from to Needs Triage.
Awjrichards updated the task description. (Show Details)
Awjrichards moved this task to Backlog on the Phabricator-Sprint-Extension board.

https://www.mediawiki.org/wiki/Phabricator/Project_management#Sprints says you must set the start and end dates and links to this bug; update it if and when the behavior changes.

It also should be entirely optional. Why does it matter if a sprint doesn't have one? The only reason Gather uses sprints is so that it can use story points. We even turned our backlog into a sprint that ends 31st December 2018 (dumb!)

@Jdlrobson A Sprint by definition is a timeboxed project. I am sorry, but this is what it is. Start and end dates will remain required as long as the project is called a Sprint.

The concept of a "Backlog Project" could be developed as an another Project Type that allows points, but does not need start and end dates. I am considering adding a Project Type application interface for a less specific use case than Agile. This would solve this problem.

In the meantime, the above referenced patch provides a form for Sprint creation that includes Start and End dates, so it will be clear that this is a requirement for the Sprint project type.

@Christopher sure.. but currently the use of story points is tied to a project being a sprint and this is my frustration (which I guess is tangential:-) ) .
A Backlog project seems like a good solution to this thanks for proposing it (is there a task for this that I can follow?). I do agree though that if a sprint is setup it should not allow it to be a sprint without a start and end date