⭐️ Making Jira tickets better

Bug reporting done wrong makes people hate what they do. You might be familiar with this scenario:

You login to Jira on Monday morning and there are 3 new bugs posted with your name on them.

You’re reading the first bug description for the 3rd time and still can’t quite grasp the context in which the reported bug occured. There are missing screenshots, the description is vague and it seems like the user might be using an older version of your product

Reluctantly, you send an apologetic message to Alice who reported the bug and… wait.
Crickets for days, until Alice gets back to you and finally you manage to jump on a conference video call with them to analyze what caused the issue.

Now imagine this is your daily routine, and you have multiple bug tickets to deal with.

The stats speak for themselves: more than 75% of projects cause their team leads to feel stressed. In a world where project management is crucial to success, we all dream of product and engineering teams working together stress-free

Bug reporting/fixing is part of every project’s lifecycle.

To empower teams, at Dashcam we want to make it super easy and super efficient for teams to smoothly collaborate and report software bugs and issues.

If you can fix bugs 10X faster, you are able to optimize your product quickly, increase user retention, decrease dissatisfaction (internal and external) and focus on your features backlog not your bug backlog.

Part of fixing bugs as we know it, leverages 3 things:

  • Good repro steps: Show exactly what leds to a frustrating software issue, as a customer or internal user
  • Error data: Logs, most importantly – truly help developers understand what the error is caused by
  • Good bug management: this usually means you’re using a tool like Jira or Notion to track bugs, assign priorities, and processes to ensure the fixes are shipped!

There’s no doubt that bad ticket management slows engineering teams down, but there are other factors too:

  • missing context
  • lack of bug “evidence”
  • bug reproduction steps
  • error logs

These are building blocks of bug reporting. If missing they cause a slowdown (sometimes block) the velocity of fixing software issues.

Our aim is to remove these barriers, and by automating it we can achieve this: reduce extra work and improve processes around bug reporting and fixing.

In the dream world, you clip a software issue as soon as you encounter it, then you seamlessly have a ticket in Jira with all the information needed for someone to work on it.

To solve this, we created our first native integration for Jira available to anyone using Dashcam!

How it works

By clipping a video and uploading to a Dashcam project in your workspace (after activating the Jira integration), Dashcam wil seamlessly create a ticket in your board. This way you don’t have to spend time creating tickets or gather evidence, manually.

Our internal tests proved that using Dashcam truly saves teams time.

The tools that Dashcam gives you are built to improve your processes. Here are some benchmarks using different apps that show how long it would take an individual to create an actionable bug-report ticket in Jira.

The process follows a typical bug report flow:

  • A user identifies a problem (bug)
  • A user builds up a case with evidence of the problem
  • A user creates a ticket in Jira to alert the team of the problem

Using Dashcam will save you time and reduce stress and errors – it’s automated – by putting everything in easy-to-use app.

Trying the integration

To get started, navigate to your Workspace, and connect a project with Jira by following the instructions described here! Please reach out for questions, and let us know how you find our first native integration.

Leave a Reply

%d bloggers like this: