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>
68 lines
3.1 KiB
C#
68 lines
3.1 KiB
C#
using System.ComponentModel.DataAnnotations;
|
|
|
|
namespace GerbilManagerWebAPI.Models
|
|
{
|
|
/// <summary>
|
|
/// FEEDBACK: a user-submitted "Fehler melden" report. Decoupled from the rest of the
|
|
/// model on purpose — GerbilId/LitterId are plain nullable Guid columns (NOT enforced
|
|
/// foreign keys), so the import re-ingest wipe (IngestResolvedService) can delete
|
|
/// gerbils/litters without deleting or breaking feedback rows. The captured EntityName
|
|
/// keeps the report human-readable even after the referenced animal is gone.
|
|
/// </summary>
|
|
public class Feedback
|
|
{
|
|
[Key]
|
|
public Guid Id { get; set; }
|
|
|
|
/// <summary>The user's free-text description of the problem.</summary>
|
|
public required string Message { get; set; }
|
|
|
|
/// <summary>Which view the report came from: stammbaum | gerbil-detail | litter-detail.</summary>
|
|
public required string Context { get; set; }
|
|
|
|
/// <summary>Loose reference (no FK) to the gerbil the report is about, if any.</summary>
|
|
public Guid? GerbilId { get; set; }
|
|
|
|
/// <summary>Loose reference (no FK) to the litter the report is about, if any.</summary>
|
|
public Guid? LitterId { get; set; }
|
|
|
|
/// <summary>Loose reference (no FK) to the contact the report is about, if any.</summary>
|
|
public Guid? ContactId { get; set; }
|
|
|
|
/// <summary>Captured name of the referenced animal/litter (survives an ingest wipe).</summary>
|
|
public string? EntityName { get; set; }
|
|
|
|
/// <summary>The client URL/route the report was filed from.</summary>
|
|
public string? Url { get; set; }
|
|
|
|
/// <summary>Client-supplied timestamp (when the user submitted, in their browser).</summary>
|
|
public DateTimeOffset? ClientTimestamp { get; set; }
|
|
|
|
/// <summary>Optional browser user-agent for diagnostics.</summary>
|
|
public string? UserAgent { get; set; }
|
|
|
|
/// <summary>Server-side creation time.</summary>
|
|
public DateTimeOffset CreatedAt { get; set; }
|
|
|
|
/// <summary>
|
|
/// Ticket lifecycle status: "Open" | "NeedsInfo" | "Answered" | "Resolved" (default "Open").
|
|
/// "NeedsInfo" = a maintainer attached a clarifying question (Rückfrage) and is waiting on
|
|
/// the breeder; "Answered" = the breeder replied. Plain string, no FK — keeps feedback
|
|
/// decoupled and ingest-surviving like the rest of the row.
|
|
/// </summary>
|
|
public string Status { get; set; } = "Open";
|
|
|
|
/// <summary>When the ticket was marked resolved; null while open.</summary>
|
|
public DateTimeOffset? ResolvedAt { get; set; }
|
|
|
|
/// <summary>A clarifying question (Rückfrage) a maintainer attaches to the ticket; null if none.</summary>
|
|
public string? Question { get; set; }
|
|
|
|
/// <summary>The breeder's (Züchterin) reply to the clarifying question; null until answered.</summary>
|
|
public string? Answer { get; set; }
|
|
|
|
/// <summary>When the breeder answered the clarifying question; null until answered.</summary>
|
|
public DateTimeOffset? AnsweredAt { get; set; }
|
|
}
|
|
}
|