I’ve been playing around with the new search functionality in 3.2,
and it seems rather nice.
In 3.0 I’d changed Search/Elements/TicketRow to display different fields
by default in search results (e.g. to show the Client name rather than
the Requestor email address, where appropriate).
In 3.2 this component no longer exists, in favour of a much more complex
set of callbacks that can display everything depending on the search
criteria.
This is very nice for custom queries, but I can’t spot a way yet to just
change the default columns (e.g. from the Quick Search) to DWIW.
Suggestions?
Tony
I’ve been playing around with the new search functionality in 3.2,
and it seems rather nice.
In 3.0 I’d changed Search/Elements/TicketRow to display different
fields
by default in search results (e.g. to show the Client name rather than
the Requestor email address, where appropriate).
In 3.2 this component no longer exists, in favour of a much more
complex
set of callbacks that can display everything depending on the search
criteria.
This is very nice for custom queries, but I can’t spot a way yet to
just
change the default columns (e.g. from the Quick Search) to DWIW.
Answered on the list in the past 3-4 days. You’ll want to look at the
config file.
change the default columns (e.g. from the Quick Search) to DWIW.
Answered on the list in the past 3-4 days. You’ll want to look at the
config file.
I’ve checked again, and I still can’t find this. There was a post by Bob
Goldstein that didn’t seem to get an answer, but that’s all I can see.
I’ve had a look in the Config, and found the part where it sets up the
DefaultSearchResultFormat, but I can’t tell from that how to include a
custom field (it’s a global ones, so there should be no per-queue
problems).
I’m also curious as to why a lot of these things are in a config file,
rather than accessible via the web interface. Is this is a policy
decision, or just something that no-one has gotten around to doing yet?
Tony
change the default columns (e.g. from the Quick Search) to DWIW.
Answered on the list in the past 3-4 days. You’ll want to look at the
config file.
I’ve checked again, and I still can’t find this. There was a post by
Bob
Goldstein that didn’t seem to get an answer, but that’s all I can see.
I’ve had a look in the Config, and found the part where it sets up the
DefaultSearchResultFormat, but I can’t tell from that how to include a
custom field (it’s a global ones, so there should be no per-queue
problems).
Use the UI to add the custom field to the default format in the query
builder and click the advanced tab. It’ll show you the format.
I’m also curious as to why a lot of these things are in a config file,
rather than accessible via the web interface. Is this is a policy
decision, or just something that no-one has gotten around to doing yet?
The latter. We needed to be able to store these things in the
database somewhere. We now have the Attributes table for this. But no,
nobody’s gotten around to writing a nice web-based editor for the
preferences, along with a nice simple CLI for doing the editing when
you haven’t gotten the web UI up and running yet.
I’ve had a look in the Config, and found the part where it sets up the
DefaultSearchResultFormat, but I can’t tell from that how to include a
custom field (it’s a global ones, so there should be no per-queue
problems).
Use the UI to add the custom field to the default format in the query
builder and click the advanced tab. It’ll show you the format.
Aha. Nice idea. That worked. Thanks.
I’m assuming there’s no way to add conditionals in here?
We used to have it show the Client if that was assigned yet, otherwise
the requestor emails. I can live without this, just checking in case
there’s deeper magic here 
Tony
Use the UI to add the custom field to the default format in the query
builder and click the advanced tab. It’ll show you the format.
Does this apply to OrderBy and Order and Rows?
The format for the individual columns made sense.
I’m also curious as to why a lot of these things are in a config file,
rather than accessible via the web interface. Is this is a policy
decision, or just something that no-one has gotten around to doing yet?
The latter. We needed to be able to store these things in the
database somewhere. We now have the Attributes table for this. But no,
nobody’s gotten around to writing a nice web-based editor for the
preferences, along with a nice simple CLI for doing the editing when
you haven’t gotten the web UI up and running yet.
If you store a default format per user, that would be very cool!
bobg