grrrrr.

[blufive]

Dear Compuware,

Speaking as someone who writes web applications professionally, the web interface to TrackRecord is a huge, steaming pile of shite.

Let me enumerate the ways:

• Accidentally clicking the incorrect option in a dropdown list results in a bug being snatched out of my hands allocated somewhere I can't edit it.
• ditto if I carelessly used the mousewheel while focus is in the wrong place. This is why using "onchange" handlers to submit forms is BAAAAD, m'kay?
• Once I've started an edit, I can't escape. <valleygirl>Guys, like, Transactional database access? Duh!</valleygirl>
• Something resembling a useful search interface that doesn't require configuration of specific queries by a sysadmin would be cool, too.
• It corrupts its own database on a daily basis (ok, that's not necessarily the web interface, but I thought I'd slip it in anyway)

Yours, etc.

Dear Employer,

Give me a real bug-tracking system to work with. If you're too terrified of (for example) bugzilla, I'll even take the old in-house character-cell-based relic instead. It may use arcane keystrokes, but it only corrupts the database once or twice a week, and the search facilities let me slice'n'dice by client, or who's dealing with it, or when it was logged, or status, and I can scroll through lists of bugs a good deal quicker than the average glacier. Oh, and once a bug is closed, it disappears unless I specifically go looking for it, rather than just cluttering the place up.

Yours, etc.

Comments

[replyhazy.livejournal.com]

Let me just say: ewwwww!

An Excel spreadsheet would be better than that.