Update permissions for adding a child issue to an epic
Related to #431210
What does this MR do and why?
In previous tasks of #397073 we updated permissions for epic-epic and epic-issue relations so this is a follow-up to address permissions involved when setting an epic as parent of an issue.
We currently require read access for both epic and issue but to match the other relationships we need to require the Guest role in the project's issue. The epic's permissions remain the same, a user who is not a member of the epic's group can assign a child issue as long as they can read the epic.
Legend
| Icon | Requirement |
|---|---|
| Can read the item: Non-member for public group/project. Guest for private group/project | |
| Guest for public and private projects |
| Relationship | Action | Current | Expected |
|---|---|---|---|
| epic -> issue | create and remove | child |
child |
| epic -> issue | update | child |
child |
For updating the relation (meaning reordering the issue within the children list) we require the Guest role in both the issue's project and the epic's group.
The changes are behind the feature flag epic_relations_for_non_members, disabled by default.
EpicIssuesController and frontend menu will be updated in a follow-up.
Screenshots or screen recordings
Screenshots are required for UI changes, and strongly recommended for all other merge requests.
| Before | After |
|---|---|
How to set up and validate locally
Numbered steps to set up and validate the change are strongly suggested.
MR acceptance checklist
This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.
-
I have evaluated the MR acceptance checklist for this MR.
Related to #397073