...
- Log into sentry: https://sentry.io/sighten/production/
- Make sure the projects filter at the top has Production selected
- Sort by "Last First Seen"
- Review all errors un-assigned errors in the queue
- Tues - Fri - This should generally be all errors created in the the last 24
- Mon - This should generally be all errors created since Friday
- After reviewing an error, assign error to yourself so it is clear it has been reviewed
...
- 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
- 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
- Watch Fullstory if available
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@
...