Standardizing the permission model for work items in groups and projects
Problem
It looks like issues_access_level (WorkItem.last.project.issues_access_level) will not be usable from group level work items (as project will be nil), how will group level work items permissions be controlled? Slack thread
We currently use project.issues_access_level
for part of the permissions for issues. In order to enable issues at the group level, we need to maintain a consistent, single set of access patterns and permissions for work items.
Proposal
- Unify the permissions/access patterns for issues/epics under something like
namespace.work_item_access_level
so it can be consistently applied to all work items in groups and projects.
Edited by Gabe Weaver