**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 selection for the projects the sprint is shared with (similar to versions). The options are:

* none - not shared at all. The sprint is available in the project it is defined in.

* subprojects - The sprint is available in the project it is defined in and its subprojects.

* all projects/systemwide - The sprint is available in all projects of the instance.

* a name (plain text) - same across all shared with projects

* a start and a finish date (dates) - same across all shared with projects

* a Begin of the deletion goal (plain text) - different between shared with projects

* aEnd of the deletion status - same across all shared with projects

* The list of status is a fixed set.

* \[open\] list of status that exist Begin of the insertion

End of the insertion Begin of the deletion

End of the deletion * Begin of the deletion a capacity - different between shared with projects

* story points or days

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

* End of the deletion The user can connect a work package to a sprint. A sprint can be associated to multiple work packages.

* Begin of the insertionFor now, this is only possible withinEnd of the insertion Begin of the deletion The sprint property can be administrated inEnd of the deletion the Begin of the insertionbacklogs module. <mention class="mention" data-id="71061" data-type="work_package" data-text="##71061">##71061</mention> will addEnd of the insertion Begin of the deletion form configuration and be displayed in the project list and in the work package view.

* Sprints can be selected usingEnd of the deletion an Begin of the insertioneditableEnd of the insertion Begin of the deletion autocompleter. All sprints shared with the project are selectable (grouped by project) regardless of whether the user can see the project the sprint is defined in.

* The property can be used to filter, sortEnd of the deletion and Begin of the insertionmanageable &quot;sprint&quot; field toEnd of the insertion Begin of the deletion group in theEnd of the deletion work Begin of the insertionpackages.End of the insertion Begin of the deletion package list.End of the deletion

* The Begin of the insertion&quot;sprint&quot;End of the insertion property is journaled.

* Begin of the deletion \[open\] How is the order the work package is in within the sprint kept. Is this &amp;quot;position&amp;quot; something that is visible to the user?

* \[Assumption\]End of the deletion Work packages Begin of the insertionhave a &quot;position&quot; fieldEnd of the insertion Begin of the deletion can only be associatedEnd of the deletion to Begin of the insertionrememberEnd of the insertion Begin of the deletion sprints that are shared withEnd of the deletion the Begin of the insertionorder withinEnd of the insertion Begin of the deletion project. Even ifEnd of the deletion the Begin of the insertionsprint. This field already exists andEnd of the insertion Begin of the deletion userEnd of the deletion is Begin of the insertionleft untouched.End of the insertion Begin of the deletion allowed to see different sprints, will sprints not shared with the project the work package is in not be eligible for association.End of the deletion

* Sprints Begin of the insertionwill later on beEnd of the insertion Begin of the deletion areEnd of the deletion exposed via an Begin of the insertionapi (see #71058End of the insertion Begin of the deletion 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, updatedEnd of the deletion and Begin of the insertion#71061)

End of the insertion Begin of the deletion deleted via the API?

End of the deletion * 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).

* Begin of the insertionThe button reading &quot;+ Version&quot; is changed to &quot;+ Sprint&quot; and opens the sprint creation form.

* The &quot;Properties&quot; menu entry in the sprint menu will lead to the sprint edit form.

* The &quot;Wiki&quot; menu entry from the sprint menu is removed

