Gulum
5069c0eb1e
Tickets können jetzt eine Rückfrage (Question) tragen und die Züchterin kann
in-app antworten. Feedback um FK-freie Felder Question/Answer/AnsweredAt erweitert
(überlebt Ingest-Wipe); Status-Lebenszyklus Open → NeedsInfo (Rückfrage gestellt)
→ Answered (beantwortet) → Resolved. Migration AddFeedbackQuestionAnswer.
PUT /feedback/{id}: question → NeedsInfo, answer → Answered+AnsweredAt; DTO gibt
die Felder zurück. Tickets-Seite (/hilfe/tickets) zeigt die Rückfrage hervorgehoben
und bietet ein Antwort-Feld + „Antworten"; Status-Badges Offen/Rückfrage offen/
Beantwortet/Gelöst.
Tests: FeedbackEndpointTests (Frage→NeedsInfo, Antwort→Answered, übersteht Ingest),
e2e tickets.spec.ts. dotnet/vitest/playwright grün.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
43 lines
1.2 KiB
C#
43 lines
1.2 KiB
C#
namespace GerbilManagerWebAPI.Dtos
|
|
{
|
|
/// <summary>FEEDBACK: payload for POST /feedback (the "Fehler melden" dialog).</summary>
|
|
public record FeedbackInput(
|
|
string Message,
|
|
string Context,
|
|
Guid? GerbilId,
|
|
Guid? LitterId,
|
|
Guid? ContactId,
|
|
string? EntityName,
|
|
string? Url,
|
|
DateTimeOffset? ClientTimestamp);
|
|
|
|
/// <summary>FEEDBACK: response DTO for a stored report.</summary>
|
|
public record FeedbackDto(
|
|
Guid Id,
|
|
string Message,
|
|
string Context,
|
|
Guid? GerbilId,
|
|
Guid? LitterId,
|
|
Guid? ContactId,
|
|
string? EntityName,
|
|
string? Url,
|
|
DateTimeOffset? ClientTimestamp,
|
|
string? UserAgent,
|
|
DateTimeOffset CreatedAt,
|
|
string Status,
|
|
DateTimeOffset? ResolvedAt,
|
|
string? Question,
|
|
string? Answer,
|
|
DateTimeOffset? AnsweredAt);
|
|
|
|
/// <summary>
|
|
/// FEEDBACK: payload for PUT /feedback/{id}. Edit the message and/or toggle status,
|
|
/// attach a clarifying question (Rückfrage), or submit the breeder's answer.
|
|
/// </summary>
|
|
public record FeedbackUpdate(
|
|
string? Message,
|
|
string? Status,
|
|
string? Question,
|
|
string? Answer);
|
|
}
|