Content
View differences
Updated by Alexander Coles 13 days ago
**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**
* ###72945 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._
**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**
* ###72945 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._