# Feature AGILE-33 - Sprints manageable from work package full/split view

Project: Stream agile
Status: closed
URL: https://community.openproject.org/work_packages/AGILE-33

## Planning

| Attribute | Value |
| --- | --- |
| Date |  |
| Priority | Medium |
| Target versions | 17.3.0 |
| Sprint |  |
| Backlog bucket |  |
| Votes |  |
| List |  |
| Roadmap |  |
| Relevance |  |

## OPEN POINTS / FEEDBACK

| ID | Subject | Status | Decision |
| --- | --- | --- | --- |
| AGILE-74 | Is the default edit field behaviour on the work package table and full/split view acceptable at first | decided | Using the default in place editor behaviour currently present on the work package view is acceptable. |

## Features and Chunks

_No work packages_

## Bugs and other work packages

| ID | Type | Subject | Status | Assignee | Target versions | Spent time | Module |
| --- | --- | --- | --- | --- | --- | --- | --- |
| AGILE-159 | Bug | "Sprint" column is missing on wp table | rejected |  | 17.3.0 |  | Modules and project features / Backlogs, Modules and project features / Work packages |

## Technical Details

| Attribute | Value |
| --- | --- |
| Module |  |
| Feature Flag |  |
| Requires doc change | No |
| Enterprise plan |  |

## Details

| Attribute | Value |
| --- | --- |
| Pull preview |  |
| Mockups |  |
| Accessibility | No |

## People

| Attribute | Value |
| --- | --- |
| Assignee |  |
| Accountable |  |
| Product manager |  |
| Developers | Jens Ulferts |
| Designer | Parimal Satyal |
| Ordered by |  |
| Signed off by |  |
| Interest by |  |

## Estimates and progress

| Attribute | Value |
| --- | --- |
| PD (min) |  |
| PD (max) |  |
| Work |  |
| Labor costs |  |

## Description

**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 <mention class="mention" data-id="70496" data-type="work_package" data-text="#70496">#70496</mention> 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 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.

  - 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