Non-columnized data is difficult to visually parse.

[James Ferguson]

Regarding the dynamic bugs listing beta.

Throwing all the data into an unstructured span soup (milestones, age, tags) is very hard to visually process. e.g. looking at a bug listing to see which bugs are unassigned... Straightforward tabular layouts have a lot to be said for them in this respect.

I appreciate that the worry is that there is too much data to fit in the width, but the current layout needs more structure. There are many possibilities, so it's hard to speculate here exactly which would be best, but I have a number of observations:

1. It's *not* very important to avoid a line break in the description
2. Making the side-portlets (rightmost, tags etc.) div collapsable would make a lot of width available
3. No data items spans position should be free-floating. Depending on screen size right now, some bugs may have items in completely different positions from others in one listing (e.g. see the Tags in the attached screenshot)
4. Color-highlighting of similar data items to help pull them out when scanning.

I appreciate this is a very difficult issue to find a good compromise solution for, but the current state of the beta is very much more difficult to visually process than the old model or any tabular model. I have previously used greasemonkey scripts to add columns to the old model and found it very usable even on a small screen. See tags items in attached screenshot.