Content
View differences
Updated by Klaus Zanders 17 days ago
**As** a user manager
**I want to** organize my departments groups hierarchically
**so that** I can show my organizational structure
**Acceptance criteria**
* Pre-requisite: <mention class="mention" data-id="73527" data-type="work_package" data-text="##OP-19115" data-display-id="OP-19115">##OP-19115</mention> Groups can be nested
* Build a new type of Roles & Permissions are inherited through the hierarchy
* Group called `Department` that has special semantics
Structure: Development Team -> Sirius Team
* Users can only be part of one `Department`. When you try to assign I make the _Development Team_ a user that is already part member of another `Department` you are asked if you want to move the user project, also members from _Sirius Team_ will be a a member of the project and if you say yes, get the user is removed from the old `Department`.
permissions
* Departments are displayed in their own menu item in Groups get a new flag to be marked as _Organizational Units_. This causes the Users & Permissions section of administration
* Departments are presented groups to show up in a tree view
structure that resembles an org chart
**Technical notes**
* Department hierarchies can be moved around We keep existing groups as they are
**Permissions and visibility considerations**
* _Should the organizational structure be visible to the entire org? Should only members of a group see their entire tree?_
**Translation considerations**
* _Key terms and phrases in the key languages_ languages_
**Out of scope**
* LDAP sync should correctly set the structure. We have to think about how we treat current groups, because this might give people permissions they not previously had
_Set the_ **To be informed/consulted teams** _field to include all teams necessary to be informed of the changes._
**I want to** organize my departments
**so that** I can show my organizational structure
**Acceptance criteria**
* Pre-requisite: <mention class="mention" data-id="73527" data-type="work_package" data-text="##OP-19115" data-display-id="OP-19115">##OP-19115</mention>
* Build a new type of
*
* Departments are presented
**Technical notes**
**Permissions and visibility considerations**
* _Should the organizational structure be visible to the entire org? Should only members of a group see their entire tree?_
**Translation considerations**
* _Key terms and phrases in the key languages_
**Out of scope**
* LDAP sync should correctly set the structure. We have to think about how we treat current groups, because this might give people permissions they not previously had
_Set the_ **To be informed/consulted teams** _field to include all teams necessary to be informed of the changes._