- Ya
- 22 Julai 2026, 20:24 UTC
- Mwandishi
- kamo
- Ahadi ya
- b9c921c
The grid already had multi-select checkboxes but nothing to do with a selection. Checking rows now reveals a Reassign action beside the other lead actions, gated on REASSIGN_LEADS_MANUALLY (the server re-checks it; this is convenience only). Uses checkRight rather than checkRole so god mode matches the backend's hasGod bypass — checkRole doesn't bypass and would diverge for god users. The dialog picks one destination member by search, takes an optional note, and says up front that the member will be emailed, since that's the point of the feature. Indigo/blue rather than Hot Reassign's orange/pink: this is a deliberate bulk admin action, not an urgent call transfer. The header checkbox selects every row in the client-side grid — thousands for a large org — so the 250 cap is enforced here too. Otherwise the headline "select all and reassign" flow would fail server-side only after the user had filled in the entire dialog, with an untranslated error. Selection is cleared through selectedIdsRef before reloading: loadLeads re-selects whatever that ref holds, so leaving it populated would re-check the rows just moved. The result message is composed rather than an else-if chain, because a batch can be both partial and unnotified and the chain reported only the first.