I am not trying to be rude. At the same time, I will show you respect only if you ensure the same. Whatever "dick" category you are talking about, I haven't fallen into. Neither am I afraid of falling in that category in somebody's books who not understand my requirements totally. You have actually done me great service by letting me know that nothing of this kind exists. That has furthered my motivation in developing something like this. It may not be called a bug tool. Possible. But that does not make my requirements go away. The idea behind the tool is that, in most small teams there is always a trade off between fixing bugs and writing new features. Unlike, large software companies, the development team size does not fluctuate with new requirements. This is where a true reflection of the bug vs feature debate needs to be considered in greater light. As to points 3 and 4 not being a part of the features list of a "bug tracking system" I accept. But I still maintain that it does not call for unparliamentary language. Finally, your estimates of this thing taking several developers more than a year to develop is way off my estimates. This perhaps because, you don't seem to really see the "threadbareness" of the application in my mind.
Abhishek theBOKA It is impossible to change your past. But it is very possible to ruin your present by worrying about the future. -Chankya