When I want to point people to the current list of
isses that need testing I want have a short url for email.

Right now the url to get a list of all bugs that need
testing

http://.../issues/issue?:columns=id,activity,title,assignedto,topic,status&:sort=-activity&:group=target&:filter=status&status=6

That's much too long to stick in an email. I wish that
I could name my queries so a like like this:

http://.../issues/queries/to-be-tested

Would generate the same page.

Logged In: YES 
user_id=6405

Neat idea :) 

Logged In: YES 
user_id=335935

Another thing that is close to this issue:

Allow the user to set the title on the query.  So the title
tag would show what query was run.  

I have tons of tabs open, it would be nice to see "To Be
Tested" at the first of the tab title, so I can navigate
thru all the tabs faster.

This isn't a good solution to the problem described here, but I thought I'd mention it anyway for posterity. If you give a query a name and save it, the roundup core assigns it a database ID. You can then go to http://tracker/queryN to go to that query. You'll still need to click submit on the form to see the results but all the fields will be filled in for you. Unfortunately, I don't think there is an easy way to find out what N is for any given query. If you go to http://tracker/query it will you show you ALL queries (and their database IDs) so you can look through that list and find out which one is yours.

If you name a query (and make it public), you can go to your sidebar
edit link for queries
(http://issues.roundup-tracker.org/query?@template=edit
foe example). Then hovering over the edit link on that page
gives you the query number. Note you need to make the query public
to share. Also I am not sure if public includes the anonymous user.

This may also handle the issue where the URL is too long for the web server to handle.

When creating the search url, use POST rather than GET for the form.

Then use ../query34?@action=perform_search to trigger the search. A plain query34
without action will load the search for editing. To do this will need to add the
perform_search action and make the search public is you want to share it.

Probably need javascript to change the GET for POST as well.

Also consider:

  ../query?@action=perform_search&@queryname=my+query+name

as an option to search by search name. It can search across all public queries for a matching
name. However queryname is not unique. So would need to handle that case somehow.