Skip to content

Follow-up: verify and clean up legacy automation_clients collection #1

@iqdoctor

Description

@iqdoctor

Context

As of 2026-02-13 (commit b9a1389), Copilot code paths were migrated off the legacy automation_clients collection in favor of automation_customers -> automation_project_groups -> automation_projects.

Follow-up

  • Verify no remaining runtime/services depend on automation_clients (including any external automation services).
  • Smoke-test key flows:
    • POST /api/crm/dictionary
    • POST /api/crm/tickets
    • GET /api/plan-fact
    • Directories UI (clients/projects/rates)
  • Decide what to do with automation_clients in MongoDB:
    • keep as legacy, or
    • migrate remaining data (if any), then drop the collection.
  • If dropping: prepare a one-off script + backup/rollback plan.

References

  • docs/FIXING_COLLECTIONS_MESS_PLAN.md

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions