Filing a Bug Report

Bugs happen! Tips on how to file a bug report

Written By Micah

While we try to make sure Strike Graph is as bug free as possible, we are after all only human (well, except for Security Assistant and Verify AI).

If you run into an issue or a bug, and you're unable to troubleshoot the issue yourself, here are some ways to get additional help:

  1. Use the Strike Graph Chat Feature (located in the bottom right corner of the platform) to start a chat with Fin. This AI agent is built into our Help Center and has access to a big library of additional information. It can't answer everything, but it's a great place to start. Since Fin is an AI, it can look across the entire Help Center library at once to identify potential solutions, something that would be pretty hard for a human to do.

  2. Ask Fin to get someone from Customer Success involved. Fin can ping members of our team to hop into the chat to assist with questions or issues that Fin is unable to solve. We're available during normal business hours (in multiple US time zones) and are always happy to help you overcome obstacles as best we can.

  3. Reach out to your Customer Success representative. They can either be called into the chat, or you can send them an email. If they don't have the solution themselves, they'll know who to bring in to help out.

  4. Email support@strikegraph.com; while this goes to the same people as the chat messenger, sometimes you just want to communicate over email! We get that.

What information should you share in a bug report?

Well, I'm glad you asked! While we can usually narrow down your issue by spelunking through our logs, sometimes finding the root cause of a problem is harder than it seems. You can help us out by providing the following in your bug report:

  1. What browser are you using?

  2. What time did you experience the problem?

  3. Can you describe what you were doing before you experienced the issue?

  4. How long have you been experiencing this problem?

  5. Are you using any privacy blockers or other browser extensions (these often get in the way)?

  6. What have you already tried doing to resolve the issue?

  7. Are there any errors in the browser console (and can you provide a screenshot)?

Including this information will help speed up our support efforts and help us get you back on track as quick as possible.

How do I take a screenshot of my browser console?

You may already know how to do this, but just in case you don't, providing a screenshot that shows your browser's console is super helpful. Here's how you can do it:

  • Go to the where you would normally experience the issue, but before triggering the bug...

  • Open the Developer Inspector (in Chrome, it's cmd+option+i on a Mac, or ctrl+shift+i on PC, and it's pretty similar in most other browsers)

  • Click on the ‘Console’ tab

  • Enable ‘Persist Logs’ by clicking on the gear icon on the right side of the console tab, and then ticking the box next to the setting.

  • ... now you can proceed to recreate the bug.

  • Once you hit the issue, take a screenshot