You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
Users of the move-contacts command made a very large hierarchy change at once. This caused a severe live-site incident https://github.com/medic/config-muso/issues/936 where users couldn't replicate for multiple weeks.
Retro after the incident, users requested faster simpler methods to reorganise the hierarchy. It was mentioned that hierarchy information in reports are not actually used by current cht-core versions.
Muso's devs indicated that they would have preferred to leave the original hierarchy in the reports for data-integrity reasons and analytics.
If we don't move reports as part of the move-contacts command, significantly less documents would be touched by the command. Servers would be less congested by moving contacts.
Describe the solution you'd like
Add a flag --skip-reports. When present, the move-contacts command will not update hierarchy information within reports.
Describe alternatives you've considered
We could default to not touching contacts?
Additional context
Users of the move-contacts command made a very large hierarchy change at once. This caused a severe live-site incident https://github.com/medic/config-muso/issues/936 where users couldn't replicate for multiple weeks.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
Users of the move-contacts command made a very large hierarchy change at once. This caused a severe live-site incident https://github.com/medic/config-muso/issues/936 where users couldn't replicate for multiple weeks.
Retro after the incident, users requested faster simpler methods to reorganise the hierarchy. It was mentioned that hierarchy information in reports are not actually used by current cht-core versions.
Muso's devs indicated that they would have preferred to leave the original hierarchy in the reports for data-integrity reasons and analytics.
If we don't move reports as part of the
move-contacts
command, significantly less documents would be touched by the command. Servers would be less congested by moving contacts.Describe the solution you'd like
Add a flag
--skip-reports
. When present, themove-contacts
command will not update hierarchy information within reports.Describe alternatives you've considered
We could default to not touching contacts?
Additional context
Users of the move-contacts command made a very large hierarchy change at once. This caused a severe live-site incident https://github.com/medic/config-muso/issues/936 where users couldn't replicate for multiple weeks.
The text was updated successfully, but these errors were encountered: