Status codes inform the users of the status of an issue. These are typically created at the time of installation and are based on company standards, but new ones can be made as needed for specific projects or types of projects.
Status codes are easy to add and modify.
To edit/change an existing status code, double-click it. You will then be able to change the text. Any changes will apply to all projects with that classification set specified on the Projects form.
The Order number indicates the order (top to bottom) in which the field values should be displayed in the create IssuesForm. In this example, the Status item is a checkbox list.
Issue Type #
Issue type codes categorize the type of issue or problem found. The ones in this example are specific to surveys. Issue types allow you to review the frequency with which a specific problem occurs. You can then use the information to pinpoint issues in the scripting process.
Some sites classify their issue types in detail; others limit issue types to three to five major categories. The choice is up to each site, but the more types you pre-define, the easier it is to later determine where problems occur in your survey process.
Internal codes can be screened by client testers.
Creating separate codes for client-requested changes might allow you to seek additional payments for changes made to projects after the client has already signed off on them.
One client found that, on average, 28% of changes made to surveys in the test phase were initiated by clients who saw the screen and then decided it did not look like they expected. One solution to the problem is to create a template library of sample screens with different grid layouts, logo placements, fonts, etc., which the client can select before coding begins. All subsequent changes are then billable.
Here are some additional samples of Classification Sets.
Sample Issue Types:
Change: Logic – Change to questionnaire to logic
Example: Change skip at Q2 for “No” response to go to Q5 instead of Q6.
Change: Screen Design – Change to questionnaire question screen design
Example: Request Q4 list be displayed in 2 columns.
Change: Text – Change to questionnaire to text
Example: Q20 typo in question text.
Correction: Logic – Logic programmed incorrectly based on questionnaire logic
Examples: Q13 should be multipunch.
“None of these” should be exclusive.
Skip Q29 if Q28 = “No one regularly uses my pool.”
Correction: Screen Design – Question displayed on screen incorrectly
Example: Add space between question text and respondent instruction.
Correction: Text – Text displayed on screen incorrectly
Example: 3rd response, “Vinyl Pool”, should be plural.
Very Detailed
