feat: return scrip results on ticket create, update frontend types

- POST /tickets now returns { ticket, scrip_results } matching PATCH pattern
- createTicket API function returns UpdateResult instead of Ticket
- Update call site to use data.ticket.id

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
This commit is contained in:
Gjermund Høsøien Wiggen
2026-06-09 10:51:14 +02:00
parent 60d2196e51
commit aa808f1d3f
5 changed files with 27 additions and 5 deletions

View File

@@ -428,7 +428,7 @@ function TicketWorkbenchContent() {
setNewSubject("");
setNewDescription("");
setNewCustomFieldValues({});
if (data) router.push(`/tickets/${data.id}`);
if (data) router.push(`/tickets/${data.ticket.id}`);
};
if (loading) return <SkeletonWorkbench />;

View File

@@ -63,8 +63,8 @@ export async function createTicket(data: {
queue_id: string;
description?: string;
custom_fields?: Record<string, string>;
}): Promise<{ data: Ticket | null; error: string | null }> {
return request<Ticket>("/tickets", { method: "POST", body: JSON.stringify(data) });
}): Promise<{ data: UpdateResult | null; error: string | null }> {
return request<UpdateResult>("/tickets", { method: "POST", body: JSON.stringify(data) });
}
export async function updateTicket(id: number, data: { subject?: string; status?: string; owner_id?: string | null }): Promise<{ data: UpdateResult | null; error: string | null }> {