Content
View differences
Updated by Jens Ulferts 9 days ago
**As** a team member in a scrum project
**I want to** see and administrate the "Sprint" column on work packages.
**so that** I can use the full work package capabilities on that field
**Acceptance criteria**
* "Sprint" becomes an attribute visible on the work package. It shows the name of the sprint the work package is assigned to.
* It is already introduced by #70496 but the field hasn't been exposed
* The sprint property can be administrated in the form configuration and be displayed in the project list and in the work package view.
* Sprints can be selected using an 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.
* For now, this follows the same UI/UX used by the other list typed attributes.
* \[open\] How to handle sprints versions shared from projects the user is not allowed to see in the autocompleter? The name would need to be hidden at least. Maybe aggregate from all those projects into a single group. Check that this is consistent with versions.
* The property can be used to filter, sort and group in the work package list.
* Sprints are part of the work package API (resource, form, schema including available values)
* <mention class="mention" data-id="72227" data-type="work_package" data-text="###72227">###72227</mention>
* Sprints have a "Stories/Tasks" (\[open\] better name) menu item that forward the user to the work package list filtered by the sprint.
* Sprints can be changed in the bulk action pages of work packages
**Technical notes**
* The field is only visible if backlogs is enabled.
* Possibly a permission to see the sprint on the work package
* Possibly a permission to govern who is allowed to change the sprint
**Permissions and visibility considerations**
* _To whom is this feature visible?_
* _When is it not visible?_
**Translation considerations**
* _Key terms and phrases in the key languages_
**Out of scope**
* <br>
_Set the_ **To be informed/consulted teams** _field to include all teams necessary to be informed of the changes._
**I want to** see and administrate the "Sprint" column on work packages.
**so that** I can use the full work package capabilities on that field
**Acceptance criteria**
* "Sprint" becomes an attribute visible on the work package. It shows the name of the sprint the work package is assigned to.
* It is already introduced by #70496 but the field hasn't been exposed
* The sprint property can be administrated in the form configuration and be displayed in the project list and in the work package view.
* Sprints can be selected using an 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.
* For now, this follows the same UI/UX used by the other list typed attributes.
* \[open\] How to handle sprints
* The property can be used to filter, sort and group in the work package list.
* Sprints are part of the work package API (resource, form, schema including available values)
* <mention class="mention" data-id="72227" data-type="work_package" data-text="###72227">###72227</mention>
* Sprints can be changed in the bulk action pages of work packages
**Technical notes**
* The field is only visible if backlogs is enabled.
* Possibly a permission to see the sprint on the work package
* Possibly a permission to govern who is allowed to change the sprint
**Permissions and visibility considerations**
* _To whom is this feature visible?_
* _When is it not visible?_
**Translation considerations**
* _Key terms and phrases in the key languages_
**Out of scope**
* <br>
_Set the_ **To be informed/consulted teams** _field to include all teams necessary to be informed of the changes._