The "sort on" listbox  may contain items that are not present in
the database.  If  i want to e.g. sort on topic, i get an error message
complaining about the non-existing column _topic.

The same problem occurs with the other listbox, "group on".
These listboxes should IMHO only contain the items that
correspond to columns in the database.

Regards,

Albert

Logged In: YES 
user_id=6405

The list of properties to sort/group on is generated using the list of 
properties on the context class (typically "issue"). 
 
Have you modified the schema or template in any way? 
 

Logged In: YES 
user_id=540690

No, I haven't modified the schema or the template.

Logged In: YES 
user_id=6405

This is only a problem with the relational database backends -  
they may not sort or group on a multilink property. There is no 
really easy fix for this - except perhaps for someone to spend 
some time looking into handling sort/group for Multilinks in the 
rdbms backends. 
 
If it's really annoying you, feel free to hard-code the list of 
sort/group properties that are valid for your tracker. 
 

Logged In: YES 
user_id=335935

I would really like to be able to group on a topic/keyword,
even if an issue shows up twice in the results.  

Logged In: YES 
user_id=6405

I've just gotta figure the sql-fu to make it work in sql databases that 
don't have decent joining capabilities. 
 
Meh, maybe I'll just code a python-side implementation and be done 
with it. Better than nothing, I reckon. 

Logged In: YES 
user_id=6405

I implemented it the hard way (though with a little smarts)...