**As** a user following agile methodologies
**I want to** have sprint objects connected to work packages
**so that** I can group work packages by sprints in which they are worked on

**Acceptance criteria**

* Sprints exist in OpenProject. They have

* a Begin of the insertionselection for the projects the sprint is shared with (similar to versions)

* \[Open\] Should the same options be used as for versions?

* aEnd of the insertion name (plain text) Begin of the insertion- same across all shared with projectsEnd of the insertion

* a start and a finish date (dates) Begin of the insertion- same across all shared with projectsEnd of the insertion

* a goal (plain text) Begin of the insertion- different between shared with projectsEnd of the insertion

* a status Begin of the insertion- same across all shared with projectsEnd of the insertion

* Begin of the insertionThe list ofEnd of the insertion Begin of the deletion \[Open\] will thisEnd of the deletion status Begin of the insertionis aEnd of the insertion Begin of the deletion haveEnd of the deletion fixed Begin of the insertionset.

* \[open\] list of status that existEnd of the insertion Begin of the deletion values or can the user administrate (add/remove/order)?End of the deletion

* a capacity Begin of the insertion- different between shared with projectsEnd of the insertion

* story points or days

* \[open\] will we support both from the start? Begin of the insertion

End of the insertion Begin of the deletion

End of the deletion * Begin of the insertionThe user can connectEnd of the insertion a Begin of the insertionwork package to a sprint. A sprintEnd of the insertion Begin of the deletion number of projects they are shared with

* \[Open\] Should the same options be used as for versions?

* Work packagesEnd of the deletion can be Begin of the insertionassociatedEnd of the insertion Begin of the deletion connectedEnd of the deletion to multiple Begin of the insertionwork packages.End of the insertion Begin of the deletion sprints.End of the deletion

* The sprint property can be administrated in the form configuration.

* The property can be used to filter, sort and group in the work package list.

* The property is journaled.

* Begin of the insertion\[open\] How is the order theEnd of the insertion Begin of the deletion \[Open\] it might be sufficient to connect aEnd of the deletion work package Begin of the insertionisEnd of the insertion Begin of the deletion to a single sprint. My \[Jens\] understanding is, that a user should be able to see which sprints a work package has been assigned toEnd of the deletion in Begin of the insertionwithinEnd of the insertion Begin of the deletion its history. We can get that information fromEnd of the deletion the Begin of the deletion journals. It will already be displayed in the activity but we could also show it differently, e.g. in a hover card over the currentEnd of the deletion sprint Begin of the insertionkept. Is this "position" something that is visible to the user?

End of the insertion Begin of the deletion value.

End of the deletion * Begin of the insertion\[Assumption\] Work packagesEnd of the insertion Begin of the deletion If a work packageEnd of the deletion can Begin of the insertiononlyEnd of the insertion be Begin of the insertionassociatedEnd of the insertion Begin of the deletion connectedEnd of the deletion to Begin of the insertionsprints that are shared withEnd of the insertion Begin of the deletion multiple sprints,End of the deletion the Begin of the insertionproject. Even if the userEnd of the insertion Begin of the deletion position within each need to be kept independently. ThereEnd of the deletion is Begin of the insertionallowedEnd of the insertion Begin of the deletion currently a "position" field addedEnd of the deletion to Begin of the insertionsee different sprints, will sprints not shared with the project theEnd of the insertion work Begin of the insertionpackage is in not be eligible for association.

End of the insertion Begin of the deletion packages by backlogs.

End of the deletion * Sprints are exposed via an API.

* Sprints are part of the work package API (resource, form, schema including available values)

* \[open\] is there a list of sprints (filterable by project)?

* This would be necessary for the mobile app

* \[open\] Can sprints be created, updated and deleted via the API?

* Versions are no longer used by the existing Backlogs module. Sprints are used instead.

* Only the left hand part of the backlogs main view will use sprints. Backlogs (currently displayed to the right) will continue to use versions (subject to change later).

* Existing versions used as sprints are migrated.

* The goal is to have an uninterrupted user experience when switching from the pre-sprint state to the post-sprint state.

* A version is migrated Begin of the insertionto a sprintEnd of the insertion if

* the version is configured to be displayed "left" (for "Column in backlog") in Begin of the insertionaEnd of the insertion Begin of the deletion at least oneEnd of the deletion project

* Begin of the insertionBacklogs is active in that project

* End of the insertion the version has at least one work package associated to it in Begin of the insertionthatEnd of the insertion Begin of the deletion aEnd of the deletion project Begin of the insertion

* Name, start & finish date, status and sharingEnd of the insertion Begin of the deletion in which the versionEnd of the deletion is Begin of the insertionmigrated

* \[open\] Mapping of status  

* \[open\] Mapping of sharingEnd of the insertion Begin of the deletion configured to be displayed "left"End of the deletion

* The existing connection from a work package to a version is kept Begin of the insertion

End of the insertion Begin of the deletion

End of the deletion * Begin of the insertionThe reason for this is that we cannot differentiate programatically whether a version was only used as a sprint or if it also served the role of a version.

* End of the insertion Work packages associated to a migrated version are associated to the created sprint.

* The button reading "+ Version" is changed to "+ Sprint" and opens the sprint creation form.

* The "Properties" menu entry in the sprint menu will lead to the sprint edit form.

* The "Wiki" menu entry from the sprint menu is removed

* The "Stories/Tasks" menu will lead to the work package list filtered by the sprint.

* The version form no longer has the "Column in backlogs" select field. Instead a "Used as backlog" checkbox is displayed.

* The limitation on the work package type (which type qualifies as a user story, which one is a task) remains unchanged.

* The task board will be using the sprint

* The burndown chart Begin of the deletion (if it still exists)End of the deletion will be using the sprint


**Technical notes**

* <br>


**Permissions and visibility considerations**

* _To whom is this feature visible?_

* _When is it not visible?_


**Translation considerations**

* _Key terms and phrases in the key Begin of the insertionlanguages_ End of the insertion Begin of the deletion languages_&nbsp;End of the deletion


**Out of scope**

* Having a sprint board (for now)