...
Under Description, describe the bug in more detail. Include the following information:
What account is it happening on? One user or a single user? Describe the bug and include details of what troubleshooting steps have already been taken.
What part of the job or workflow is affected? Is it on the quote phase? Is it happening in the user setting? Let us know!
Important information to link as applicable (as many as possible):
Job url/site link
Sentry link, if an error was thrown
Fullstory link
Detail everything you attempted to de-bug.
...
Make sure to select the Environment where the bug is happening. It is defaulted to Prod (engine) but change it from the default if it happened on Onboard, Staging, etc.
Scroll down and enter the rest of the required information.
Under Logged in as, enter the user that is receiving the error
Under Steps to Reproduce, enter the exact steps to reproduce the bug. Sometimes it is not always clear, but give the steps taken that you did to get the bug. In cases where the steps are not clear, it is very important to include a Sentry and Fullstory link.
Be as detailed as possible!
The best steps to reproduce do not include engine.
Under Actual Result, describe the bug. For example, if sending a proposal fails, under Actual result enter, "Proposal will not send".
Under Expected Result, describe what should happen. From the example above, the expected result would be, "Proposal email should send".
...
Click Create and the bug is created.
Slack the #CustomerSupport channel with the bug link and include @channel in the message so a Product Manager can assess how to prioritize. Please include a detailed description in the post as well.
Circle Back With Customer
...