Content
View differences
Updated by Attila Dombi 4 months ago
**As** a project administrator \[enter role of user\]
**I want to** be informed whether a Project Initiation Request configurations are incorrect when I go to the settings page \[enter objective\]
**so that** I can fix the configuration issues and others can continue creating projects from PIR templates without any unexpected validation errors. \[enter desired result\]
**As** a user with permissions to create project from templates
**I want to** be informed whether a chosen PIR template's configuration is valid whenever I create a new project
**so that** I can won't create a project that has PIR related validation errors.
<br>
**Acceptance criteria**
* Display a status banner on the Project Initiation Request Wizard Settings page header, with all validation errors the settings have.
<br>
**Technical notes**
* The status banner is shown instantly when the PIR settings are visited <br>
**Permissions and invalid, without requiring to save the settings first.
visibility considerations**
* Suggested layout:
_To whom is this feature visible?_
* <img class="op-uc-image op-uc-image_inline" src="/api/v3/attachments/918922/content">
_When is it not visible?_
**Translation considerations**
* Display a status banner on _Key terms and phrases in the second step key languages_
**Out of the project creation wizard if the chosen PIR template project has configuration errors.
scope**
* Additionally prevent creation of a project from an invalid PIR template project.
* Suggested layout:
<img class="op-uc-image op-uc-image_inline" src="/api/v3/attachments/918923/content">
<br>
* Whenever the user tries
_Set the_ **To be informed/consulted teams** _field to submit the anyway, display an error message too:
<img class="op-uc-image op-uc-image_inline" src="/api/v3/attachments/918924/content">
* Whenever the **Assignee when submitted** field is set (as a Project attribute include all teams necessary to be informed of type User), display the Project attribute of type **User** as a required and validate its presence too. This will ensure the PIR configuration does not end up invalid because of the missing required **User** Project attribute on the new project.
**Technical notes**
* The `Projects::SetAttributesService` initialized with the `Projects::SettingsContract` is a good way to validate PIR configuration for the settings page.
<br> changes._
**I want to** be informed whether a Project Initiation Request configurations are incorrect when I go to the settings page
**so that** I can fix the configuration issues and others can continue creating projects from PIR templates without any unexpected validation errors.
**As** a user with permissions to create project from templates
**I want to** be informed whether a chosen PIR template's configuration is valid whenever I create a new project
**so that** I can won't create a project that has PIR related validation errors.
<br>
**Acceptance criteria**
* Display a status banner on the Project Initiation Request Wizard Settings page header, with all validation errors the settings have.
**Technical notes**
**Permissions
**Translation considerations**
**Out
* Suggested layout:
<img class="op-uc-image op-uc-image_inline" src="/api/v3/attachments/918923/content">
<br>
* Whenever the user tries
_Set the_ **To be informed/consulted teams** _field
<img class="op-uc-image op-uc-image_inline" src="/api/v3/attachments/918924/content">
* Whenever the **Assignee when submitted** field is set (as a Project attribute
**Technical notes**
* The `Projects::SetAttributesService` initialized with the `Projects::SettingsContract` is a good way to validate PIR configuration for the settings page.
<br>