### Release Notes We reduced the minimum role required to relate issues and tasks from Reporter to Guest, giving you more flexibility to organize work across your GitLab instance while maintaining [permissions](https://docs.gitlab.com/ee/user/permissions.html). ## Summary As per https://gitlab.com/groups/gitlab-org/-/epics/10266, we should reduce the minimum role to relate two records to `Guest`. This epic is to address the relationships associated with issues. ## Proposal | Relation | Description | {-Current Permissions-} | {+New Permissions+} | Status | | ------ | ------ | ------ | ------ | ------ | | Epic-Issue (vertical) | Add/remove child issue | read access in epic (non-member if group is public, `Guest` if private) / `Reporter` access in issue | `Guest` access in issue and epic | Complete with https://gitlab.com/gitlab-org/gitlab/-/issues/382506 | | Issue-Issue (horizontal)|Link issues as blocked/blocking/related |`Reporter` access in both issues | `Guest` access in both issues |Scheduled with | | Issue-Task (vertical) | Add task to an issue | `Reporter` access in both work items | `Guest` access in both issue and task| Scheduled with|