Blocker Tracking App Reskin - Feedback on New Mockups

Christopher A. Williams chriswfedora at cawllc.com
Wed Sep 12 14:30:21 UTC 2012


On Wed, 2012-09-12 at 08:18 -0600, Tim Flink wrote:
> On Wed, 12 Sep 2012 04:33:57 -0400 (EDT)
> Kamil Paral <kparal at redhat.com> wrote:
> 
> > > The two mockups that I'm looking at right now (identical other than
> > > the table column ordering) are:
> > > http://tflink.fedorapeople.org/blockerbugs/reskin-draft3/blockers-3.html
> > > http://tflink.fedorapeople.org/blockerbugs/reskin-draft3/blockers.html
> > 
> > Tim, I love it!
> > 
> > The first way of column ordering seems better to me.
> 
> I've been going back and forth between the two column layouts - one
> follows the idea that the primary key (bug_id) is on the far right and
> the second most important key (status, changed indicator, update info)
> is on the far right to make scanning the table easier for either the
> primary or secondary key.

FWIW, having the status key on the far right seemed a little more
natural to me in terms of scanning. It implies an order of 1) what am I
looking at, 2)what's the high-level detail I need to know about it, and
3) what's the status. The other column order winds up splitting the
description between two status oriented columns.

But I really like the look regardless.

Just my 2 cents worth... Hope it's helpful!

Chris




More information about the test mailing list