...
- Testing: Discuss with the district and take note of any district specific processes that may be relevant. Include details related to your testing, example transactions, steps taken, etc. in your ticket. Depending on the issue, it can be helpful to use a test instance of their data to review the process they are asking about. Questions that are not related to making database changes (ex. running a report) may be tested in their live instance. If you are unable to confirm the same details reported by the district, please include a summary of the steps you’ve attempted.
Report a Bug
- General Information (see above) District Name, Time Sensitive, Record Specific Information, Reports, Errors
- Description of the Issue: Please include a detailed description of the behavior that the user is experiencing and which specific page, program, or report in the software is impacted. The more detail the better as this will help us expedite the process of looking into the issue on our end.
- Include which specific page, program, or report in the software is impacted
- If you have screenshots that illustrate the issue please attach those to the ticket
- If you are referring to specific totals on reports, please attach a copy of the report with the Report Options Page
- If the bug report you are including is copied directly from the district’s email/ticket to you please include additional information on what you’ve looked at so far
- Recreate the Issue: Discuss with the district and take note of the actions they took directly prior to receiving the error or encountering the issue. We recommend creating a test instance of their data to try to reproduce their issue. Issues that do not require database changes (ex. running a report) may be recreated in their live instance. If you can successfully reproduce the issue, please include an example with the steps to recreate in the ticket. If you are unable to recreate the behavior reported by the district, please include a summary of the steps you’ve attempted.
- Determine if this is specific to a district or user: This depends on what the issue is, but generally this is helpful to determine ahead of time. If you are able to recreate the behavior in a test instance, take note if it only happens with the user that reported or if you were able to get that same behavior with another user.
- In a situation where multiple districts are reporting a bug at once, include the name of all districts and if there are any similarities/differences.
...