Content
View differences
Updated by Parimal Satyal over 3 years ago
**As** a project member
**I want** to archive my project myself
**so that** I don’t need to ask the admin to do that.
**Acceptance criteria**
* Archiving is Archive link in project settings
* Archive only possible by for users that have having the “archive\_project” permission
* "Archive" button in Project settings for all roles that have the "archive\_project" permission
* "Archive Add "archive project" permission can either be:
* added as global role or
* Alternatively set as project permission:
* In case subprojects are present:
* If the user has the “archive\_project” permission in all of the subprojects, the user is notified (a statement listing all the projects that are going to be archived) and asked again whether he wants to archive all the sub-projects projects
* In case the user lacks the “archive\_project” permission in any of the subprojects, the user is notified that archiving is currently impossible as he is lacking permissions in one of the subprojects.
* **Error text:** "You do not have the necessary permissions required to archive all sub-projects. Please contact your project administrator."
* ~~“manager” “manager” role in default data receives “archive\_project” permission by default~~
**Open questions**
* What does the "manager" role refer to, in a default OP installation? (Since we cannot control which custom roles are created in each instance)
* Does adding the permission _as_ a global role mean adding it _to_ a global role, as in, making it available to that role?
**Out of scope**
* Ability to unarchive a project for a non admin.
**Wireframes**
* See attachments
**I want** to archive my project myself
**so that** I don’t need to ask the admin to do that.
**Acceptance criteria**
* Archiving is
* Archive
* "Archive" button in Project settings for all roles that have the "archive\_project" permission
* "Archive
* added as global role or
* In case subprojects are present:
* If the user has the “archive\_project” permission in all of the subprojects, the user is notified (a statement listing all the projects that are going to be archived) and asked again whether he wants to archive all the sub-projects
* In case the user lacks the “archive\_project” permission in any of the subprojects, the user is notified that archiving is currently impossible as he is lacking permissions in one of the subprojects.
* ~~“manager”
**Open questions**
* What does the "manager" role refer to, in a default OP installation? (Since we cannot control which custom roles are created in each instance)
* Does adding the permission _as_ a global role mean adding it _to_ a global role, as in, making it available to that role?
**Out of scope**
* Ability to unarchive a project for a non admin.
**Wireframes**
* See attachments