CasperPanel Suggestions: Difference between revisions
(Created page with "{|align=right |__TOC__ |} = '''<span style="color:#00528c">Suggestion Tickets</span>''' = The new suggestion system in CasperPanel is streamlined to be less confusing to...") |
m (→Bugs) |
||
| (11 intermediate revisions by 2 users not shown) | |||
| Line 4: | Line 4: | ||
= '''<span style="color:#00528c">Suggestion Tickets</span>''' = | = '''<span style="color:#00528c">Suggestion Tickets</span>''' = | ||
The new suggestion system in CasperPanel is streamlined to be less confusing to non-technical people. | The new '''[https://www.casperpanel.com/suggestions 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. | However, there are a few guidelines to follow if you want Casper to consider your feasible idea. | ||
== '''<span style="color:#00528c">Bugs</span>''' == | |||
To ensure that we can see and respond to bugs as quickly as possible, please report them directly to us via the '''[[CasperVend_2/Getting_Help#2.29_When_Casper_is_offline:_By_IM-to-Webform_.28Preferred.29 | IM to webform process]]'''. | |||
== '''<span style="color:#00528c">Read The Rules Popup!</span>''' == | == '''<span style="color:#00528c">Read The Rules Popup!</span>''' == | ||
That information is there for a reason, please read it. Also, the suggestion system is ONLY for suggestions - support issues go through '''[[CasperVend_2/Getting_Help#2.29_When_Casper_is_offline:_By_IM-to-Webform_.28Preferred.29 | IM to webform process.]]''' | That information is there for a reason, please read it. Also, the suggestion system is ONLY for suggestions - bugs and support issues go through '''[[CasperVend_2/Getting_Help#2.29_When_Casper_is_offline:_By_IM-to-Webform_.28Preferred.29 | IM to webform process.]]''' | ||
== '''<span style="color:#00528c">Title Should Be Descriptive</span>''' == | |||
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 | |||
== '''<span style="color:#00528c">Summarize Your Suggestion</span>''' == | == '''<span style="color:#00528c">Summarize Your Suggestion</span>''' == | ||
The initial suggestion description box should have a 1-2 sentence '''summary''' of the suggestion, without a lot of details. | 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 declined.''' | 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 === | === Bad Example === | ||
---- | ---- | ||
: 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. | : '''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 === | === Good Example === | ||
---- | ---- | ||
: Add a bulletin board with owner/group/manager/public security capability. | : '''Initial suggestion box:''' Add a bulletin board with owner/group/manager/public security capability. | ||
== '''<span style="color:#00528c">Subfeatures/Requirements Go In Comments</span>''' == | == '''<span style="color:#00528c">Subfeatures/Requirements Go In Comments</span>''' == | ||
All of the little details you can think of for that product go in a '''comment''' - or multiple comments - to that ticket. | 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 === | === Bad Example === | ||
---- | ---- | ||
: 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. | : '''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 === | === Good Example === | ||
Latest revision as of 16:39, 19 November 2020
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
To ensure that we can see and respond to bugs as quickly as possible, please report them directly to us via the IM to webform process.
Read The Rules Popup!
That information is there for a reason, please read it. Also, the suggestion system is ONLY for suggestions - bugs and 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.