Skip to content
Snippets Groups Projects

Unclear error message is shown when trying to expand a group with sub-groups

    • Closed Issue created by Alexandr Tanayno @atanayno

    Summary

    If you are a member of a nested group inside a sub-group, unclear error message will be shown to you when trying to expand a top-level group.

    Steps to reproduce

    • create a group level0-group and mark it as internal/public
    • create a private sub-group level1-group inside level0-group
    • create a private sub-group level2-group inside level1-group
    • add a member in level2-group with Owner permissions
    • login as this member, open explore/groups page and find level0-group there
    • click arrow next to the group to expand both sub-groups, expanding will work fine
    • now click the link to level0-group and then click arrow next to it, you will get an empty red error (see the screenshot below)
    • create a project inside level2-group, now you will be able to expand level0-group and see level1-group successfully

    Example Project

    It can be reproduced with the group https://atatahost.ml/level0-group and its sub-groups though you will either need to have admin access to check it or ask me to add you as a member of the sub-group level2-group inside this group.

    What is the current bug behavior?

    1. Expanding will not work from level0-group page: on GitLab 13.3.x it will fail with An error occurred. Please try again., on GitLab 13.4.x it fails with empty red error block.
    2. If you click the link to level1-group, it will give you 404. It is probably expected in this case as the sub-group is private, but it looks rather confusing.

    What is the expected correct behavior?

    Expanding should work fine from level0-group page.

    Relevant logs and/or screenshots

    The developer console will show error 404 when trying to expand the group. UI shows empty red block as shown in the screenshot:

    group_expand_error

    Output of checks

    This bug was reproduced on GitLab.com and on self-managed instances (13.3.7/13.4.1).

    Workaround

    Create a project inside level2-group.

    Edited by Alexandr Tanayno

    Designs

      Child items ...

      2. Activity

      Please register or sign in to reply