Issue Reporter System

UX/UI Proposal for Eventify — Built-in bug reporting on every page

Contents
1. Overview & User Flow 2. The Floating Bug Button (FAB) 3. Report Panel — What We Ask 4. Complete Fields Reference 5. What's Auto-Captured (No User Input) 6. Admin Dashboard — Issues List 7. Admin Dashboard — Issue Detail 8. Status Workflow 9. Color Coding System 10. Open Questions for You

1. Overview & User Flow

Every page in both apps (guest event site + admin platform) will have a floating bug button. When clicked, a slide-out panel appears with a minimal form. The system auto-captures everything technical. Admins triage issues in a dashboard.

Visitor sees bug
Clicks bug button
Picks category + describes issue
Optionally: screenshot, more details
Submits → Gets ISS-42 confirmation
Admin opens /issues
Sees all reported issues
Clicks into detail
Triages: sets priority, assigns, resolves

2. The Floating Bug Button (FAB)

Guest Event App (Mobile)

Sarah & David
June 15, 2026 • The Grand Ballroom
RSVP
Will you attend?
🐛
Position: Bottom-right, ABOVE the navigation bar
First visit: Subtle pulse animation to draw attention
Keyboard: Cmd+Shift+F also opens it
Always visible: On every single page

Admin Platform (Desktop)

platform.eventify.com/dashboard
✨ Eventify
📈 Activation
💳 Billing
🐛 Issues
Dashboard content here...
🐛
Position: Bottom-right corner (no nav bar to avoid)
Sidebar: "Issues" nav item added with Bug icon
Same widget: Identical form, but pre-fills email from auth

3. Report Panel — What We Ask

The panel slides in from the right. It uses progressive disclosure — only 3 fields are visible by default. Advanced fields are hidden behind expandable sections.

Default View (what everyone sees)

Report an Issue

×
🐛 Bug
👁 UI Glitch
📄 Content
💡 Feature
Speed
Access
Other
What went wrong?
Tell us more... (what were you doing?)
you@example.com

Expanded "More Details" (optional)

More Details

all optional
1. Go to...
2. Click on...
3. See error
What should have happened?
What actually happened?
Minor  ▼
Critical / Major / Minor / Trivial
N/A  ▼
Always / Sometimes / Once / Can't Reproduce / N/A

Technical Info (auto-captured, read-only)

Chrome 128 macOS 15.2 1920×1080 /schedule 2 console errors 1 network failure
Key UX principle: The reporter doesn't need to know anything technical. We capture browser, OS, screen size, console errors, network failures, user actions (breadcrumbs), and Web Vitals automatically. They just describe the problem.

4. Complete Fields Reference

What the reporter fills in:

FieldRequired?TypeDefaultPurpose
CategoryRequiredIcon tile selector (7 options)NoneBug, UI Glitch, Content Error, Feature Request, Performance, Accessibility, Other
TitleRequiredText input (max 500 chars)None"What went wrong?" — one-line summary
DescriptionRequiredTextarea (max 5000 chars)Falls back to title"Tell us more..." — freeform details
ScreenshotOptionalOne-click capture buttonNoneAuto-captures current page as JPEG (quality 0.8, max 1920px)
EmailOptionalEmail inputSaved from last time / pre-filled from authFor follow-up. "Remember me" persists to localStorage
▼ More Details (hidden by default, expandable)
Steps to ReproduceOptionalTextarea (max 5000)Empty"1. Go to... 2. Click on... 3. See error"
Expected ResultOptionalText input (max 2000)Empty"What should have happened?"
Actual ResultOptionalText input (max 2000)Empty"What actually happened?"
SeverityOptionalDropdownMinorCritical / Major / Minor / Trivial
ReproducibilityOptionalDropdownN/AAlways / Sometimes / Once / Cannot Reproduce / N/A

5. What's Auto-Captured (No User Input)

The system silently collects this data in the background from the moment the page loads. It's attached to every report automatically.

DataHow It's CollectedExample
Browser + VersionUser agent parsingChrome 128.0
OS + VersionUser agent parsingmacOS 15.2
Screen Sizewindow.screen2560 × 1440
Viewport Sizewindow.innerWidth/Height1920 × 1080
Device TypeUser agent parsingdesktop / mobile / tablet
Languagenavigator.languageen-US
Current URLwindow.location.href/events/wedding/schedule
Console ErrorsMonkey-patched console.errorLast 20 errors with timestamps
Network FailuresMonkey-patched fetchLast 20 failed requests (URL, method, status)
User BreadcrumbsClick + navigation listenersLast 30 actions (clicked "RSVP", navigated to /gallery)
Web Vitalsweb-vitals libraryLCP: 1200ms, CLS: 0.05, INP: 120ms

