Content
View differences
Updated by Robin Wagner over 5 years ago
# User Story
As an project manager
**I want** to assign work packages to placeholder users
**so** that I can create a work plan that include (placeholder) users that must not have access to the system (yet).
# Acceptance criteria:
## 1: New user type "placeholder user"
* We introduce the concept of "placeholder users" to user objects.
* For placeholder users only the username is mandatory. The email address can not be added.
## 2 - 5: Out of scope for 11.2
* Will be part of #36308.
## 6: New permissions to create placeholder users
* Invite new placeholder user to a project.
* 1: Create new placeholder user: New global permission (independent of a project scope) "Create placeholder users".
* Will be granted to most users. users at AMG.
<figure class="image op-uc-figure" style="width:28.08%;"><div class="op-uc-figure--content"><img class="op-uc-image" src="/api/v3/attachments/19710/content"></div></figure>
* 2: Add an existing placeholder user to a project: New project permission "Manage placeholder users".
* Will be granted to most users. users at AMG.
<figure class="image op-uc-figure" style="width:57.88%;"><div class="op-uc-figure--content"><img class="op-uc-image" src="/api/v3/attachments/19709/content"></div></figure>
* Invite new users to a project
* 1: Create new user: New global permission (independent of a project scope) "Create new user ".
* 2: Add a user to a project: Existing project permission "Manage members".
## 7: Update seed data
* Out of scope for 11.2 (will be part of #36308).
## 8: Administration and user contingents in subscription plans
* Show placeholder users in user administration table with an extra column "Placeholder" with a checkbox icon for placeholder users.
* No filtering on that attribute.
* Placeholder users do not count for user limits. So if somebody has a 5 users plan and has 1 user and 10 placeholder users then in terms of the subscription they count as 1.
# Out of scope
The following features are not included in the effort estimated. They are to be specified in a separate work package:
* Guest users (they are only added to the Prototyp to ensure consistency).
* We will most likely not implement a switching between the user types (e.g. make a placeholder a normal user). Instead we believe that batch editing work packages and assigning them to a real user is the cleaner approach.
* Menu items for work packages in the header navigation (the mechanism to decided which work package type are displayed in the menu).
As an project manager
**I want** to assign work packages to placeholder users
**so** that I can create a work plan that include (placeholder) users that must not have access to the system (yet).
# Acceptance criteria:
## 1: New user type "placeholder user"
* We introduce the concept of "placeholder users" to user objects.
* For placeholder users only the username is mandatory. The email address can not be added.
## 2 - 5: Out of scope for 11.2
* Will be part of #36308.
## 6: New permissions to create placeholder users
* Invite new placeholder user to a project.
* 1: Create new placeholder user: New global permission (independent of a project scope) "Create placeholder users".
* Will be granted to most users.
<figure class="image op-uc-figure" style="width:28.08%;"><div class="op-uc-figure--content"><img class="op-uc-image" src="/api/v3/attachments/19710/content"></div></figure>
* 2: Add an existing placeholder user to a project: New project permission "Manage placeholder users".
* Will be granted to most users.
<figure class="image op-uc-figure" style="width:57.88%;"><div class="op-uc-figure--content"><img class="op-uc-image" src="/api/v3/attachments/19709/content"></div></figure>
* Invite new users to a project
* 1: Create new user: New global permission (independent of a project scope) "Create new user ".
* 2: Add a user to a project: Existing project permission "Manage members".
## 7: Update seed data
* Out of scope for 11.2 (will be part of #36308).
## 8: Administration and user contingents in subscription plans
* Show placeholder users in user administration table with an extra column "Placeholder" with a checkbox icon for placeholder users.
* No filtering on that attribute.
* Placeholder users do not count for user limits. So if somebody has a 5 users plan and has 1 user and 10 placeholder users then in terms of the subscription they count as 1.
# Out of scope
The following features are not included in the effort estimated. They are to be specified in a separate work package:
* Guest users (they are only added to the Prototyp to ensure consistency).
* We will most likely not implement a switching between the user types (e.g. make a placeholder a normal user). Instead we believe that batch editing work packages and assigning them to a real user is the cleaner approach.
* Menu items for work packages in the header navigation (the mechanism to decided which work package type are displayed in the menu).