When would I use this instead of Jira or Github Issues?

Github sync would be nice.

Zendesk integration would be nice.

The few scenarios in which I imagine it would make sense to track bugs outside of Jira or Github Issues are when the bug reports arrive to a customer support desk and the bug needs to be linked to 1 or more customer tickets and tracked within Zendesk, and yet the actual work against the bug item is being tracked in Github Issues (or Jira, etc). Whereby some property on the issue can be modified to indicate severity and impact (i.e. fixing this would close n customer tickets of which the highest severity is x), so that something is gluing together the disparate systems that exist around a bug.

A bug tracker by itself... doesn't feel as valuable as the integration that enables the smooth management of a bug for all those who interact with it.

A mature bug system might even have complex routing rules, so that Zendesk automation can apply, if tagged as X, create an issue against this repo and link these two things together, and to even allow the moving of the downstream ticket between systems of differing types, i.e. "this ticket doesn't apply to this Github repo, move the ticket to Jira as it does apply to that other team".

Then as the master view of bugs and debt across the company (even spread across multiple repos, systems, issue trackers) a bug tracking tool now makes a lot of sense.

Does that make sense?

Your landing page talks all about workflows, so I'm unclear how this meets your own stated goal of being focused less on workflows and more on helping the team close bugs faster. From reading your page, I don't see a single feature that isn't already in Jira. I also have no ideas why reminding people to do their work is an issue to be resolved by software - sounds like a cultural problem, not a tech problem.

In any case, I don't think your problem is that you are missing features. It is that you are aiming for table stakes, and aren't showing us anything new and exciting.

If you want to truly change how teams operate and present us with a new model for managing and closing bugs, then you need to live up to your own description, move away from workflows and "my bugs" listed on pages, and show us something completely new.

We are trying to be less workflow focused and more closure focused. I do see how it might not be clear on the landing page.

You are right, we have limited features. That is because we are a small team and we want to have only the minimum features required for bug tracking (and not everything JIRA has). But, what we do intend is to go deep into this space and really question how we have all been building software and managing bugs.

The nudging people to move issues is indeed a culture thing. And the intention is to bring in culture building as part of the platform. This will reinforce and make resolving issues a much needed thing in our space.

The wrong culture is a bug, and maybe bugasura will help fix it. :)

I really like Sentry to track my bugs. However, it lacks some workflow, so I'd say I expect a Sentry with a light Jira (a Trello ?) to follow fixings

Will checkout Sentry. What do you mean by it lacks some workflow?

Is the name intentionally sounding like "basura"? In Spanish it means "trash"

no, it is based off a mythical man-eater called Bakasura https://en.wikipedia.org/wiki/Bakasura