The Operations Workstream uses a triage process to identify, recreate, troubleshoot, resolve, or escalate issues outside of expected behavior in the production environments of the ShapeShift product suite and services. This process is evolving as the DAO’s contributors, resources, and services grow and this documentation will be updated to reflect changes and optimizations.

Caught a bug? Report it!

🐛 The evolution of a bug 🦋

• How to report a bug 🐛  by making a Thread in #operations-publicchat
• Bug report details

For Operations Contributors to consider when responding to a bug report:

1. Does a clear cache fix the issue? Is the Issue re-createable in an incognito browser session?
2. What Products does this issue affect? - Is the issue be specific to wallet, browser, device, platform, service, etc)
3. How many users does this affect currently? - Good measurement of affected users that can help assess priority.
4. Does this issue currently affect the users ability to interact with their money? - A major line in the sand between a bounty-able bug and a potential #Prod-Issues post

• 2. How a bug 🐛  goes through the triage process
• 3. How recreate-able bugs 🐛🐛🐛  evolve into GitHub tickets