CasperPanel Suggestions: Difference between revisions
No edit summary |
No edit summary |
||
| Line 10: | Line 10: | ||
== '''<span style="color:#00528c">Bugs</span>''' == | == '''<span style="color:#00528c">Bugs</span>''' == | ||
We no longer accept bugs via this system. Instead, please report bugs directly to us via a support ticket. This way we can prioritise them better. | We no longer accept bugs via this system. Instead, please report bugs directly to us via a [[CasperVend_2/Getting_Help#Contact_Us_Directly|support ticket]]. This way we can prioritise them better. | ||
== '''<span style="color:#00528c">Read The Rules Popup!</span>''' == | == '''<span style="color:#00528c">Read The Rules Popup!</span>''' == | ||
Revision as of 12:55, 23 February 2018
Suggestion Tickets
The new suggestion system in CasperPanel is streamlined to be less confusing to non-technical people.
However, there are a few guidelines to follow if you want Casper to consider your feasible idea.
Bugs
We no longer accept bugs via this system. Instead, please report bugs directly to us via a support ticket. This way we can prioritise them better.
Read The Rules Popup!
That information is there for a reason, please read it. Also, the suggestion system is ONLY for suggestions - bug/support issues go through IM to webform process.
Title Should Be Descriptive
To be able to determine what a suggestion is about in a list, the suggestion ticket should have a non-vague title. It helps with determining what each ticket is about on the "all tickets" page, but it also helps prevent other commenters from adding ideas for the unrelated products on your suggestion.
For example, if you're trying to suggestion bulk configuration options for a specific product, instead of:
- Title: Bulk configuration options
The title should be something more like:
- Title: add <productname> bulk configuration options
Summarize Your Suggestion
The initial suggestion description box should have a 1-2 sentence general summary of the suggestion, without a lot of details.
Don't be too vague, but don't fill it with all the subfeatures and requirements you can think of, either. If you put too much information in the initial box, the suggestion will be automatically declined.
Bad Example
- Initial suggestion box: Add a bulletin board with owner/group/manager/public security capability. Message board should have web access, wall and freestanding versions, customization capability, use mesh for lower prims, and link to specific systems.
Good Example
- Initial suggestion box: Add a bulletin board with owner/group/manager/public security capability.
Subfeatures/Requirements Go In Comments
All of the little details you can think of for that product go in a comment - or multiple comments - to that ticket. The reason is because Casper tries to keep his products to a single script, and there may not always be room to add everything. Things in comments are recognized as "wish list" or "nice to include" features, and will not inherently prevent a ticket from being approved.
Bad Example
- Initial suggestion box: Add a bulletin board with owner/group/manager/public security capability. Message board should have web access, wall and freestanding versions, customization capability, use mesh for lower prims, and link to specific systems.
Good Example
- Initial suggestion box: Add a bulletin board with owner/group/manager/public security capability.
- Added comment: Message board should have web access, wall and freestanding versions, customization capability, use mesh for lower prims, and link to specific systems.