User Tools

Site Tools


hortus:support:requests

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

hortus:support:requests [2026/04/01 17:19] – created savino.frisardihortus:support:requests [2026/04/07 15:01] (current) savino.frisardi
Line 1: Line 1:
 ===== What to include in a useful support request ===== ===== What to include in a useful support request =====
  
-A good support request improves response time and accuracy. +^ Include this ^ Why it helps the support team ^ 
- +**The module or page name** | Support can route the request to the correct feature area faster. | 
-Include: +**What you were trying to do** | A short goal statement is more actionable than "it does not work". | 
- +| **The exact step where the issue happened** | Reproduction becomes much easier for maintainers and developers. | 
-  clear description of the problem +**A screenshotpage titleor link** | The team can identify the correct UI state quickly. | 
-  steps to reproduce the issue +| **Your role and sign-in state** | Many features are permission-aware, so the team needs to know whether you were a visitor, user, contributor, or maintainer. | 
-  expected vs actual behaviour +**Any error or visible message** | Even partial wording can help identify the failure class. |
-  screenshots (if available) +
-  relevant context (modulefeaturerole) +
- +
----- +
- +
-==== Example structure ==== +
- +
-  What you tried to do +
-  What happened +
-  What you expected +
-  Where it happened (module/page)+
  
 ---- ----
hortus/support/requests.1775056743.txt.gz · Last modified: by savino.frisardi