Content
View differences
Updated by Robin Wagner about 6 years ago
**As** a project admin
**I want** to archive my project myself
**so that** I don’t need to ask the admin to do that.
**Acceptance criteria**
*
- Archive link in project settings
*
- Archive only possible for users having the “archive\_project” permission
* Add "archive project" permission as global role
* 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 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” role in default data receives “archive\_project” permission by default
**Out of scope**
*
- Ability to unarchive a project for a non admin.
**Wireframes**
*
- See attachments
**Acceptance criteria**
*
-
*
-
* Add "archive project" permission as global role
* Alternatively set as project permission:
*
-
*
-
*
-
*
-
**Out of scope**
*
-
**Wireframes**
*
-