Content Comparison

...

• Try to determine how to reproduce the error on staging:
  • Watch Fullstory if available
    • See section on Fullstory below
  • Check for api request : Under the exception trace, you may see an exact api request
    • Example: https://sentry.io/sighten/production/issues/422847366/
    • 
  • Open each line in the exception trace to see if there is a clear indicator of a failure on a specific field
    • Example: https://sentry.io/sighten/production/issues/426038336/
    • The example above shows that the field "ssn" has a specific pattern "[^0-9+]" that is not met.  This can then be communicated to the user in order to allow them to move forward.
  • If you have full steps to reproduce and are certain of priority:
    • If E1, add to current hotfix and leave unassigned
    • If P1, add to current sprint and leave unassigned
    • If P2, add to current design sprint and assign to Mariya
    • If P3, leave in backlog and assign to Mariya
  • If you are uncertain of steps to reproduce and / or priority
    • Add to current sprint and assign to lead developer for the sprint
    • Lead developer for any given sprint can be found in Release Tracker
      • https://docs.google.com/spreadsheets/d/1SJfMj9iIlXoQtpMB4DM0DqQz_pAkdCC1X0liEjHN91Y/edit#gid=1049894141

Prioritization:

• Impact on deal
  • If there is no workaround to get through a deal, then the ticket is automatically E1
  • Example: User cannot download a contract
• First seen
  • Did an error start occuring after a recent release?

• Number of events

• Number of users
  • Ignore all sighten users, such as admin@sighten and sightenadmin@

Closing Ticket:

• If ticket is deemed as won't fix
  • Ignore for 6 months
  • Close Jira Ticket
    • Resolution as Won't Do
    • Add reason it is low priority
    • Communication Audience: Internal 

Ignoring Errors:

Errors that are determined should not throw errors:

...