064a73ba4b
feat: add conversations:read_team_all permission to allow agents to see conversations assigned to their team, regardless of whether an agent is assigned or not.
...
- Allow all SLAs to be fetched without permission checks.
Ref #203
2025-12-26 19:57:45 +05:30
d2e5d85e3a
fix: return created/updated objects in POST/PUT responses with masked secrets
...
All POST/PUT handlers now return actual database objects instead of `true`
2025-06-20 19:35:09 +05:30
3998798e54
refactor: rename SQL query names and struct fields for clarity and consistency
2025-05-27 02:45:43 +05:30
b715483260
refactor(conversation): reduce DB I/O by using existing appliedSLAID from conversation
...
- Passes appliedSLAID directly to SLA logic instead of refetching
- Adds appliedSLAID field to conversation struct (already fetched in get-conversation query)
2025-05-26 03:48:41 +05:30
7426a09478
feat: allow setting metric per SLA notification, so admins can set SLA alert per metric or just set to all if they want a notification to be sent for all metrics
...
- Make sla time fields (first response, next response, resolution) optional, only 1 field is required.
2025-05-26 03:48:41 +05:30
8ad2f078ac
fix sql query
2025-05-26 03:48:41 +05:30
9226063db3
fix: remove queries using conversation.applied_sla_id
...
as this column is removed
- fix sql query
2025-05-26 03:48:41 +05:30
a9fd4fe2b6
fix: uise existing set next sla deadline sql query and remove duplicate query.
...
- remove previously added `applied_sla_id` column to conversations table as it was causing cyclic dep
2025-05-26 03:48:41 +05:30
7e8c9962c3
Fixes for next response time sla metric
2025-05-26 03:48:41 +05:30
4c766d8ccb
wip: next response metric for sla
2025-05-26 03:48:41 +05:30
aeef7d4ad7
feat: configurable SLA alerts per SLA.
2025-03-21 23:23:03 +05:30
45541c221a
fix: various bugs in SLA calculation
...
prevents multiple update queries unnecessarily on applied sla table.
clear next sla deadline in conversations properly when there's no deadline to be met.
uses the new status column in the applied sla table to determine if the sla is still active and has to be calculated again.
2025-03-12 02:45:17 +05:30
6993d972ab
fix[SLA]: Use conversation created_at time as start time for SLA calculation. This makes sure when SLA is changed for a conversation the elapsed time carries over.
...
refactor: improve error handling and update comments for clarity
2025-02-02 23:51:50 +05:30
3c71ab35ff
Feat: Add SLAs per team
...
- Feat: Provide the ability to change SLAs for conversations; this will start a new deadline calculation from the time the SLA is set.
2025-01-24 04:34:51 +05:30
50188352a5
fix: Use SyncedEnforcer in casbin, fixes panics.
...
feat: store user roles in user roles table, drops the roles table on users table.
feat: standardize column names in schema, renames disabled bool to enables.
- vue router fixes to allow components / pages to rerender after creating an object in db.
- minor fixes and refactors.
2025-01-22 03:40:32 +05:30
0c01b53b09
feat(conversations): add trigram index for searching ref numbers
...
feat(messages): add trigram index for text content search
- feat: UI animations for conversation and messages list.
- Simplify websocket updates.
2025-01-19 23:10:53 +05:30
caf8e7d34d
WIP: MVP with shadcn sidebar
...
- csat
- SLA
- email notification templates
2025-01-06 02:39:44 +05:30
Abhinav Raut