Content
View differences
Updated by Klaus Zanders almost 3 years ago
To allow users or groups to be added to single work packages as contributors, we need to establish a new membership system that allows this. The current `members` table only supports adding users to whole projects.
* [ ] Create a new table that links WorkPackages with users members (polymorphic: group or user) and allows assigning **one** role for that member
* [ ] Change the `visible` scope of WorkPackages to also include those, where the requested user is either able to view the WP because of project membership or direct WP membership
~~Extending Extending the current~~ `~~members~~` ~~relation current `members` relation is not really an option, as it does not support polymorphism and changing that would be a really big data model change. Also, it supports assigning multiple roles to a membership, that is something that is not needed for the WP memberships~~ memberships
* [ ] Create a new table that links WorkPackages with users
* [ ] Change the `visible` scope of WorkPackages to also include those, where the requested user is either able to view the WP because of project membership or direct WP membership
~~Extending