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

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?