Content
View differences
Updated by Jens Ulferts 12 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.
* Clarification - Opposed to Versions, sprints will simply be displayed with their name. There is no indication on the project they are defined in. The reason for this is that all sprints within a project are from the same source.
* 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>
**Permissions and visibility considerations**
* The `view_sprints` permission is required to see the sprint
* The `manage_sprint_items` permission is required to change the sprint
**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
* For now, this follows the same UI/UX used by the other list typed attributes.
* Clarification - Opposed to Versions, sprints will simply be displayed with their name. There is no indication on the project they are defined in. The reason for this is that all sprints within a project are from the same source.
* <mention class="mention" data-id="72227" data-type="work_package" data-text="###72227">###72227</mention>
**Permissions and visibility considerations**
* The `view_sprints` permission is required to see the sprint
* The `manage_sprint_items` permission is required to change the sprint