Content
View differences
Updated by Rosanna Sibora 6 days ago
**As** an agile user
**I want to** the necessary fields (i.e. story points) and only the allowed types to be offered in the "New work package" modal
**so that** I can easily create work packages with all the information necessary and avoid erroneously creating a work package that is not displayed.
**Acceptance criteria**
* The "New work package" modal has the "Story points" field
* The field is only displayed if the form configuration for the currently selected type has "Story points" configured
* The "New work package" modal already has a type selection. The available types are limited to those:
* Active in the project AND
* Active in backlogs according to the "Excluded work package types" setting in the backlogs project settings (see <mention (see <mention class="mention" data-id="71305" data-type="work_package" data-text="##71305" data-display-id="71305">##71305</mention>) data-text="##71305">##71305</mention>)
* \[open\] should this limitation be applied to all containers (sprint/bucket/inbox)? Specification states that work packages of other types should be displayed in the sprint if the user moved them into it. The rational might also be applied to explicitly creating such work packages.
**Technical notes**
* This will require implementing a backlog specific wp create modal.
**Permissions and visibility considerations**
* No changes
<br>
**I want to**
**so that** I can
**Acceptance criteria**
* The "New work package" modal
* The field is only displayed if the form configuration for the currently selected type has "Story points" configured
* The "New work package" modal
* Active in the project AND
* Active in backlogs according to the "Excluded work package types" setting in the backlogs project settings (see <mention
* \[open\] should this limitation be applied to all containers (sprint/bucket/inbox)? Specification states that work packages of other types should be displayed in the sprint if the user moved them into it. The rational might also be applied to explicitly creating such work packages.
**Technical notes**
* This will require implementing a backlog specific wp create modal.
**Permissions and visibility considerations**
* No changes
<br>