Administrate Individual Plan for Sub Trees

1 Requirements

In the current implementation of the Study Programme, the Individual Plan for a member of the program can only be edited at the node where the member was assigned. This was designed with a person like a "programme supervisor" in mind, that controls the node where a user is assigned. He then could set individual conditions for the user, while the persons controlling the subnodes of the programme can not change those conditions but only decide whether a member passed the node or not (via accrediting the user or supplying her with courses to complete the node).

This, however, is not enough to represent all real world use cases, where persons controlling the subnodes could in fact be in charge to set individual conditions for a user in their sub tree of the study programme.

The user story thus is:
A person controlling a sub-tree of a larger Study Programme should be able to edit the Individual Plan of a user for the sub tree they control, even if the user was assigned at a node above.

To implement this requirement a new permission "edit individual plans" is created to make it possible to restore the current behaviour and implement the new requirement. If a user has that permission at a node, he is able to edit the Individual Plans of all members of that node, even if they were assigned at a node above, but only for the subtree starting at that node.

2 Additional Information

• Idea / concept: Marko Glaubitz, Richard Klees <richard.klees@concepts-and-training.de>
• Interest in funding: (please indicate if you are interested/able to fund this feature)
• Maintainer: Richard Klees <richard.klees@concepts-and-training.de>
• Implementation of the feature is done by (will be set by Jour Fixe / maintainer)
• Testcases by: (please add your name if you want to create the testcases for this feature)

3 Discussion

4 Implementation

{please give a description of the final implementation and add screenshots if possible}

Test Cases

Test cases completed at {date} by {user}

• {Test case number linked to Testrail} : {test case title}

Approval

Approved at {date} by {user}.