Content
View differences
Updated by Tobias Dillmann about 1 month ago
* Namespace `Agile::Sprint`
* but ensure that the table is just called `sprints` - the namespace will be removed later on.
* Name, start & end date, status
* Connect to work packages (add `sprint_id`), journal
* Sprints can be shared globally, **belong to a project,** or shared with subprojects.
* Similar behaviour to Versions, but with less options.
* Validations
<br>
Notes:
* Namespace it at the beginning - rename it later when the feature is (near) complete
* Come up with a good namespace
* This way, we will not break the existing implementation and can move in smaller steps instead of having to perform one big leap
* Model itself
* name (automated naming has been added to the requirements)
* goal (out of scope for first implementation, defined in [#71059 Sprint goals](https://community.openproject.org/wp/71059))
* start & end date
* status
* capacity (out of scope for now, defined in [#71060 Sprint Capacity](https://community.openproject.org/wp/71060))
* project\_id (? since Sprints can be shared with multiple projects, this column is not needed!)
* sharing (none, subprojects, system)
* Validations:
* Must have a name
* Sprints cannot have overlapping start & end dates.
* Start date must be earlier (or equal?) than end date
* Maximum 1 sprint can be active at any given time (project validation)
* Association with Work Packages (`sprint_id`)
* but ensure that the table is just called `sprints` - the namespace will be removed later on.
* Connect to work packages (add `sprint_id`), journal
* Sprints can be shared globally, **belong to a project,** or shared with subprojects.
* Similar behaviour to Versions, but with less options.
* Validations
<br>
Notes:
* Namespace it at the beginning - rename it later when the feature is (near) complete
* Come up with a good namespace
* This way, we will not break the existing implementation and can move in smaller steps instead of having to perform one big leap
* Model itself
* name (automated naming has been added to the requirements)
* goal (out of scope for first implementation, defined in [#71059 Sprint goals](https://community.openproject.org/wp/71059))
* start & end date
* status
* capacity (out of scope for now, defined in [#71060 Sprint Capacity](https://community.openproject.org/wp/71060))
* project\_id (? since Sprints can be shared with multiple projects, this column is not needed!)
* sharing (none, subprojects, system)
* Validations:
* Must have a name
* Sprints cannot have overlapping start & end dates.
* Start date must be earlier (or equal?) than end date
* Maximum 1 sprint can be active at any given time (project validation)
* Association with Work Packages (`sprint_id`)