add issues and screenshotsmain

3 files changed, 84 insertions, 0 deletions

diff --git a/issues/new_issue_(severity_p2)_01.md b/issues/new_issue_(severity_p2)_01.md
new file mode 100644
index 0000000..917968e
--- /dev/null
+++ b/issues/new_issue_(severity_p2)_01.md
@@ -0,0 +1,27 @@
+[UI] [P2] Broken images render as missing icons on /broken_images page
+
+**Severity:** P2 (Medium)
+
+**Issue Type:** UI
+
+**Frequency:** Everytime
+
+**Environment:**
+- Browser: Mozilla LibreWolf 150.0.1-1 / Linux (Artix)
+- OS: Artix Linux, x86_64
+- URL: https://the-internet.herokuapp.com/broken_images
+
+**Steps to Reproduce:**
+1. Navigate to https://the-internet.herokuapp.com/broken_images
+2. Observe the two image elements on the page
+3. Note the broken/missing image icons in place of expected images
+
+**Expected:** Two images should render with valid `src` paths pointing to
+existing image files on the server.
+
+**Actual:** Two `<img>` elements display broken image icons. The `src`
+attributes point to non-existent paths (`/images/asdf.jpg` and
+`/images/hjkl.jpg`) returning HTTP 404.
+
+**Severity:** P2 — Visual content missing but page remains functional. No data
+loss.
diff --git a/issues/new_issue_(severity_p2)_02.md b/issues/new_issue_(severity_p2)_02.md
new file mode 100644
index 0000000..79a8167
--- /dev/null
+++ b/issues/new_issue_(severity_p2)_02.md
@@ -0,0 +1,26 @@
+[Functional] [P2] The page becomes unresponsive when clicking on the Post Comment button.
+
+**Severity:** P2 (High)
+
+**Issue Type:** Crash
+
+**Frequency:** Everytime
+
+**Environment:**
+- Browser: Mozilla LibreWolf 150.0.1-1 / Linux (Artix)
+- OS: Artix Linux, x86_64
+- URL: https://academybugs.com/store/heart-bracelet → Scroll Down → Fill Comment Form → Click "Post Comment"
+
+**Steps to Reproduce:**
+1. Open https://academybugs.com
+2. Click the Find Bugs link on the navigation bar
+3. Open a product
+4. Scroll down to the Leave a Reply section
+5. Fill out the comment form
+6. Click "Post Comment"
+
+**Expected:** The comment is posted under the product.
+
+**Actual:** The page becomes unresponsive when clicking on "Post Comment"
+
+**Severity:** P2 — Core purchase flow is blocked. Users cannot complete checkout.
diff --git a/issues/new_issue_(severity_p3)_03.md b/issues/new_issue_(severity_p3)_03.md
new file mode 100644
index 0000000..f318953
--- /dev/null
+++ b/issues/new_issue_(severity_p3)_03.md
@@ -0,0 +1,31 @@
+[Edge-Case] [P3] Non-standard/unhandled HTTP status codes render raw error pages 
+without user-friendly messaging
+
+**Severity:** P3 (Low)
+
+**Issue Type:** Edge Case
+
+**Frequency:** Everytime
+
+**Environment:**
+- Browser: Firefox 128 / Linux (Artix)
+- OS: Artix Linux, x86_64
+- URL: https://the-internet.herokuapp.com/status_codes
+
+**Steps to Reproduce:**
+1. Navigate to https://the-internet.herokuapp.com/status_codes
+2. Click the "404" link — observe raw "Not Found" error text
+3. Click the "500" link — observe raw "Internal Server Error" text
+4. Manually navigate to /status_codes/1000 — observe unhandled response
+
+**Expected:** Error pages should display user-friendly messages with navigation 
+options (e.g. "Page not found. Return to homepage."). Non-standard codes should 
+be caught and handled gracefully.
+
+**Actual:** All error status codes (404, 500, and non-standard codes like 1000) 
+render server error text with "Heroku" branding, yet no navigation links, and
+no guidance for the user to recover. Non-standard codes are not caught by any 
+fallback handler.
+
+**Severity:** P3 — No data loss, but poor user experience. Users encountering 
+errors have no path back into the application.