MyVideoGameList/myvideogamelist.com
MyVideoGameList/myvideogamelist.com
Watch
3
0
Fork
You've already forked myvideogamelist.com
 0
Code Issues 46 Pull requests 5 Projects 2 Releases Activity Actions

Repair Contact Us Support Path #785

New issue
Closed
opened 2026-06-30 06:03:40 -05:00 by Veilor · 1 comment
Veilor commented 2026-06-30 06:03:40 -05:00
Member
Copy link

Users need a working Contact Us path for account help, site issues, and support questions that do not fit the game request form.

The current Support > Contact Us page points users to an Open Service Desk button, but the destination is not usable for users. The site should either provide a working support destination or replace the broken CTA with an in-app contact option that can actually reach the team.

Scope

  • Public Support > Contact Us page.
  • Support overview and sidebar links that lead to Contact Us.
  • The current Open Service Desk call to action and any replacement contact flow.
  • User-facing copy for account help, site issues, and non-game-request support.
  • Existing game request support guide and request-game form behavior.

Acceptance Criteria

  • The Contact Us page gives users a working way to contact support.
  • The page no longer sends users to a dead or inaccessible support destination.
  • Support overview and sidebar Contact Us links continue to resolve to the Contact Us page.
  • The copy clearly distinguishes general support from game request submissions.
  • The Contact Us experience works for guests and authenticated users unless a deliberate auth requirement is added and explained.
  • The implementation avoids exposing private support credentials or internal-only URLs.
  • Existing How to Request Games guidance remains unchanged.

Test Coverage Required

  • Add or update feature coverage for the Contact Us page CTA or form.
  • Preserve support overview, knowledge base, and sidebar route/link coverage.
  • Cover guest access to the Contact Us page.
  • If a form is added, cover validation and successful submission or dispatch behavior.
  • Run focused support page tests before closing the issue.
  • Run vendor/bin/pint --dirty --format agent before implementation closeout if PHP files change.

Progress Checklist

  • Decide the replacement support contact path or in-app form behavior
  • Replace the broken service desk CTA with a working user-facing option
  • Keep Contact Us discoverable from Support and the sidebar
  • Preserve game-request-specific guidance separately
  • Add focused Contact Us regression coverage
  • Run focused support page tests
  • Run vendor/bin/pint --dirty --format agent if PHP files changed
  • Move the issue out of Codex review once verification is complete
Users need a working Contact Us path for account help, site issues, and support questions that do not fit the game request form. The current Support > Contact Us page points users to an Open Service Desk button, but the destination is not usable for users. The site should either provide a working support destination or replace the broken CTA with an in-app contact option that can actually reach the team. ## Scope - Public Support > Contact Us page. - Support overview and sidebar links that lead to Contact Us. - The current Open Service Desk call to action and any replacement contact flow. - User-facing copy for account help, site issues, and non-game-request support. - Existing game request support guide and request-game form behavior. ## Acceptance Criteria - The Contact Us page gives users a working way to contact support. - The page no longer sends users to a dead or inaccessible support destination. - Support overview and sidebar Contact Us links continue to resolve to the Contact Us page. - The copy clearly distinguishes general support from game request submissions. - The Contact Us experience works for guests and authenticated users unless a deliberate auth requirement is added and explained. - The implementation avoids exposing private support credentials or internal-only URLs. - Existing How to Request Games guidance remains unchanged. ## Test Coverage Required - Add or update feature coverage for the Contact Us page CTA or form. - Preserve support overview, knowledge base, and sidebar route/link coverage. - Cover guest access to the Contact Us page. - If a form is added, cover validation and successful submission or dispatch behavior. - Run focused support page tests before closing the issue. - Run `vendor/bin/pint --dirty --format agent` before implementation closeout if PHP files change. ## Progress Checklist - [x] Decide the replacement support contact path or in-app form behavior - [x] Replace the broken service desk CTA with a working user-facing option - [x] Keep Contact Us discoverable from Support and the sidebar - [x] Preserve game-request-specific guidance separately - [x] Add focused Contact Us regression coverage - [x] Run focused support page tests - [x] Run `vendor/bin/pint --dirty --format agent` if PHP files changed - [x] Move the issue out of Codex review once verification is complete
Codex changed title from Fix contact us for support to Repair Contact Us Support Path 2026-07-01 16:38:51 -05:00
Codex self-assigned this 2026-07-16 22:11:16 -05:00
Codex commented 2026-07-17 00:01:37 -05:00
Member
Copy link

Implemented via PR #835 and merged to master.

Notes for reviewers/deployers:

  • The broken service desk CTA was replaced with a working support email path.
  • Contact Us copy now separates general support needs from missing-game requests.
  • The page remains accessible to both guests and authenticated users.
  • Existing How to Request Games guidance and request-game behavior were preserved.

