Revise bug report template for clarity

Updated bug report template to clarify issue attribution and wording.

Signed-off-by: Philip Abbey <philipabbey@users.noreply.github.com>

.github/ISSUE_TEMPLATE/bug_report.md

@@ -2,13 +2,19 @@
 name: Bug report
 about: Create a report to help us improve
 title: ''
-labels: bug
+labels: question
 assignees: ''
 
 ---
 
-**Describe the bug**
-A clear and concise description of what the bug is.
+The majority of bug reports submitted are solved without changes to the Garmin application's code. This means that reporters are too often keen to attribute their issue to a problem with the application instead of:
+1. Their own lack of reading documentation
+2. Their own infrastructure
+
+Therefore in the first place make your report as if it were a **question** in order to establish if the authors agree there is really a bug!
+
+**Describe your issue**
+A clear and concise description of what the issue is.
 
 **IMPORTANT!**
 I have:
@@ -17,8 +23,9 @@ I have:
 - [ ] Checked that my JSON Syntax is correct ([options 2, 3, or 4](https://github.com/house-of-abbey/GarminHomeAssistant#editing-the-json-file) or otherwise)
 - [ ] Checked that my JSON follows the schema ([options 2, 3, or 4](https://github.com/house-of-abbey/GarminHomeAssistant#editing-the-json-file))
 - [ ] Used the online editor to check my JSON against HomeAssistant ([option 1](https://github.com/house-of-abbey/GarminHomeAssistant#editing-the-json-file))
-- [ ] Checked the [Docs](https://github.com/house-of-abbey/GarminHomeAssistant)
-- [ ] Checked the [Troubleshooting Guide](https://github.com/house-of-abbey/GarminHomeAssistant/blob/main/TroubleShooting.md)
+- [ ] Read the [Documentation](https://github.com/house-of-abbey/GarminHomeAssistant)
+- [ ] Run through the [Troubleshooting Guide](https://github.com/house-of-abbey/GarminHomeAssistant/blob/main/TroubleShooting.md)
+- [ ] Checked the [Known Issues](https://github.com/house-of-abbey/GarminHomeAssistant?tab=readme-ov-file#known-issues), i.e. the problems beyond the control of this Garmin application and must therefore be tolerated!
 
 **To Reproduce**
 Steps to reproduce the behavior:

Etiquette.md

@@ -142,6 +142,8 @@ On Mon, 6 May 2024 at 09:01, <noreply@garmin.com> wrote:
 
 ![Please help me set this up](images/etiquette/2024-05-06_GHA_Bad_Review.png)
 
+<img src="images/etiquette/2026-04-02_GHA_Bad_Review.png" width="70%" title="Not working">
+
 Answer: Make sure you meet the [minimum requirements for being a user](#etiquette) please! Provide more information on what the problem actually is. Clearly the support reply pointing to the documentation was either not read or not considered helpful, hence the point about meeting the minimum user requirements.
 
 On Fri, 31 Oct 2025 at 11:45, <noreply@garmin.com> wrote:
@@ -390,10 +392,10 @@ Don't get an embarrassing retort, I call out those who "click & complain" withou
 
 Two words. Perhaps too lazy to consider why others gave rave reviews and ponder what he was doing wrong? Perhaps did not consider there might be some documentation to assist or support routes (subject to [getting a polite reply](getting-help-with-a-polite-reply))?
 
-<img src="images/etiquette/2026-01-21 GHA_Bad_Review.png" width="70%" title="Two words">
+<img src="images/etiquette/2026-01-21_GHA_Bad_Review.png" width="70%" title="Two words">
 
 ---
 
 Blaming the wrong application. Just rude. Please get your facts straight. And it was such a simple workaround for the Garmin Connect IQ app bug.
 
-<img src="images/etiquette/2025-11-19%20GHA_Bad_Review.png" width="85%" title="Misplaced blame">
+<img src="images/etiquette/2025-11-19_GHA_Bad_Review.png" width="85%" title="Misplaced blame">