Christopher Lenz wrote:
Am 16.03.2006 um 15:07 schrieb Alec Thomas:
+1, seems like a good idea to me.
I know this is a bit out of scope, but it would also be nice to be able
to match against ticket comment bodies and usernames. I sometimes
add a comment to a ticket and would like to get a report on these later,
to see what became of them.
Nice to have I guess, but not all that important.
I left out searching the description from the query module because
that's more of a full-text search than simpler attribute queries.
The initial drafts of the query UI actually had a separate field for
doing a full-text search over various various:
<http://projects.edgewall.com/trac/attachment/ticket/203/query2.png>
The idea behind that was that if you're searching for some text, you
don't really care whether it's in the description or in the comments.
Now, the reason I dropped that again was that we'd have two different
types of full-text search, one in the query module, and of course one
in the actual search module.
If you start from the query module, looking for a bit of text in the
summary
only is too restrictive (see also
http://projects.edgewall.com/trac/ticket/2647).
You should be able to look at some string regardless of where it's located.
I agree however that this would overlap with the Search functionality.
Using the Search for tickets is currently the only way to retrieve
tickets when
you're looking for a bit of text. But then, you're left with a mostly
unstructured
list of tickets, and you can't refine the search based on other criterions
(the status for example, like requested in
http://projects.edgewall.com/trac/ticket/1329).
So I think it would make sense to be able to *transfer* the results of a
Search
to the query module, for example when only the ticket filter is selected.
Not only would the results be better presented (better status info than
what I did for http://projects.edgewall.com/trac/ticket/2859),
and you'd have the possibility to refine the search and organize the
search results.
In that scenario, the usage of the "description" field can be seen more
as a way
to filter (in or out) tickets from the current list than a way to start
a query from scratch.
-- Christian
_______________________________________________
Trac-dev mailing list
[email protected]
http://lists.edgewall.com/mailman/listinfo/trac-dev
