Page Comparison

...

• Reports

  • If this ticket is related to a specific report, please include the report name and/or attach the report(s).

  • If you are referring to specific totals on reports, please attach a copy of the report with the Report Options Page
• Errors
  • The error detail/stack trace is usually a long technical message. When reporting an error, this can be extremely helpful in locating the cause of the reported issue.
  • If the error message has a double-arrow icon, click this to expand the full error detail and copy/paste into a .txt or word document and attach it to the ticket. 
    
    
  • If the district encountered the error and the entire error message was not captured at that time:
    • Recreate the error in a test instance to capture the full error detail and copy/paste into a .txt or word document and attach it to the ticket. 
      OR
    • Discuss with the district what time they received the error. Navigate to System > Monitor > App Log and use that information to locate the record of the error. Locate a row for the error, click directly on the row to open the detail view and copy/paste the data from the Exception Detail box into a .txt or word document and attach it to the ticket.
      

New Feature/Enhancement

• General Information (see above for details)
  • District Name
• Description of the Enhancement Request: A description of the functionally they are requesting. Please include any relevant details - which page, program, report this request is related to. 
• How this enhancement will help: When possible, please include a summary of how they see this enhancement benefiting them and any additional details on their process that may be relevant to their request. The feedback issues are brought to the Prioritization Committee for consideration and discussion. That committee is made up of ITC & District representatives. However, districts may have different practices and not all use the software the same so any additional details provided at the time of request may help with prioritizing the feedback request for a future update.
• Feedback Issue: (optional) If you are aware that there is already an issue in Jira for this Feedback request, please feel free to include the USASFB, USPSFB, or INVFB number in the ticket. When we receive enhancement requests, we will review the existing feedback requests. If a feedback request already exists for the New Feature/Enhancement, we will update the Times Requested count on the Jira Issue. The number of times requested is used in determining priority of scheduling that issue for a future update.

...

• General Information (see above for details)
  • District Name
  ,
  • Time Sensitive
  ,
  • Record Specific Information
  ,
  • Reports
  ,
  • Errors
• Question: Please include a summary of the situation/question.
  • Include the specific page, program, or report in the software your ticket is related to
  • If this ticket is related to specific records include the identifying information in the ticketIf you have screenshots, please attach those to the ticket
  • If the question 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
• 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.

...

• 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 ticket
  • If 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 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 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.

...