| 2005-05-26 13:16:45 |
Matthew Paul Thomas |
description |
I just got a notification email after editing bug 785 where the description change was reported like:
- Changed description to:
The default sort order (and it's not configurable) for the
bugtask listing is simply bug ID, descending. I feel that the
default sort order should be something like severity (highest to
lowest), then priority (highest to lowest.) I think it would
probably be useful if: * each column in the search listing
were clickable to sort on * the cursor was positioned in the
search text/bug id box by default * the default number of bugs
shown were bumped up to, say, 500. i think this number would
make paging a fairly rare occurrence (with any kind of
moderately useful filter criteria! :) and allow the user to do
their work more efficiently by reducing the number of clicks
required to go through the bugs that interest them. * the
advanced search page were extracted into a separate page linked
to from the task listing. this allows us to more easily group
all the search widgets together. when criteria is entered and
the user clicks "Search" they would be returned to the bugtask
listing with the appropriate results, and a small area near the
top of the listing displaying what the filter criteria was used.
* the left-to-right ordering of columns where something like:
bug id, severity, priority, assignee, package (for
distro/distrorelease listings), status, title * the title
should wrap as needed, no "..." shortening
It appears that this edit notification email is not respecting newlines in descriptions. |
Description changes are currently reported like this (using a change to bug 785 as an example):
- Changed description to:
The default sort order (and it's not configurable) for the
bugtask listing is simply bug ID, descending. I feel that the
default sort order should be something like severity (highest to
lowest), then priority (highest to lowest.) I think it would
probably be useful if: * each column in the search listing
...
It appears that this edit notification email is not respecting newlines in descriptions.
The fix for this bug may share some code with bug 130. |
|
