CRM error when enabling CRM at parent group level with contacts in subgroup issues

Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.

Summary

When enabling CRM at a parent group , the system throws "Contact source cannot be changed" error if subgroup issues already have contacts assigned, even though all contacts use the same source.

Steps to reproduce

  1. Create a parent group and subgroup
  2. Assign contacts to issues in the subgroup from a specific contact source
  3. Try to enable CRM at the parent group level
  4. Error appears: "Contact source cannot be changed when issues already have contacts assigned from a different source"

What is the current bug behavior?

While attempting to enable CRM in the parent group, the user gets the error "Contact source cannot be changed when issues already have contacts assigned from a different source" if subgroup issues have contacts assigned.

What is the expected correct behavior?

GitLab should allow CRM in the parent group when subgroup issues have contacts assigned from the same source.

Output of checks

High-severity bug remediation

To remediate high-severity issues requiring an internal release for single-tenant SaaS instances, refer to the internal release process for engineers.

Edited by 🤖 GitLab Bot 🤖