It would be nice to be able to limit searches by time so
queries 
like:

  show all tickets that were created in the last 24 
hours

  show all tickets opened this week

  show all of 
the issues I worked on over the last week

This idea is 
actually stolen from a request and
implementation on the rt 
mailing list.

-- rouilj

Logged In: YES 
user_id=764

I'd like to second this request: I'm using a schema
involving types
such as 'Bug' and 'Milestone' (on issues.fresco.org), and
I'd like
to be able to generate a list of bugs that have been closed 
between two milestone releases.
That seems to be included in this request as a special case.

Logged In: YES 
user_id=218539

Well, this feature is in CVS since yesterday:)

Your queries could be performed as:

1. Created: from -1d

2. If "opened" - is it a synonim for "created" then Created:
from -1w (or just -1w)

3. Activity: -1w and AssignedTo: assigned to me

It is a bit harder to perform a Stefan's query with classic
tracker, but possible:

notice that activity on issue usually stops when issue is
closed, so you can search like this:

Activity: from {milestoneAdate} to {milestoneBdate} and
Status=resolved

You should substitute {milestoneAdate} and {milestoneBdate}
with actual dates.

However some activity is actually possible after closing
issue (e.g. change of priority). To be more precise, you can
add one more property to Issue schema - close_date=Date() -
and write a reactor, that changes it to 'now' when issue's
status becomes 'resolved' and to '' when issue status
becomes other than 'resolved'. As I did for my tracker.

Logged In: YES 
user_id=6405

This is implemented.