Skip to main content

MAZENG-FT-51 · Authenticated bug-report intake

Feature intent

Signed-in users need to submit reproducible, environment-specific defects and receive a stable reference.

Why it matters

Signed-in users need to submit reproducible, environment-specific defects and receive a stable reference.

Expected outcome

The team receives actionable reports while reporter identity and staff workflows remain secure and auditable.

In scope

  • Structured authenticated intake for title, area, description, reproduction steps, environment, and device.
  • Separate reporter categories from internal staff workflow states.
  • Stable submission references and staff-only report administration.
Delivery status
IN_BACKLOG
Owner
RootAtSkic (product lead)
Parent Epic
MAZENG-EP-13
Solution approval
PENDING

Acceptance

Acceptance outcomes

  1. 01

    A signed-in reporter can supply all required defect and environment details.

  2. 02

    Server validation records immutable reporter identity and separates reporter categories from staff states.

  3. 03

    Successful submission returns confirmation and a stable reference.

  4. 04

    Only authorized staff can list, change, archive, or delete reports.

Dependencies and risks

Dependencies

None recorded.

Risks

  • Legacy area selection converts display text to a number, preventing valid submission.
  • Legacy read and mutation routes are unauthenticated.
  • Legacy update behavior creates records and conflicts with test expectations; these defects must not be preserved.

Authoritative Architecture tasks

No authoritative Architecture tasks are linked.

Original source