**As** a user following scrum methodology
**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, and easily reorganise sprints by moving items between them (and the backlog)

**Acceptance criteria**

* Sprints exist in OpenProject. They have

* a Begin of the deletion 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 (use case: for SAFe ART users will create a project on the portfolio or program level and will be able to pass it on to all subprojects)

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

* aEnd of the deletion name (plain text) - same across all shared with projects

* we automatically set a name when a user creates a sprint bucket "Sprint 1"

* user can overwrite the name

* for each new bucket we count +1 based on the latest sprint bucket, copying the text part of the sprint name used for the latest sprint, e.g. the one edited by the user

* if user removed the digits in all sprint names in planning, we stop counting

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

* a status - same across all shared with projects. The list of status is a fixed set:

* In planning

* Active

* Completed

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

* For now, this is only possible within the Backlog module. <mention class="mention" data-id="71061" data-type="work_package" data-text="##71061">##71061</mention> will add an editable and manageable &quot;sprint&quot; field to work packages.

* The &quot;sprint&quot; property is journaled.

* Work packages have a &quot;position&quot; field to remember the order within the sprint. This field already exists and is left untouched.

* Sprints will later on be exposed via an API (see #71058 and #71061)

* 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).

* The button reading &quot;+ Version&quot; is changed to &quot;+ Sprint&quot; and [opens the sprint creation form](https://www.figma.com/proto/yRewu4Y5nuWCa8aMM3DFw3/Agile--Sprints-and-Backlogs?node-id=416-9277&p=f&t=6CQJQUzsbb0dlgvl-0&scaling=min-zoom&content-scaling=fixed&page-id=142%3A13148) (the header of the modal: &quot;Create sprint&quot;).

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

* Will be renamed to &quot;Edit sprint&quot;

* 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 Begin of the insertionunchanged (for now).End of the insertion Begin of the deletion unchanged.End of the deletion

* The task board will be using the sprint

* The burndown chart will be using the sprint Begin of the insertion

* Sprints can be shared

* Sharing is a project-level setting, not a sprint-level one (like with versions at the moment). Users can choose in the project settings:

* Share sprints - Sprints can be created in this project. All those created sprints are shared to either (user selection):

* All projects

* Subprojects

* No sharing - Sprints can be created in this project. None of the created sprints are shared with any other project

* Receive shared sprints - No sprints can be created within this project. Instead shared sprints are used.

* Status, Name and dates of a sprint are also shared (can&#39;t be different per project)

* Only one project can &quot;Share with all projects&quot;.

* \[open\] Possibly, define systemwide sprints not within a project but outside of it. It could then be guarded by a global permission.

* Sprint sharing is only possible if enabled first in the instance administration

* Only sprints from one sharing project are received. If there are multiple projects from which a receiving project could take its sprints the order of priority is as follows (lowest to highest priority):

* All projects sharing

* Subproject sharing higher up the ancestor chain

* Subproject sharing lower down the ancestor chain&nbsp;


End of the insertion Begin of the deletion


End of the deletion **Technical notes**

* Migration considerations:

* Existing versions used as sprints are migrated (read copied).

* 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 insertionareEnd of the insertion Begin of the deletion isEnd of the deletion migrated

* Mapping of status

* Version open -&gt; Sprint in planning

* Version locked or closed -&gt; Sprint completed

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

* Begin of the insertion\[open\] NeedsEnd of the insertion Begin of the deletion The project furthest down the hierarchy with the sharing setEnd of the deletion to Begin of the insertionbeEnd of the insertion Begin of the deletion &quot;subprojects&quot; - if the sprint is used in multiple projects and they share the same hierarchy

* Just the project where the sprint is used with the sharing set to &quot;none&quot; - if the sprint is only used in a single project.

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

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

* The reason for this is that we cannot differentiate programmatically whether a version was only used as a sprint or if it also served the role of a version.

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

* A journal is written by the system user informing about the shift from version to sprint - no notification is sent

* \[open\] Phrasing of the message

* Permissions need to be Begin of the insertionmigrated:

* View master backlog → View sprints

* View taskboards → View sprints

* Select done statuses (remove later on or remove the functionality with it)

* Update sprints → _(remove, but to be confirmed)_

* Manage versions  → Create sprints (?)

* Assign versions → (split) Manage sprint items


End of the insertion Begin of the deletion migrated (see below)


End of the deletion **Permissions and visibility considerations**

* Begin of the insertionBacklogs needs to be activated for any ofEnd of the insertion Begin of the deletion If backlogs is activated, all users havingEnd of the deletion the Begin of the insertionpermissions toEnd of the insertion Begin of the deletion &quot;ViewEnd of the deletion work Begin of the deletion packages&quot; permission can access backlogs and can see the sprints and backlogs and their contents.End of the deletion

* Begin of the insertionViewEnd of the insertion Begin of the deletion ManageEnd of the deletion sprints

* Allows Begin of the insertionaccessing backlogs

* Allows seeingEnd of the insertion Begin of the deletion adding and updatingEnd of the deletion sprints Begin of the insertionon work packages (once that feature is developed)End of the insertion

* Begin of the insertionAllows accessingEnd of the insertion Begin of the deletion ReplacesEnd of the deletion the Begin of the insertionburndown chartEnd of the insertion Begin of the deletion current &quot;Update sprints&quot;End of the deletion

* Begin of the insertionThis permission isEnd of the insertion Begin of the deletion Allows startingEnd of the deletion a Begin of the insertiondependency for all the other permissions below. This is coded in.

End of the insertion Begin of the deletion new sprint

End of the deletion * Begin of the insertionCreate sprints

End of the insertion Begin of the deletion <mention class="mention" data-id="71386" data-type="work_package" data-text="###71386">###71386</mention>

End of the deletion * Allows Begin of the insertionadding/updating/deleting sprints including name, dates but excluding status. Allows to configure whether to receive or to not receive shared sprints in the project configuration.

* Start/completeEnd of the insertion Begin of the deletion adding and removing work packages (withinEnd of the deletion sprint Begin of the insertion

End of the insertion Begin of the deletion buckets)

End of the deletion * Allows Begin of the insertionchangingEnd of the insertion Begin of the deletion definingEnd of the deletion the Begin of the insertionstatusEnd of the insertion Begin of the deletion orderEnd of the deletion of Begin of the deletion work packages withinEnd of the deletion the sprint Begin of the insertion

End of the insertion Begin of the deletion bucket

End of the deletion * Begin of the insertionManageEnd of the insertion Begin of the deletion ~~Start and completeEnd of the deletion sprint Begin of the insertionitemsEnd of the insertion Begin of the deletion (use case: this role would be relevant for SAFe teams or large organizations where sprints should be managed centrally. Interesting especially while sharing sprints.)~~End of the deletion

* Begin of the insertionAllows adding and removing fromEnd of the insertion Begin of the deletion ~~Allows startingEnd of the deletion a Begin of the insertionsprint, and re-ordering of items

* Share sprint

* Allows to configure sharing (all projects or sub-projects) in the project configurationEnd of the insertion Begin of the deletion new sprint~~End of the deletion

* Begin of the insertionDepends on the user having the &quot;Create sprints&quot; permission.End of the insertion Begin of the deletion ~~Allows completing an active sprint~~End of the deletion


**Translation considerations**

* _Key terms and phrases in the key languages_


**Out of scope**

* Having a sprint board (for now)