RocketChat / RocketChat/Rocket.Chat
the Omnichannel audit form collects visitor/agent (required fields) but they are
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 46.1k
- Forks
- 13.9k
- Avg merge
- 3d 3h
- Merged PRs (30d)
- 130
Description
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: 1393186e690104a8ae94b109df6067448bd976b6
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start at apps/meteor/client/views/audit/hooks/useAuditMutation.ts#L26-L31 and trace how the original DDP flow handled the required visitor and agent fields. Confirm the selected values are forwarded by the Omnichannel audit form so the audit filter can use them; done means neither required field is dropped.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 68/100