Verification completed:

  • php artisan test --compact tests/Feature/SupportGameRequestGuidanceTest.php
  • vendor/bin/pint --dirty --format agent
  • Forgejo Actions quality and CI passed on PR #835.
Implemented via PR #835 and merged to `master`. Notes for reviewers/deployers: - The broken service desk CTA was replaced with a working support email path. - Contact Us copy now separates general support needs from missing-game requests. - The page remains accessible to both guests and authenticated users. - Existing How to Request Games guidance and request-game behavior were preserved. Verification completed: - `php artisan test --compact tests/Feature/SupportGameRequestGuidanceTest.php` - `vendor/bin/pint --dirty --format agent` - Forgejo Actions quality and CI passed on PR #835.
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
master
renovate/composer/master/nunomaduro-collision-8.9.5
renovate/composer/master/pestphp-pest-plugin-laravel-5.0.1
renovate/npm/master/lightningcss-linux-x64-gnu-1.33.0
renovate/npm/master/axios-1.19.0
renovate/playwright-monorepo
dev
No results found.
Labels
Clear labels   
automated

   
code-quality

   
component: admin dashboard
The issue is related to the admin dashboard functionality.

  
component: backend
The issue is related to the backend code.

  
component: billing
The issue is related to our billing and payment system functionality.

  
component: content management
The issue is related to site content and moderation functionality.

  
component: faqs
The issue relates to our frequency asked questions and their categories.

  
component: game genres
The issue is related to genres in relation to games.

  
component: game lists
The issue is related to user-facing game list functionality.

  
component: game reviews
The issue relates to the game reviews functionality.

  
component: game search
The issue is related to the user-facing game search functionality.

  
component: games
The issue relates to games in our database.

  
component: internal notifications
The issue is related to the functionality of notifications sent for internal usage.

  
component: platforms
The issue is related to platform functionality.

  
component: security
The issue relates to the security issues within the app.

  
component: tests
The issue relates to unit and feature tests.

  
component: user api
The issue relates to the user-facing API.

  
component: user badges
The issue is related to our badge/achievements functionality.

  
component: user blogs
The issue is related to blogging functionality.

  
component: user consoles
The issue is related to user console lists functionality.

  
component: user favorites
This is issue is related to the favorites functionality.

  
component: user friends
The issue relates to the friending functionality.

  
component: user notifications
The issue is related to user-facing notifications functionality.

  
component: user profiles
The issue is related to user profile functionality.

  
component: user site notifications
The issue relates to the functionality of notifications shown to users directly on the website.

  
component: user wishlists
This issue is related to the wishlists functionality.

  
component: web design
This issue is related to the design of the website.

  
dependencies
Pull requests that update a dependency file.

  
javascript
Pull requests that update Javascript code

  
php
Pull requests that update PHP code.

  
priority
high
 The issue is considered a high priority.

  
priority
low
 This issue is considered a low priority.

  
priority
medium
 This issue is considered a medium priority.

  
security-hotspot

   
source: codex

   
source: sonarqube
  
status
awaiting feedback
 The issue is awaiting feedback from others.

  
status
backlog
 Issues that are in a backlog status.

  
status
done
 The issue has been completed and closed out.

  
status
in progress
 The issue is in progress and being actively worked on.

  
status
in queue
 The issue is in queue and will be worked on shortly.

  
status
in review
 The issue work has been completed and now the work needs to be reviewed.

  
status
needs codex review
 Use this tag to have Codex spiffy up your issue.

  
status
needs investigation
 The issue describes a problem which needs further investigation.

  
status
wontfix
 This issue will not be worked on.

  
type: bug
The issue describes something working the way it wasn't intended too.

  
type: documentation
Improvements or additions to site documentation.

  
type: feature
A new feature for the website.

  
type: improvement
An improvement on an existing feature.

  
type: regression
The issue describes a function that previously worked and no longer does.

  
type: task
A small-ish task.

No labels
automated
code-quality
component: admin dashboard
component: backend
component: billing
component: content management
component: faqs
component: game genres
component: game lists
component: game reviews
component: game search
component: games
component: internal notifications
component: platforms
component: security
component: tests
component: user api
component: user badges
component: user blogs
component: user consoles
component: user favorites
component: user friends
component: user notifications
component: user profiles
component: user site notifications
component: user wishlists
component: web design
dependencies
javascript
php
priority
high
priority
low
priority
medium
security-hotspot
source: codex
source: sonarqube
status
awaiting feedback
status
backlog
status
done
status
in progress
status
in queue
status
in review
status
needs codex review
status
needs investigation
status
wontfix
type: bug
type: documentation
type: feature
type: improvement
type: regression
type: task
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Post-Laravel 13 Release Clean Up
Assignees
Clear assignees
No assignees
Codex
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
MyVideoGameList/myvideogamelist.com#785
No description provided.