* The &quot;Stories/Tasks&quot; menu item will be removed (later on possibly readded by #71061).

* The version form no longer has the &quot;Column in backlogs&quot; select field. Instead a &quot;Used as backlog&quot; 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 will be using the sprint


**Technical notes**

* Migration considerations:

* End of the insertion 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 to a sprint if

* the version is configured to be displayed &quot;left&quot; (for &quot;Column in backlog&quot;) in a project

* Backlogs is active in that project

* the version has at least one work package associated to it in that project

* Name, start &amp; finish date, status Begin of the deletion and sharingEnd of the deletion is migrated

* \[open\] Mapping of status &nbsp; Begin of the insertion

* The project the sprint is created in and the sharing it has:

* The project furthest down the hierarchy with the sharing set to &quot;subprojects&quot; - if the sprint is used in multiple projects and they share the same hierarchyEnd of the insertion

* Begin of the insertionJust the project where the sprint is used with theEnd of the insertion Begin of the deletion \[open\] Mapping ofEnd of the deletion sharing Begin of the insertionset to &quot;none&quot; - if the sprint is only used in a single project.

* The project having the &quot;system-wide&quot; version defined with the status set to systemwide - for a version shared system-wide.End of the insertion

* The existing connection from a work package to a version is kept

* The 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. Begin of the insertion

End of the insertion Begin of the deletion

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

End of the insertion Begin of the deletion

End of the deletion * Begin of the insertionA journalEnd of the insertion Begin of the deletion The button reading &amp;quot;+ Version&amp;quot;End of the deletion is Begin of the insertionwritten byEnd of the insertion Begin of the deletion changed to &amp;quot;+ Sprint&amp;quot; and opensEnd of the deletion the Begin of the insertionsystem user informing aboutEnd of the insertion Begin of the deletion sprint creation form.

* The &amp;quot;Properties&amp;quot; menu entry inEnd of the deletion the Begin of the insertionshift from versionEnd of the insertion Begin of the deletion sprint menu will leadEnd of the deletion to Begin of the deletion theEnd of the deletion sprint Begin of the insertion- no notification is sent

End of the insertion Begin of the deletion edit form.

End of the deletion * Begin of the insertion\[open\] Phrasing ofEnd of the insertion Begin of the deletion The &amp;quot;Wiki&amp;quot; menu entry fromEnd of the deletion the Begin of the insertionmessage

End of the insertion Begin of the deletion sprint menu is removed

End of the deletion * Begin of the insertionPermissions needEnd of the insertion Begin of the deletion The &amp;quot;Stories/Tasks&amp;quot; menu will leadEnd of the deletion to Begin of the insertionbe migrated (see below)


**Permissions and visibility considerations**

End of the insertion Begin of the deletion the work package list filtered by the sprint.

End of the deletion * Begin of the insertionManage sprints

End of the insertion Begin of the deletion The version form no longer has the &amp;quot;Column in backlogs&amp;quot; select field. Instead a &amp;quot;Used as backlog&amp;quot; checkbox is displayed.

End of the deletion * Begin of the insertionAllows adding and updating sprintsEnd of the insertion Begin of the deletion The limitation on the work package type (which type qualifies as a user story, which one is a task) remains unchanged.End of the deletion

* Begin of the insertionReplacesEnd of the insertion Begin of the deletion The task board will be usingEnd of the deletion the Begin of the insertioncurrent &quot;Update sprints&quot;

End of the insertion Begin of the deletion sprint

End of the deletion * Begin of the insertionView sprints

End of the insertion Begin of the deletion The burndown chart will be using the sprint


**Technical notes**

End of the deletion * Begin of the insertion\[open\] copied from the epic. WhatEnd of the insertion Begin of the deletion &lt;br&gt;


**Permissions and visibility considerations**

* _To whomEnd of the deletion is Begin of the insertionthe permission necessary for? Seeing the sprint is definitely necessary whenever backlogs is to be used.

End of the insertion Begin of the deletion this feature visible?_

End of the deletion * Begin of the insertion\[open\] ThereEnd of the insertion Begin of the deletion _WhenEnd of the deletion is Begin of the insertionan &quot;Assign versions&quot; permission that is required when wanting to connect work packages and versions. Do we want the same for sprints? This would allow a role like a &quot;Product owner&quot; in Scrum.End of the insertion Begin of the deletion it not visible?_End of the deletion


**Translation considerations**

* _Key terms and phrases in the key languages_


**Out of scope**

* Having a sprint board (for now)