You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: frontend/src/features/usecase-demo/demoDefinitions.js
+8-23Lines changed: 8 additions & 23 deletions
Original file line number
Diff line number
Diff line change
@@ -15,33 +15,18 @@ Für schnelle Ausführung:
15
15
Liefere nur eine kurze, handlungsorientierte Zusammenfassung mit Prioritäten und nächstem Schritt.
16
16
Nutze ausschließlich CSV-Daten und nenne die verwendeten Ticket-IDs in Fließtext.`;
17
17
18
-
constSLA_BREACH_DEFAULT_PROMPT=`Find all tickets where the "assignee" field is empty (no individual person assigned — note: Status "Assigned" means assigned to a group, NOT to a person. A ticket can have Status="Assigned" and still have no individual assignee).
18
+
constSLA_BREACH_DEFAULT_PROMPT=`Use the csv_sla_breach_tickets tool to retrieve all unassigned tickets at SLA risk.
19
19
20
-
IMPORTANT: When calling csv_list_tickets, use the "fields" parameter to request ONLY the fields you need: "id,summary,priority,urgency,assignee,assigned_group,created_at". Also use has_assignee=false to filter server-side. This avoids fetching unnecessary data.
21
-
Set limit=100 for initial retrieval and keep this compact field set unless a specific ticket needs deep detail.
22
-
Do not use semantic/text-heavy analysis for this use case; numeric/status/date fields are sufficient.
23
-
Do not include notes/resolution by default; fetch them only for a small number of tickets if strictly required.
20
+
Call it with default parameters (unassigned_only=true, include_ok=false). The tool returns a pre-computed SlaBreachReport with:
21
+
- reference_timestamp: the anchor date used for age calculations (max date in the dataset)
22
+
- total_breached / total_at_risk: summary counts
23
+
- tickets: list of TicketSlaInfo objects already grouped (breached → at_risk) and sorted by age_hours descending
24
24
25
-
Check these tickets against priority-based SLA thresholds measuring time since created_at (the reported date).
25
+
Output the tickets array as a JSON block with these fields per row:
IMPORTANT: For the reference timestamp ("now"), do NOT use the current system time. Instead, find the most recent date across all date fields in the CSV data and use that as "now". This ensures meaningful age calculations for demo/historical data.
28
-
29
-
SLA thresholds by priority:
30
-
- Critical (1): 4 hours
31
-
- High (2): 24 hours (1 day)
32
-
- Medium (3): 72 hours (3 days)
33
-
- Low (4): 120 hours (5 days)
34
-
35
-
For each matching ticket, compute:
36
-
- age_hours: hours elapsed from reported_date to the reference timestamp
37
-
- sla_threshold_hours: the SLA threshold for its priority
38
-
- breach_status: "breached" if age_hours > sla_threshold_hours, "at risk" if age_hours > 0.75 * sla_threshold_hours, otherwise "ok"
39
-
40
-
Return ALL tickets with breach_status "breached" or "at risk". Group them by breach_status (all "breached" first, then all "at risk"), and within each group sort by age_hours descending.
41
-
42
-
Output a JSON array of objects with these fields: ticket_id, priority, urgency, assigned_group (the team responsible), reported_date, age_hours (rounded to 1 decimal), sla_threshold_hours, breach_status.
43
28
After the JSON block, provide a short markdown summary that:
44
-
1. States the reference timestamp used
29
+
1. States the reference_timestamp used
45
30
2. Groups ticket counts by breach_status and assigned_group
46
31
3. Recommends actions for the most critical breaches`;
0 commit comments