I'm having a problem with the "Group By" functionality
in searches. I had a problem before, grouping on the
"Assigned To" field, but I've been
installing/reinstalling Roundup multiple times to learn
the ropes... and that problem has disappeared.

Now, however, when I group by a field I added,
"projecturl", a Link() field, it groups correctly on
all 3 of my url's except the FIRST one I entered (so
perhaps it's a problem related to the id # of the item?).

Entries for the first url are instead grouped under
"(no projecturl set)", at the bottom of this list (and
not interspersed with the others in order by activity).

In a previous tracker lifetime, the exact same thing
was happening with "Assigned To", but now it's only
happening (and reproducibly) with my custom
"projecturl" field.

I read somewhere about sorting+grouping on the same
field "breaking the index", however I don't think I've
ever done this, and am certainly not doing it with my
test searches now.

Tried:
- modifying the projecturl value then changing it back
- restarting roundup server
- using roundup-admin's "reindex" command (as a guess)
- making new searches from scratch
- small tantrum :-)
- testing on my other roundup server (however, they've
both been built following EXACTLY the same steps, and
both show the same errors).

The issues in my tracker have all been imported out of
a textfile via a script, but the URLs have been added
by-hand as a test-case.  (they link to our docs wiki)

Using Roundup 0.8.3, Windows XP, SQLite 1.1.6, Python 2.4.

Logged In: YES 
user_id=999673

More info: It seems that grouping by anything of type Link()
(to a type String() item) breaks if any items are "unassigned".

Instead of the lowest-ID linked entries getting their own
category, they are being displayed at the bottom of the "(no
___ set)" list.  

Here's a way to reproduce it with a vanilla download:

1) Install a tracker, classic template, sqlite backend
2) Edit config for web/mail settings (I used
http://localhost:444/bug2/,  example.com, and example, for
the 3 must-set variables)
3) Use the load_tracker.py script to load up some garbage
issues (I used 50).  I suppose you could also enter them by
hand.
4) Use roundup-server -p 444 bug2=c:\roundup\trackers\bug2
to start the tracker, then login 
5) Modify some of the issues to set status = "- no selection-"
6) Use the SEARCH feature to make a Search that uses "group
on" = Status.  The bug shows either way, but to make it
most-visible, choose to display a column for Status also. 
Name the search "All by Status" and run it.  

You'll see that whatever items have the lowest-ID value for
status are getting grouped with the "(no status assigned)"
values.  

I can provide a zipfile of an example, if needed.  

Logged In: YES 
user_id=999673

Uploaded file showing the problem.  Tracker is called
"bug2".  Run it on port 444, if you don't wanna change the
configuration.  Login with "admin/admin", then click the
"All by Status" report.  Note the last few entries in the
"(no status set)" group.   

Logged In: YES 
user_id=6405