I don't know where you plan on heading with this, but there are a couple things you could probably do with this, as well. As a part of your standard "adding their project to the tracker" process, you could also register their e-mail address(es).

You could then have your app listen for incoming e-mail messages in order to auto create tickets, etc. I have always had a hard time getting clients (back when I freelanced) to actually visit a bug tracking tool and input information. It usually involved them e-mailing me and me manually adding the bug.

Github integration (at the project level) would allow you to target your bugs with commit messages and then see which code was committed to resolve each bug (much like it works with github issues at the moment, but with your private solution.)

Sorry for rambling. Caffeine.

I'd say: You know very well what you need, so go ahead and create something that fits your needs. You'll end up with a solution for yourself, and I'm pretty sure there are people out there for whom this solution fits too. (Unless, of course, this is primarily about creating and selling a product.)

By the way, despite there being PLENTY of bug trackers out there, most of the people I talk to are not satisfied with the bug tracker they use.

I've noticed this as well. In general, there seem to be some kinds of tools which are very personal. Issue trackers, TODO-lists, notebooks. I'm pretty sure it is impossible to satisfy everyone with a single tool. Everyone wants to optimize it for themselves.

In these cases I think a decent solution would be to make a general backend service and well-defined data format (for interchangeability) but make it easy to add customized (their own or third party) frontends/skins by individual users.

Next time I meet somebody who's unhappy with their bug tracker, I'll ask if customizing it would be an option for them.

EDIT: I like the simple design.

EDIT: Keeping it simple is the key. A ticket to me is either "urgent" or "normal." Why should there be 4 priority levels, it never made sense to me.

It seems like you would be competing with things like Google Docs.

Even in my scenario I often have higher-level "stakeholders" reporting bugs to me via email, skipping over their own bug tracking systems.

One challenge would be making it more appealing to those bug reporters than using email. Maybe you can have it receive email and parse it into a bug? For people who won't sign into a separate web app.