hortus:support:requests
What to include in a useful support request
| Include this | Why it helps the support team |
|---|---|
| The module or page name | Support can route the request to the correct feature area faster. |
| 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. |
| A screenshot, page title, or link | The team can identify the correct UI state quickly. |
| 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. |
| Any error or visible message | Even partial wording can help identify the failure class. |
hortus/support/requests.txt · Last modified: by savino.frisardi