Content
View differences
Updated by Dominic Bräunlein 10 days ago
**As** a project manager
**I want to** have important project documents archived at a central place
**so that** I can access them when needed
**Acceptance criteria**
* An optional project folder setting for automatically managed project folders that enables the project document archive is available
<img class="op-uc-image op-uc-image_inline" src="/api/v3/attachments/825761/content">
* When the "project archive" is enabled on a project folder, a managed subfolder is created in the automatically managed project folder
* The folder name is unclear. Suggestion: "Project artefact archive"
* This archive folder is read only for all users (and admins?)
* The archive folder includes a subfolder named "Project initiation". (At a later time there will be sibling folders for each project phase)
<br>
**Workflow**
* Prerequisite
* Project artefact archive is enabled and created
* Work package type &quot;Project approval&quot; is created
* Status: &quot;submitted&quot;, &quot;approved&quot;, &quot;rejected&quot;
<br>
* Trigger
* The user submits the project initiation request
<br>
* \-> A pdf is created based on the project initiation request
* \-> PDF is saved as "Project Folder" -> "Project artefact archive" -> "Project initiation" -> "Project initiation request.pdf"
<br>
* \-&gt; A work package of type &quot;Project approval&quot; is created
* The status us set to &quot;submitted&quot;
* And a File Link to the pdf is created
<br>
**Technical notes**
* <br>
**Permissions and visibility considerations**
* _To whom is this feature visible?_
* _When is it not visible?_
**Translation considerations**
* _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._
**I want to** have important project documents archived at a central place
**so that** I can access them when needed
**Acceptance criteria**
* An optional project folder setting for automatically managed project folders that enables the project document archive is available
<img class="op-uc-image op-uc-image_inline" src="/api/v3/attachments/825761/content">
* When the "project archive" is enabled on a project folder, a managed subfolder is created in the automatically managed project folder
* The folder name is unclear. Suggestion: "Project artefact archive"
* This archive folder is read only for all users (and admins?)
* The archive folder includes a subfolder named "Project initiation". (At a later time there will be sibling folders for each project phase)
<br>
**Workflow**
* Prerequisite
* Project artefact archive is enabled and created
* Status: &quot;submitted&quot;, &quot;approved&quot;, &quot;rejected&quot;
<br>
*
* The user submits the project initiation request
<br>
* \-> A pdf is created based on the project initiation request
* \-> PDF is saved as "Project Folder" -> "Project artefact archive" -> "Project initiation" -> "Project initiation request.pdf"
<br>
* \-&gt; A work package of type &quot;Project approval&quot; is created
* The status us set to &quot;submitted&quot;
* And a File Link to the pdf is created
**Technical notes**
* <br>
**Permissions and visibility considerations**
* _To whom is this feature visible?_
* _When is it not visible?_
**Translation considerations**
* _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._