Our team works hard to provide you with an efficient and delightful user experience. But as with any software out there, there may be instances that bugs happen here and there or you have some wonderful suggestions to make the site better.
Either way, we would love to hear your feedback and receive it in as much detail as you can provide.
1. On the home page or on the Help menu, click Email Support.
2. Fill out the email support form. Please refer to the next section for detailed information.
Please copy and paste the template below into the form and fill it out.
Include the word BUG at the beginning of the subject line.
Here is a good example of a bug report:
1. URL of the page you were on https://intelliriversource.groovehq.com/help/how-to-report-bugs-and-suggest-improvements#
2. Environment or Machine specs: Windows 10, Google Chrome
3. Steps to reproduce the problem:
a. opened the Get in Touch on a new tab
b. clicked the help "? widget
c. collapsible section/panel pulled up, but no KB articles were listed/shown on both Knowledge Base and Contact Us tabs
4. Expected behavior: Collapsible section/panel should show the list of options
5. No error messages (please see attached).
Please copy and paste the below text into the form and fill it out.
1. Page/feature you want to suggest improvements on.
2. Detailed suggestion with expected behavior:
3. Attach any screenshots:
1. Subject line: Add ‘BUG’ at the beginning of the subject and include a brief description of it.
Bugs are top of our priority list and seeing it in the subject line makes it faster for the team to triage tickets and prioritize.
Example: BUG: error filtering articles
2. Description: Provide a detailed description of the bug and steps to reproduce it.
Being able to reproduce the bug helps the team in investigating what has caused the error.
Here is a brief checklist of what to include in the description:
• URL of the article or page where the bug occurred
• Actions/steps you performed that lead to the bug (buttons clicked, links clicked, queries copied, fields edited)
• Provide a brief explanation of your expected correct behavior
3. Provide screenshots:
Sending a screenshot in your bug report is necessary as it will help the developers get a visual of what’s happening on your end. Sometimes we may not be able to reproduce the bug, but would still occur on your end. So it is very beneficial for the development team to see what you see on your screen.
