I just had a look at 0.5.5 in order to migrate our
0.4.2 installation
and would like to suggest an improvement of the classic
schema:

The navigation at the end of the issue index table does not
tell how many issues there are altogether and which of
these I am currently looking at. It also looks bad if
the table only has one column.

Attached is a patch which puts the navigation into its own
table inside the last line of the outer table and thus
ensures that on the left side there's the (optional)
"<< prev", centered in the middle there's a "xx..yy out
of zzz" 
text and at the right there's the (again optional)
"next >>".

Logged In: YES 
user_id=416927

Forgot the upload checkmark...

Logged In: YES 
user_id=598066

I'm not equipped to evaluate the patch, but +1 on the 
ideas -- the << prev and >> next links can look a little 
bit ropy shoehorned into the same table as the issues.

I implemented something very similar to the "xx..yy out 
of zzz" issues in our templates last week after a user 
requested it, although I did it by tacking an extra plain 
row on after the navigation row and filling it with a 
spanned left-aligned "Issue xx--yy of zzz".

(The user request was actually for a "how many issues 
are in status X?" report, but providing a "how many 
issues matched the query" field seemed to me a more 
generically-useful solution.)