Content Comparison

...

• All Production sentry error's reviewed
• 0 open E1 / P1 issues in SEN project in JIRA
• All Sentry errors on sentry-prod E1 or P1 errors
• Error's addressed based on appropriate priority
• Minimal noise (metric?)
  • Minimal sentry errors silenced
  • Minimal sentry errors ignored

Daily Process:

...

For all new

...

tickets in Jira SEN project:

• Add steps to reproduce to ticket
• Add priority to ticket:
  • E1
    • Highest Priority Error 
    • Main functionality blocked, user cannot proceed with deal
    • Hotfix prior to next release
  • P1
    • High Priority Error
    • Key functionality heavily degraded, large number of users impacted
    • Include in next release
  • P2
    • Medium Priority Error
    • Clear bug
    • Include in next 4-6 weeks
  • P3 
    • Low priority Error
    • Minor bug
    • Keep in backlog
  • Not a bug
  • Needs Aggregation
    • Error is creating multiple tickets in Jira
    • Please use one ticket as the "aggregation" ticket to clean up the error handling and ensure the error is thrown in a way that merges all instances together
• Add sprint to ticket:
  • 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

How to check an error:

• 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.
  When finished checking, mark in some way indicating reviewed

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

• Number of events

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

...