-----BEGIN PGP SIGNED MESSAGE-----
Back when I did some bug triage in Oct'08, I drew up this list of
requests, rants and questions (I haven't checked recently to see if
any are now no longer relevant) that made my workflow slower.
I'd like to have these addressed, in some fashion, either by modifying
Tracker, or by denying the request.
- --- Vladimir
1. If a submission fails, please do not clear any fields, in
particular "Module" and "Platform".
2. Please add "x86_64" to the list of platforms.
3. If it is not the case that Linux is assumed, please add "Linux" to
the list of platforms.
4. It would be nice if there were a "Next" button (like in Bugzilla)
to go to the next issue in the current list. (I happen to be working
off the Open issues list, so "Show Open" works for me.)
5. Shouldn't every issue have a status of at least "New"? If so,
please make it the default when submitting or modifying an existing
issue which does not have a status set.
6. If an issue is the result of the interaction between two modules,
then the "Module" field will not capture essential information since
only one module can be specified. The "Module" field should be a list.
7. There is no way to save the current issue list or to re-load a
previously created issue list.
8. Comment text should be forcibly wrapped (or should be an option).
See Issue 150 for an example of an issue that's hard to read.
9. "core code other" should be broken up[sic] into "core code other"
and "core code lisp", with "core code other" covering lib-src and
lwlib and "core code lisp" covering (obviously) the core lisp code.
10. "Make a copy" doesn't work and returns errors.
11. The Comment field seems to start up with a number of spaces and/or
tabs. So, when clicking anywhere except at the very beginning, the
cursor is misplaced. The spaces & tabs should be removed.
12. The automated transition to "deferred" after one month of
inactivity doesn't seem to work. I've opened 8 month old issues that
are still "chatting".
13. When I forgot to fill in "Module", "Submit Changes" reported
something like "Required issue property platform not supplied." This
should refer to "module" not "platform". (But, next time it worked,
maybe I'm hallucinating.)
14. There should be an "N/A" in the module list, for use when the
issues is not a bug. Same comment for "Type".
15. The elements in the platform list seem to be missing some entries:
Linux, Solaris, lwlib, motif, SPARC, but nt is mentioned even though
mswindows is in the list. And what is "stream"?
- --- Vladimir
Vladimir G. Ivanovic
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org
-----END PGP SIGNATURE-----
XEmacs-Beta mailing list