Domain Separation and Assignment groups

[ChrisLawer]

We have domain separation setup and I'm having trouble with the assigned to field in tickets in our client domains. Let me explain how the domains are setup:

TOP (root)
  ├── Clients
  │   ├── Client1
  │   ├── Client2
  │   └── Client3
  ├── Standard
  │   ├── Partners (your default domain)
  │   ├── Leads
  │   └── Support Teams
  └── Default

Our users were moved to the Partners domain, along with the custom dashboards. As long as they put tickets in under that domain everything works fine. We have three client domains that really are more project domains and we have given members from the partners domains visibility to the client domains. There are no users directly within the client domains at this time, everyone just has visibility. The idea is that the data stays separated more than anything else. 

The problem I am running into is that we can't see the members in the assignment groups while in the client domains. Even if the group and members both have visibility set. 

Any thoughts?

[rudipohjaniemi]

Can you see the users if you edit the Assigned to field from list view?
Could be that you have the property on for "Use the domain for the record being viewed" that could be limiting it on the record itself.

I don't have access to an environment where I can test this right now, so I'm just asking from memory.

[ChrisLawer]

So I checked that out and it wasn't the solution. 

[ChrisLawer · Accepted solution]

Figured out the solution. In the Since the partners domain and the client domains are in two separate branches on the tree the clients could only see global users or those with visibility. To allow them to see all users I needed to add the partners domain to the client domains via the "Contains domain" option. This gives the clients the ability to see everything in the main domain including people while still keeping their data safe from the rest of the company.