> I don't think you'll ever find a finished bug-/issue-tracking solution that > caters just as well for newbies and developers. The main reason is (of > course?) that most issue tracking software is written for developers, by > developers with little or no experience or thought as to what makes a good > end-user experience. Also, most issue tracking tools are *made > deliberately* to work best for developers - with human (end-user) > interaction kept to a minimum. That's also why most issue tracking > solutions end up looking like glorified (not the good kind) spreadsheets > (Mantis, Flyspray, others?), something the IRS would want you to fill out > (BZ, OTRS, RT, others?), or some kind of bastard child in-between (The Bug > Genie, Redmine, Jira, Fogbugz, others?). >
I'd like to go one step further. There is not a single good bug/issue tracking system in existence. Yes, I'm completely serious too. I've come to believe that it's impossible to make one that anyone will be happy with. That includes most developers of tracking systems too (I've written one, and I hated it, though I liked it better than what I was using before). We can complain about this till the end of time. This discussion is even worse than bikeshedding discussions. At least with bikeshedding discussions you end up with a color for the bikeshed. When discussing bug/issue trackers you just end up with the same tracker, or another crappy tracker. - Ryan _______________________________________________ Wikitech-l mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/wikitech-l
