Do not restrict issues that can be assigned to epics by hierarchy position
What does this MR do and why?
Allow epics to have child issues from ancestors, descendants, or siblings group projects.
Before this MR when epic_issues_from_different_hierarchies was on it was not possible to
add an issue from a ancestor group project to an epic. We do not want any kind of restriction anymore.
For more detailed information check this thread: #375289 (comment 1116213979)
related to #375289 (closed)
How to set up and validate locally
- Enable
epic_issues_from_different_hierarchiesfeature flag - Create the following group structure:
graph TD;
A-->B;
A-->C;
B-->D;
C-->E;
- Create an epic on Group B
- Now you should also be able to assign child issues from groups A, C and E projects to the epic.
obs: With the flag disabled only issues from group D projects should be accepted.
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.
Edited by Felipe Cardozo