Content
View differences
Updated by Tobias Dillmann about 1 month ago
Namespace `Agile::Sprint` **As** a \[enter role of user\]
**I want to** \[enter objective\]
**so that** \[enter desired result\]
**Acceptance criteria**
* Name, start & end date, status
<br>
**Technical notes**
* Connect to work packages (add `sprint_id`), journal
* Validations <br>
<br> **Permissions and visibility considerations**
<br>
Notes:
* Namespace it at the beginning - rename it later when the _To whom is this feature is (near) complete
visible?_
* Come up with a good namespace
_When is it not visible?_
**Translation considerations**
* This way, we will not break the existing implementation _Key terms and can move phrases in smaller steps instead of having to perform one big leap
* Model itself
* name (automated naming has been added to the requirements)
* goal (out key languages_&nbsp;
**Out of scope for first implementation, defined in [#71059 Sprint goals](https://community.openproject.org/wp/71059))
scope**
* 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 <br>
_Set the_ **To 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 informed/consulted teams** _field to include all teams necessary to 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`) informed of the changes._
**I want to** \[enter objective\]
**so that** \[enter desired result\]
**Technical notes**
* Validations
<br>
<br>
Notes:
* Namespace it at the beginning - rename it later when the
**Translation considerations**
* Model itself
* name (automated naming has been added to the requirements)
* goal (out
**Out
* status
* capacity (out of scope for now, defined in [#71060 Sprint Capacity](https://community.openproject.org/wp/71060))
* project\_id (? since Sprints can
_Set the_ **To
* sharing (none, subprojects, system)
* Validations:
* Must have a name
* Sprints cannot have overlapping start & end dates.
* Start date must
* Maximum 1 sprint can be active at any given time (project validation)
* Association with Work Packages (`sprint_id`)