DEF-039 — Masters create and edit forms have no Cancel or Back button

Admin Panel
Low severity
UX
New
Defect DEF-039 — Severity: Low · Status: New
Published

2026-06-17

DEF-039 — Masters create and edit forms have no Cancel or Back button

Summary

The create and edit forms for all Masters sub-pages (Safety & Hazard, Broadcasting, SOS, Obstacle, Weather, Sale Attributes, Story Report Reasons, User Report Reasons, Maintenance Master) contain only a Submit button. There is no Cancel or Back button to return to the list without saving. Admins who open the form by mistake or change their mind must use the browser’s back button or click the breadcrumb link.

Environment

  • URL: https://project6.dxtserver.com/drivelink_new/public/masters/safety-hazard/create
  • Module: Admin Panel — Masters (all sub-pages, create and edit forms)
  • Date Reported: 2026-06-17
  • Browser: Chromium (Playwright)
  • Testing Phase: Admin Panel — Section 2: Masters (test case MST-02-5)

Steps to Reproduce

  1. Log in to the Admin Panel.
  2. Navigate to any Masters sub-page (e.g., Masters → Safety and Hazard).
  3. Click + Create New.
  4. Observe the form — only a Submit button is present.
  5. There is no Cancel, Back, or Discard button.

Expected Behaviour

Create and edit forms should include a Cancel button that navigates back to the list page without saving any changes. This is standard UX practice for admin CRUD forms and matches the pattern used in most of the other admin sections.

Actual Behaviour

Only a Submit button is present. To leave the form without saving, admins must: - Press the browser’s back button - Click the “Drivelink” breadcrumb link at the top of the page

Neither option is clearly labelled as “cancel this action”, which may cause confusion, especially for less technical users.

Impact

  • Minor UX friction; no data loss risk since navigating away without submitting does not save data
  • Inconsistent with standard admin form patterns
  • Likely affects all Masters create and edit forms (not verified individually for every sub-page)

Severity

Low — Purely a UX omission; no functional breakage or data risk.

Priority

Low

Status

New

Reported By

QA / Testing Team