Content
View differences
Updated by Parimal Satyal 2 months ago
**Context**
We **As** a \[enter role of user\]
**I want project admins who enable the Backlogs module to immediately see the 'Sprint' and 'Story point' fields in the work package details page, without having to think about manual form configuration per type. to** \[enter objective\]
**so that** \[enter desired result\]
**Acceptance criteria**
* Add a project setting that allows users to exclude certain types to be excluded from sprints and backlogs
* _\[phrasing to be defined\]_
* Make the 'Sprint' and 'Story points' fields global and automatically visible on the work package details page when the Backlog module is enabled
* Except for types excluded from sprints and backlogs
<br>
**Technical notes**
* The 'Story points' field is not behind a permission check; 'Sprints' is. <br>
**Permissions and visibility considerations**
* _See technical notes_ _To whom is this feature visible?_
* _When is it not visible?_
**Translation considerations**
* <br> _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._
We
**I
**so that** \[enter desired result\]
**Acceptance criteria**
* Add a project setting that allows users to exclude certain types to be excluded from sprints and backlogs
* _\[phrasing to be defined\]_
* Make the 'Sprint' and 'Story points' fields global and automatically visible on the work package details page when the Backlog module is enabled
* Except for types excluded from sprints and backlogs
* The 'Story points' field is not behind a permission check; 'Sprints' is.
**Permissions and visibility considerations**
* _See technical notes_
* _When is it not visible?_
**Translation considerations**
* <br>
**Out of scope**
* <br>
_Set the_ **To be informed/consulted teams** _field to include all teams necessary to be informed of the changes._