Comment 12 for bug 29495

Revision history for this message
era (era) wrote : Re: Bug statuses should be better explained

Joey Stanford,

These issues are related, but what I would expect (based on other bug trackers, for example Bugzilla) would be for the header to link to an explanation, and the field itself to be editable.

In pseudo-HTML, something like this:

  <table>
    <tr>
      <th><a href="link explaining 'affects' field, maybe?">Affects</a></th>
      <th><a href="BugStatuses">Status</a></th>
      <th><a href="link explaining 'Importance' field">Importance</a></th>
      <th><a href="link explaining 'assigned to', maybe?">Assigned to</a></th>
    </tr>
    <tr>
      <td><a href="link to edit package, maybe?">Lunchbox Bugs</a></td>
      <td><a href="link to edit status">Confirmed</a></td>
      <td><a href="link to edit importance">Medium</a></td>
      <td><a href="link to edit assignee?">Joey Stanford</a></td>
    </tr>
    <!-- .... -->
  </table>

I'm not too sure about this, but IMNSHO the "expander" arrows are too small by themselves to be comfortable to click (this properly belongs to the discussion in bug 137448 I guess). On the other hand, some people might expect the links in the headers to be used for sorting on a field, although for most bug reports, that doesn't really make much sense (I guess you would need to be able to sort only when you have more than about three affected packages).