Bug - Project Assigned to Client doesn't allow assigning any users.

[GaianHelmers]

What is your set up?

Self Hosted Docker

Version

3.7.3

Describe the issue

When we set a project to include anyone assigned to the client, it becomes visible and editable.

However, I can't assign the to-dos to myself, because the only user actually considered attached to the project is the admin that made the project at the beginning.

Reproduction steps

1. Create Project
2. Assign to Team responsible for Client
3. With a team member account, create To-do's
4. To-do's get created.
5. Assign it to anyone on the team. No team members.

Error Logs (LEANTIMEFOLDER/storage/logs)

No response

[marcelfolaron]

Triage note (automated)

Thanks for reporting this. To help us verify and reproduce:

1. Which Leantime version are you running? (confirmed 3.7.3 from the issue)
2. How was the client team configured? Did you assign users to the client via Company → Clients → [client name] → Team, or through the project settings?
3. Are there any entries in storage/logs/error.log when you try to assign a user to a to-do?
4. When you say "the only user actually considered attached to the project is the admin" — does the user dropdown in the to-do assignment show only the admin, or does it show no users at all?

This could be a legitimate bug in how client-scoped project membership resolves available assignees, but we need the details above to pinpoint the query path involved.

[GaianHelmers]

Leantime.-.AllowCompany.mp4

• Yes I added my team to our "company client", then set the scope of the project to accept anyone in the target client, being our company.
• No logs that I can discern. I'm not great on Linux, but leantime.log is a blank file. No Error.log
• The drop down only shows the owner of the project, in this case it's the admin account.

[marcelfolaron]

Triage follow-up (automated)

Thanks for the video and details — this confirms the bug. The behavior is clear:

• Client team members are correctly associated with the client
• Project is scoped to "anyone assigned to the target client"
• Users can see and create tasks in the project
• But the assignee dropdown only shows the project owner (admin), not the other client-associated users

This is a query-level bug: the assignee dropdown likely queries zp_relationuserproject (direct project membership) instead of resolving users through the client association path (zp_clients → zp_user via client assignment → project scope).

Root cause: When a project uses psettings = 'clients', the project team resolver needs to include all users who belong to the project's client, not just users with a direct zp_relationuserproject entry. The access check in middleware correctly grants access through this path, but the assignee query doesn't use the same resolution logic.

Fix approach: The user listing for the assignee dropdown (likely in Users/Repositories/Users.php or Projects/Services/Projects.php) needs to be updated to also query users associated with the project's client when psettings = 'clients'.

Marking this as verified.