[Rt-commit] rt branch, 4.4/columns-as-values-in-ticket-search, updated. rt-4.4.4-8-gbd628e2bd

[? sunnavy]

The branch, 4.4/columns-as-values-in-ticket-search has been updated
       via  bd628e2bd0b8dbb266ee47c6147c136b1a681d31 (commit)
      from  10c640ef34bf49171934cceab4edee91072c99af (commit)

Summary of changes:
 docs/query_builder.pod | 40 ++++++++++++++++++++++++++++++++++++++++
 1 file changed, 40 insertions(+)

- Log -----------------------------------------------------------------
commit bd628e2bd0b8dbb266ee47c6147c136b1a681d31
Author: sunnavy <sunnavy at bestpractical.com>
Date:   Tue Apr 2 22:20:24 2019 +0800

    Document the feature of "columns as values in ticket search"

diff --git a/docs/query_builder.pod b/docs/query_builder.pod
index 1195ea06e..a7b2d2116 100644
--- a/docs/query_builder.pod
+++ b/docs/query_builder.pod
@@ -158,3 +158,43 @@ piece of RT metadata, please see the Definitions of Ticket Metadata document.
 
 =cut
 
+=head1 Advanced
+
+Besides the query builder, there is a page labelled as "Advanced" where
+you can write query and format directly, e.g. you can simply set the
+following query there:
+
+    Status = 'resolved' AND Resolved > '2014-06-15' AND Queue = 'RT'
+
+and then click "Apply" to let RT parse it.
+
+=head2 Columns as values
+
+In the above example, search values like I<'resolved'>, I<'2014-06-15'>
+and I<'RT'> are all literals, of which you need to know beforehand.
+Sometimes you want to compare 2 columns in RT tables without knowing
+exact values, which is also supported, here are some examples:
+
+=over
+
+=item Search tickets of which LastUpdated is bigger than Due
+
+    LastUpdated > Due
+
+Note that I<Due> is not quoted here indicating that it's a column
+instead of a literal.
+
+=item Search tickets of which requestor is owner
+
+    Requestor.id = Owner
+
+=item Search tickets of which custom fields Foo and Bar have the same value
+
+    CF.Foo IS NOT NULL AND CF.Bar = ObjectCustomFieldValues_1.Content
+
+This looks a bit weird at a glance, but if you are familiar with RT's
+table structure and the SQL RT searches generate, it's actually quite
+straightfoward.  As I<CF.Foo> appears first as a custom field in the
+query, I<ObjectCustomFieldValues_1.Content> represents its Content.
+
+=back

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