Correct, this wouldnt be for anyone who works in a large team or corporation. I have a couple of friends who work exclusively with ordinary folks and small businesses. Everything is communicated via email when it comes to feature requests and bug tracking.
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.
Comments
Correct, this wouldnt be for anyone who works in a large team or corporation. I have a couple of friends who work exclusively with ordinary folks and small businesses. Everything is communicated via email when it comes to feature requests and bug tracking.
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.
I think it's a good idea.
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.
Yup! That was the first thing I thought of, how to make the process easy for the clients.