You need to sign in or sign up before continuing.
Pass correct GraphQL variable when expanding a group
What does this MR do and why?
Related to #574413 (closed)
When expanding a subgroup in the nested groups lists the API variables are not being passed correctly. This causes a bug where archived or pending deletion groups/projects are shown when they should not be.
This MR passes the correct variables when making the API call.
References
Screenshots or screen recordings
Group overview
Unarchived project
no changes
| Before | After |
|---|---|
 |
 |
Archived project
| Before | After |
|---|---|
 |
 |
no changes
| Before | After |
|---|---|
 |
 |
Your work -> Groups
no changes
| Before | After |
|---|---|
 |
 |
 |
 |
How to set up and validate locally
- Go to a group
- Create a subgroup
- Created a nested subgroup and a nested project
- Go back to the original group
- Archive the project using the quick action
- Expand the subgroup, the archived project should not be shown
- Go to the
Inactivetab, the archived project should be shown
MR acceptance checklist
Evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.
Edited by Peter Hegman