the Omnichannel audit form collects visitor/agent (required fields) but they are

[github-actions]

dropped here — carried over from the original DDP flow. Forwarding them would let the
omnichannel audit filter by the selected visitor/agent. Left for investigation.

📝 Found in apps/meteor/client/views/audit/hooks/useAuditMutation.ts#L26

Commit: 1393186

[coderabbitai]

🔗 Related PRs

#40728 - chore: migrate batch4 client DDP callers + add 6 REST endpoints [merged]
#41480 - fix: missing "user left" system message after omnichannel room forward [merged]

---

📝 Issue Planner

_{Check the box below or use the @coderabbitai plan command to generate an implementation plan and prompts that you can use with your favorite coding assistant.}

• Create Plan

---

🧪 Issue enrichment is currently in open beta.

You can configure auto-planning by selecting labels in the issue_enrichment configuration.

To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

issue_enrichment:
  auto_enrich:
    enabled: false

💬 Have feedback or questions? Drop into our discord!

[krishna5379chaudhary-eng]

Hi, I would like to work on this issue. Could you please assign it to me? I will investigate the missing visitor/agent fields in the Omnichannel audit mutation and submit a fix.