Reporting Technical Issues & Bugs
Best practices for reporting bugs to ensure a swift resolution.
Omar Noaman Studios
Last Update 8 months ago
If you encounter unexpected behaviour on your website, our technical team is ready to investigate. To help us fix the issue quickly, please follow this guide before submitting a ticket.
1. Basic Troubleshooting (Try This First)
Often, "bugs" are simply caching issues. Please try:
Hard Refresh:
Press `Ctrl + F5` (Windows) or `Cmd + Shift + R` (Mac) to clear the browser cache.
Incognito Mode:
Open the page in a private/incognito window. If it works there, the issue is likely with your browser cache or extensions.
2. How to Report a Bug
If the issue persists, please submit a ticket with the following details:
URL:
The specific link where the error occurs.
Device & Browser:
(e.g., iPhone 14 using Safari, or Windows PC using Chrome).
Screenshots/Video:
A visual recording of the issue is invaluable.
Steps to Reproduce:
Briefly list the actions you took right before the error appeared (e.g., "I clicked 'Add to Cart' then 'Checkout'").
3. Response Time
Critical bugs affecting site availability (e.g., site down) are prioritised and typically addressed within 4 hours. Cosmetic or non-urgent issues are scheduled into our standard development sprint.
1. Basic Troubleshooting (Try This First)
Often, "bugs" are simply caching issues. Please try:
Hard Refresh:
Press `Ctrl + F5` (Windows) or `Cmd + Shift + R` (Mac) to clear the browser cache.
Incognito Mode:
Open the page in a private/incognito window. If it works there, the issue is likely with your browser cache or extensions.
2. How to Report a Bug
If the issue persists, please submit a ticket with the following details:
URL:
The specific link where the error occurs.
Device & Browser:
(e.g., iPhone 14 using Safari, or Windows PC using Chrome).
Screenshots/Video:
A visual recording of the issue is invaluable.
Steps to Reproduce:
Briefly list the actions you took right before the error appeared (e.g., "I clicked 'Add to Cart' then 'Checkout'").
3. Response Time
Critical bugs affecting site availability (e.g., site down) are prioritised and typically addressed within 4 hours. Cosmetic or non-urgent issues are scheduled into our standard development sprint.