(Replace this first paragraph with a brief description of your new category. This guidance will appear in the category selection area, so try to keep it below 200 characters.)
Use the following paragraphs for a longer description, or to establish category guidelines or rules:
Why should people use this category? What is it for?
How exactly is this different than the other categories we already have?
What should topics in this category generally contain?
Do we need this category? Can we merge with another category, or subcategory?
Technical Support & Troubleshooting- Get help resolving bugs, errors, or technical issues. Share diagnostics, find solutions, and report broken functionality.
This category is the designated place for users to seek assistance when the product or service is not working as expected.
Why should people use this category? What is it for?
It prevents bug reports from cluttering other categories (like General Discussion or Feature Brainstorming).
It allows experienced users and staff to quickly identify, diagnose, and provide workarounds or fixes for common problems.
It serves as a public knowledge base of known issues, allowing users to find existing solutions before posting a new question.
How exactly is this different than the other categories we already have?
Difference from “How-To/Tutorials”: That category is for teaching users how to use working features. This category is strictly for discussing broken or faulty functionality.
Difference from “Feature Brainstorming”: That category is about future changes. This category is about fixing current problems.
Focus: The discussion is focused on diagnosis, error messages, system configuration, and reproduction steps, rather than opinions or general conversation.
What should topics in this category generally contain?
What should topics in this category generally contain?
Topics must contain sufficient detail for others to understand and potentially replicate the issue. A well-formed technical post should include:
Clear Title: State the exact problem or error message (e.g., "Error Code 404 on login, "Widget disappears after update, “Database connection failing”).
Environment Details: Specify the relevant setup. This is often the most crucial detail.
Examples: Operating System (Windows 11, macOS Sonoma), Browser (Chrome 120, Firefox 121), Product Version Number, Hardware.
Steps to Reproduce: A numbered list showing exactly what you did before the issue occurred. If the issue cannot be reliably reproduced, state that.
Observed Behavior (The Problem):Describe what happened (the unexpected result). Include the exact error message text or a screenshot.
Expected Behavior: Describe what should have happened (the correct result).
Note: Do not share personal identifying information (PII) like passwords or account numbers in public posts. Share logs/diagnostics via secure private message if requested by staff.
Recommendation: This should be a standalone, high-visibility primary category. For clarity, we could enforce tags like [BUG], [ERROR], [BROWSER], etc., to help filter and organize the reports within the category.