...
- General Information (see above for details)
- 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.
- Include which specific page, program, or report in the software is impacted
- If this ticket is related to specific records include the identifying information in the ticketIf you have screenshots that illustrate the issue, please attach those to the ticket
- 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 recreate 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: If you are able to recreate the behavior in a test instance, take attempt to determine if this is user or district specific. Take note if it only happens with the user that reported or if you were able to get that same behavior with another user. Attempt the test with another district's data to determine if it only happens for the district that reported the bug.
- 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.
...