Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Option to move-contacts without making changes to reports #551

Open
kennsippell opened this issue Mar 30, 2023 · 0 comments
Open

Option to move-contacts without making changes to reports #551

kennsippell opened this issue Mar 30, 2023 · 0 comments
Labels

Comments

@kennsippell
Copy link
Member

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant