Skip to content

fix(audit): forward visitor and agent fields in Omnichannel audit mutation #41665

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.

Sign up for GitHub

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

Open
surjeetkumar8006 wants to merge 1 commit into
base: develop
Choose a base branch
from
+7 −5
Open

fix(audit): forward visitor and agent fields in Omnichannel audit mutation #41665

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 5 additions & 0 deletions .changeset/omnichannel-audit-visitor-agent-filtering.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,5 @@
---
'@rocket.chat/meteor': patch
---

Fix Omnichannel audit filtering by forwarding selected visitor and agent IDs to `POST /v1/audit.omnichannelMessages` API endpoint.
7 changes: 2 additions & 5 deletions apps/meteor/client/views/audit/hooks/useAuditMutation.ts
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -23,11 +23,8 @@ export const useAuditMutation = (type: IAuditLog['fields']['type']) => {
startDate,
endDate,
users,
// TODO: the Omnichannel audit form collects visitor/agent (required fields) but they are
// 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.
visitor: '',
agent: '',
visitor,
agent,
});
return messages.map((message) => mapMessageFromApi(message));
}
Expand Down