medic
"Move-Contacts" action should provide an overview of the users which will be impacted
Use of the "move-contacts" action may cause significant disturbances to projects.
Removing contacts from an offline user's view will not cause them to disappear. The contact remains on the user's device, but any updates made to the user, or any reports created for that user will silently fail to sync. medic/medic/issues/5701. The tool recommends that users who have contacts removed from their view need to clear cache and perform a clean synchronization. Similarly, adding documents to an offline user's view can slow down their experiences and cause lengthy synchronizations.
It would be useful to help mitigate this disturbance if the "move-contacts" action provided a list of impacted users so the operator can 1) clearly understand the level of impact of the operation they are performing, and 2) more easily follow-up with impacted users.
The ongoing discussions in medic/cht-core#5701 should include discussion of this requirement. I'm labeling this as blocked for now until a broader strategy is identified.