6. Admin Dashboard — Issues List

Route: /issues in the platform app. Accessible from the sidebar.

platform.eventify.com/issues
🐛

Issues

Track and triage reported issues from your event guests.

New
12
In Progress
5
Resolved
28
Closed
15
New Triaged In Progress Resolved Verified Closed Reopened Rejected Deferred Duplicate
All Categories ▼
All Severities ▼
All Priorities ▼
🔍 Search issues...
IDTitleCategorySeverityPriorityStatusReporterCreated
ISS-42 RSVP form doesn't submit on Safari Bug Critical None New sarah@gmail.com 2h ago
ISS-41 Gallery images load slowly on mobile Performance Major High In Progress Anonymous 5h ago
ISS-40 Typo in Hebrew translation on schedule page Content Error Trivial Low New moshe@test.com 1d ago
ISS-39 Add dark mode support for event pages Feature Request Minor None New david@test.com 2d ago

7. Admin Dashboard — Issue Detail

Route: /issues/:id. Click any row in the list to see full details + triage controls.

platform.eventify.com/issues/abc123
← Back to Issues
ISS-42 Bug

RSVP form doesn't submit on Safari

Description

When I try to submit the RSVP form on Safari 18, clicking the "Submit" button doesn't do anything. No error message appears. The form just stays there. It works fine on Chrome.

Steps to Reproduce

1. Open the event page on Safari 18 2. Fill in name and email in the RSVP form 3. Click "Attending" 4. Click "Submit RSVP" 5. Nothing happens

Expected Result

RSVP should be submitted and confirmation shown

Actual Result

Button click has no effect, no error displayed

Technical Details
URL: /rsvp
Browser: Safari 18.0
OS: macOS 15.2
Screen: 2560×1440
Viewport: 1440×900
Device: desktop
Console Errors (1)
TypeError: form.requestSubmit is not a function

🕑 Activity

Changed status from "new" to "triaged" • 1h ago
Changed priority from "none" to "urgent" • 1h ago
A
Admin 45m ago
Confirmed — Safari 18 doesn't support form.requestSubmit(). Need to add polyfill or use form.submit() fallback.

💬 Add Comment

Write a comment...

8. Status Workflow

NewTriagedIn ProgressResolvedVerifiedClosed

                                                        ↓                        ↓
                                                   Reopened ←←←←←←←←←←← (verification failed)

At any point:  →  Rejected  |  Deferred  |  Duplicate

Resolution Values (set when resolving)

FixedBug was fixed in the code
Won't FixValid issue but intentionally not fixing
DuplicateAlready reported (linked to original)
Cannot ReproduceUnable to reproduce with given steps
By DesignWorking as intended, not a bug
DeferredValid but postponed to a future release

9. Color Coding System

Categories

Bug UI Glitch Content Error Feature Request Performance Accessibility Other

Severity

Critical Major Minor Trivial

Priority

Urgent High Medium Low None

Status

New Triaged In Progress Resolved Verified Closed Reopened Rejected Deferred Duplicate

10. Open Questions for You

  1. Categories: Are these 7 categories right? (Bug, UI Glitch, Content Error, Feature Request, Performance, Accessibility, Other) Want to add/remove/rename any?
  2. Severity levels: 4 levels (Critical/Major/Minor/Trivial) — enough? Too many?
  3. Anonymous reporting: Should guests be able to report without any email at all? Currently yes.
  4. Screenshot capture: Auto-capture on button click, or should it also offer manual file upload?
  5. FAB position/color: Bottom-right with primary (indigo) color. Want a different color or position?
  6. Admin assignee: Currently just shows user ID. Should we pull team member names for a dropdown? (Requires team.list integration)
  7. "Feature Request" as a category: Should feature requests go through the same system, or should they be separate?
  8. Notification: Should admins get notified (email/toast) when a new issue is submitted?
  9. Reporter follow-up: Should we send an email to the reporter when their issue is resolved?
  10. Anything else you'd change about the flow, fields, or look?
— End of Proposal —
Generated for Eventify Issue Reporter System • March 2026