Skip to content

Groups originating from group shares should be listed on project import

Manoj M J requested to merge 365223-groups-originating-from-group-shares-that-the-user-has-access-to-are-not-listed-when into master

What does this MR do and why?

Related to #365223 (closed)

Note: Both project create and project import uses the same GraphQL endpoint to fetch the groups where new projects can be created, so this change affects and fixes the groups dropdown of both project create and project import pages.

This MR tries to solve the following problem:

Before After the fix
Screenshot_2023-03-30_at_2.37.31_PM Screenshot_2023-03-30_at_2.39.31_PM
Screenshot_2023-04-05_at_9.56.08_AM Screenshot_2023-04-05_at_9.56.24_AM

Existing problem

A user has the rights to create a project in:

  • groups where direct OWNER

  • groups where direct MAINTAINER

  • groups where direct DEVELOPER and the group's setting says that "DEV+MAINTAINERS" can create projects.

  • groups where OWNER via group share.

  • groups where MAINTAINER via group share.

  • groups where DEVELOPER via group share and the group's setting says that "DEV+MAINTAINERS" can create projects.

The first (3) items in the list are currently exposed in the UI. However, any group arising from group shares wasn't being listed in the dropdown until now, which is what this MR fixes.

Screenshots or screen recordings

Screenshots are required for UI changes, and strongly recommended for all other merge requests.

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.

Edited by Manoj M J

Merge request reports