[Rt-commit] rt branch, 4.4/get-referenced-queues-more-search-items, updated. rt-4.4.2-135-g1aaa828575

[Jim Brandt]

The branch, 4.4/get-referenced-queues-more-search-items has been updated
       via  1aaa828575fac90c3da8047aef73dcbe30c8d463 (commit)
       via  00f8b12ab762edcecdd3d95eb4b246aec8379d6d (commit)
      from  d4460613f05bcdc9cfab5f45e05100866767b88b (commit)

Summary of changes:
 docs/query_builder.pod | 33 +++++++++++++++++++++++++--------
 1 file changed, 25 insertions(+), 8 deletions(-)

- Log -----------------------------------------------------------------
commit 00f8b12ab762edcecdd3d95eb4b246aec8379d6d
Author: Jim Brandt <jbrandt at bestpractical.com>
Date:   Thu Jun 25 13:41:22 2020 -0400

    Document new queue and lifecycle search options

diff --git a/docs/query_builder.pod b/docs/query_builder.pod
index da08d93be3..43c9833e35 100644
--- a/docs/query_builder.pod
+++ b/docs/query_builder.pod
@@ -147,5 +147,23 @@ And there are the basics of the query builder! To implement these basics to
 build reports, please see the Dashboard & Reports document. For definitions of
 piece of RT metadata, please see the Definitions of Ticket Metadata document.
 
+=head1 Searching Custom Fields
+
+If you use custom fields on your tickets, you might initially load the Query
+Builder and not see them listed. If your custom fields are applied to
+individual queues and not globally, they won't show up as options on a
+new search. However, once you add a queue to your search, as shown above, the
+custom fields applied to the queue or queues in your search will be displayed.
+You can then add custom field values to your search just like other fields.
+
+In addition to exact queue name searches like "Queue = 'RT'", the query builder
+also allows 'LIKE' searches. This can be useful if you have several queues that
+follow some naming pattern, like "IT Support", "Printer Support", and "Email Support".
+To include all of these, you can use "Queue LIKE 'Support'".
+
+Using the Advanced tab, you can also type one other criteria to search for queues
+by their lifecycle. TicketSQL supports "Lifecycle = 'support'" if you type it
+directly into the Advanced search box.
+
 =cut
 

commit 1aaa828575fac90c3da8047aef73dcbe30c8d463
Author: Jim Brandt <jbrandt at bestpractical.com>
Date:   Thu Jun 25 13:47:21 2020 -0400

    Apply a few small changes from updated RT 5 docs

diff --git a/docs/query_builder.pod b/docs/query_builder.pod
index 43c9833e35..79dbf2e8f4 100644
--- a/docs/query_builder.pod
+++ b/docs/query_builder.pod
@@ -8,11 +8,7 @@ to find exactly what you're looking for (and no more) are discussed below.
 The Query Builder is the heart of reporting in RT, which is covered in the
 L<Dashboard and Reports|docs/dashboards_reporting.pod> document.
 
-To follow along with the examples, go to
-L<issues.bestpractical.com|http://issues.bestpractical.com> and try the
-searches yourself.
-
-=head1 Example
+=head1 Basic Ticket Searches
 
 Let's look for tickets in the "RT" queue (RT's bugtracker for itself) that have
 been resolved in the last year. (These examples assume it's currently mid June,
@@ -143,10 +139,6 @@ The same pieces of information are now spread across the display next to one
 another, which can be harder to read. So when you tell RT to display a lot of
 columns, it's usually worth adding a well-placed NEWLINE.
 
-And there are the basics of the query builder! To implement these basics to
-build reports, please see the Dashboard & Reports document. For definitions of
-piece of RT metadata, please see the Definitions of Ticket Metadata document.
-
 =head1 Searching Custom Fields
 
 If you use custom fields on your tickets, you might initially load the Query
@@ -167,3 +159,10 @@ directly into the Advanced search box.
 
 =cut
 
+=head1 Learn More
+
+To use the query builder to to build and save reports, see
+L<Dashboard and Reports|docs/dashboards_reporting.pod>. For definitions of
+RT metadata, see L<Ticket Metadata|docs/ticket_metadata.pod>.
+
+=cut

-----------------------------------------------------------------------