Reporters are unable to filter issues by contact without membership in root namespace

Summary

Users with Reporter permissions or above in a subgroup are now able to assign contacts to an issue. However, if one of these users attempts to filter issues via the contact, all issues are returned instead of only the issues with the contact. If this user is then granted Reporter permissions or above in the root namespace, the filter is appropriately applied.

Steps to reproduce

  1. Enable CRM in your root namespace and designate a subgroup as your contact source.
  2. Enable CRM in the subgroup and create a contact.
  3. Create a few issues within a project in said subgroup.
  4. Assign the contact to one of the issues.
  5. Within the subgroup, invite/assign a user who does not have membership in the root group. Give them the reporter permissions.
  6. On the issue with a contact, click the contacts name view all issues in the subgroup, filtering by the contact. (Logged in as Reporter user)
  7. All issues will be displayed, regardless of contact assignment.

If you then give the user Reporter permissions in the root namespace, the issue list will be properly filtered.

What is the current bug behavior?

Issues are not filtered by the contact attribute unless the user has Reporter permissions or above in the root namespace.

What is the expected correct behavior?

Issues are filtered by the contact attribute when the user does not have Reporter permissions or above in the root namespace.

Relevant logs and/or screenshots

Screenshot_2025-02-03_at_1.42.32_PM Screenshot_2025-02-03_at_1.41.51_PM

Output of checks

This bug happens on GitLab.com

Edited Feb 03, 2025 by Caleb Williamson
Assignee Loading
Time tracking Loading