Content
View differences
Updated by Dominic Bräunlein 9 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**
* UI
* An admin can select a optional project storage to be used folder setting for automatically managed project folders that enables the project artefact document archive
is available
* Optionally: A file name can be defined
* Is this part of this feature?
<br>
* Upload Service / Command When the &quot;project archive&quot; is enabled on a project folder, a managed subfolder is created in the automatically managed project folder
* The upload command takes following arguments
* File folder name
* File Path
* Read-only flag
* File
* When the file path does not exist yet, the folders are created on demand is unclear. Suggestion: &quot;Project artefact archive&quot;
* The file This archive folder is uploaded read only for all users (and admins?)
* File names and The archive folder includes a subfolder named &quot;Project initiation&quot;. (At a later time there will be sibling folders are modified to work with the storage's naming restrictions. for each project phase)
<br>
**Workflow**
* Prerequisite
* Project artefact archive is enabled in the wizard settings and created
* 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>
<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**
* UI
* An admin can select a
* Is this part of this feature?
<br>
* Upload Service / Command
* The upload command takes following arguments
* File
* File Path
* Read-only flag
* File
* When the file path does not exist yet, the folders are created on demand
* The file
* File names and
<br>
**Workflow**
* Prerequisite
* Project artefact archive is enabled in the wizard settings
* 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>
<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._