# Feature AGILE-31 - Sprint goals

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

## Planning

| Attribute | Value |
| --- | --- |
| Date |  |
| Priority | High |
| Target versions | 17.6.0 |
| Sprint | Sprint 5 |
| Backlog bucket |  |
| Votes |  |
| List |  |
| Roadmap |  |
| Relevance |  |

## OPEN POINTS / FEEDBACK

_No work packages_

## Use cases

_No work packages_

## Features and Chunks

_No work packages_

## Bugs and other work packages

| ID | Type | Subject | Status | Assignee | Target versions | Spent time | Module |
| --- | --- | --- | --- | --- | --- | --- | --- |
| AGILE-301 | Bug | Selecting a date wipes goal text in Sprint dialog | closed |  | 17.6.0 |  | Modules and project features / Backlogs |

## Technical Details

| Attribute | Value |
| --- | --- |
| Module | Modules and project features / Backlogs |
| Feature Flag |  |
| Requires doc change | Yes |
| Enterprise plan |  |

## Details

| Attribute | Value |
| --- | --- |
| Pull preview |  |
| Mockups | https://www.figma.com/design/yRewu4Y5nuWCa8aMM3DFw3/Agile--Sprints-and-Backlogs?node-id=3475-38843 |
| Accessibility | No |

## People

| Attribute | Value |
| --- | --- |
| Assignee |  |
| Accountable |  |
| Product manager |  |
| Feature Lead |  |
| Developers | Alexander Coles |
| Designer | Parimal Satyal |
| Ordered by |  |
| Signed off by |  |
| Interest by |  |

## Estimates and progress

| Attribute | Value |
| --- | --- |
| PD (min) |  |
| PD (max) |  |
| Work | 3d 0h · Σ 3d 0h |
| Labor costs |  |

## Description

**As** a product owner  
**I want to** define and communicate the goal of the sprint to the team in a concise manner  
**so that** the intend of the sprint is clear.

**Acceptance criteria**

  - Sprints have a goal (plain text) per project

  - The goal is administrated in the new/edit sprint modal
    
      - If the sprint is not shared:
        
          - The "Sprint goal" field is visibly a part of the form together with the "Name" and "Date" fields
    
      - If the sprint is shared, The "Sprint goal" field:
        
          - is separated by a horizontal bar from the other fields.
        
          - has a suffix at the label reading "(for this project)"
        
          - has a caption "The sprint goal is unique to this project and is not shared with other projects also using this sprint."

  - Shared sprints display a banner at the top of the modal. The permissions the user has define what is displayed and whether the fields are active. The relevant permission is `create_sprints` :
    
      - Permission in sharing and shared with project: An info notification is displayed reading "This is a shared sprint. Modifications will be reflected in all projects using it.". All Fields are active.
    
      - Permission in sharing but not in shared with project: An info notification is displayed reading "This is a shared sprint. Modifications will be reflected in all projects using it.". Name and date fields are active, goal is inactive.
    
      - Permission not in sharing but in shared with project: Warning notification is displayed reading "This is a shared sprint. You do not have the necessary permissions to edit it." Only the goal field is active.

  - If a goal is set, it is displayed in the header of the sprint on the "Backlog and sprints" page.  

  - ~~The goal property is part of the API.~~

**Permissions and visibility considerations**

  - See AC

**Out of scope**

  - <mention class="mention" data-id="72945" data-type="work_package" data-text="###72945">###72945</mention> is expected to be done

  - PATCH API support

*Set the* **To be informed/consulted teams** *field to include all teams necessary to be informed of the changes.*
