[Rt-commit] rt branch, 4.2/charts-docs, updated. rt-4.1.13-32-g5abffdd
Thomas Sibley
trs at bestpractical.com
Tue Jun 25 19:00:39 EDT 2013
The branch, 4.2/charts-docs has been updated
via 5abffddd461b0077dec8c59de96d81e8a7be1d65 (commit)
via ff96555fd2ce03522c0f7fe3839a9a4d7cff25e8 (commit)
via 02595cb0779ef57aa83e6687c7c76e8a74d6abbf (commit)
via 010b27cc65b54ac9a869a0807ec1440725ad1ff4 (commit)
via 53ab71a81aace0d35c993485e58c60221ccff2cf (commit)
from de79a0f862d0bb044e7b27bde7a69fecd95cc783 (commit)
Summary of changes:
docs/charts.pod | 31 +++++++++++++++++--------------
1 file changed, 17 insertions(+), 14 deletions(-)
- Log -----------------------------------------------------------------
commit 53ab71a81aace0d35c993485e58c60221ccff2cf
Author: Thomas Sibley <trs at bestpractical.com>
Date: Tue Jun 25 15:55:47 2013 -0700
configure must be re-run with all previous options as well
Otherwise defaults such as database type and database user may be
rewritten.
diff --git a/docs/charts.pod b/docs/charts.pod
index fe06d4b..086b851 100644
--- a/docs/charts.pod
+++ b/docs/charts.pod
@@ -17,8 +17,9 @@ came in RT 4.2. If you're running a version of RT earlier than
While charts is a core part of RT, you do need to enable it using
the C<--enable-gd> option and install the required dependencies when
you install RT. If you didn't originally install with this flag, you can
-enable it by rerunning the L<< C<configure> >> script from the RT
-distribution or doing the following in your current install:
+enable it by re-running the L<< C<configure> >> script from the RT
+distribution (including all previous options passed to it originally)
+or doing the following in your current install:
=over
commit 010b27cc65b54ac9a869a0807ec1440725ad1ff4
Author: Thomas Sibley <trs at bestpractical.com>
Date: Tue Jun 25 15:56:53 2013 -0700
rt-test-dependencies doesn't look at $DisableGD, it needs --with-gd
diff --git a/docs/charts.pod b/docs/charts.pod
index 086b851..4118e88 100644
--- a/docs/charts.pod
+++ b/docs/charts.pod
@@ -33,7 +33,7 @@ In your C<RT_SiteConfig.pm> set C<$DisableGD> to 0:
Run the RT dependency checker:
- $ /opt/rt4/sbin/rt-test-dependencies -v
+ $ /opt/rt4/sbin/rt-test-dependencies --with-gd --verbose
=item 3
@@ -47,7 +47,7 @@ or something similar.
Install Perl GD modules:
- $ /opt/rt4/sbin/rt-test-dependencies --install -v
+ $ /opt/rt4/sbin/rt-test-dependencies --with-gd --install --verbose
=back
commit 02595cb0779ef57aa83e6687c7c76e8a74d6abbf
Author: Thomas Sibley <trs at bestpractical.com>
Date: Tue Jun 25 15:57:45 2013 -0700
Clarify that out of the box RT will handle Unicode in charts
Link to the %ChartFont option while I'm at it.
diff --git a/docs/charts.pod b/docs/charts.pod
index 4118e88..7824489 100644
--- a/docs/charts.pod
+++ b/docs/charts.pod
@@ -54,14 +54,16 @@ Install Perl GD modules:
=head2 Chart Configuration Options
-By default, GD doesn't have full Unicode support, but RT has a configuration
-option, C<%ChartFont>, to enable additional fonts.
+By default, RT is configured to use the "Droid Sans" font for Unicode support
+across English, many western european languages, Chinese (Traditional and
+Simplified), and Japanese. If you prefer to use a different font, you can
+change the L<< "C<%ChartFont>"|RT_Config/ChartFont >> option.
There is also an option to use database timezone conversion for PostgreSQL
and MySQL to enable timezone conversion for time-based reports. See
F<docs/customizing/timezones_in_charts.pod> for details.
-Search for 'Chart' entries in L<< C<RT_Config> >> for more information on these
+Search for "Chart" entries in L<< C<RT_Config> >> for more information on these
options.
=head1 Basic Charting
commit ff96555fd2ce03522c0f7fe3839a9a4d7cff25e8
Author: Thomas Sibley <trs at bestpractical.com>
Date: Tue Jun 25 15:58:32 2013 -0700
Minor word choice tweaks for clarity
diff --git a/docs/charts.pod b/docs/charts.pod
index 7824489..e2468f1 100644
--- a/docs/charts.pod
+++ b/docs/charts.pod
@@ -68,9 +68,9 @@ options.
=head1 Basic Charting
-Charts are based on the set of tickets defined by a search, so every chart starts
-with a search on your RT tickets. When constructing your search, think about
-the report you need to generate and try to narrow the result set to the set
+Charts are based on the set of tickets returned by a search, so every chart starts
+with a search of your RT tickets. When constructing your search, think about
+the report you need to generate and try to narrow the results to the set
of tickets that will have the information you want.
=head2 Basic Ticket Search
commit 5abffddd461b0077dec8c59de96d81e8a7be1d65
Author: Thomas Sibley <trs at bestpractical.com>
Date: Tue Jun 25 15:59:15 2013 -0700
Using July 1 and 31 is more clear, at least to me
Noting TIMTOWTDI is ancillary to showing people how to use charts.
diff --git a/docs/charts.pod b/docs/charts.pod
index e2468f1..bd93d3e 100644
--- a/docs/charts.pod
+++ b/docs/charts.pod
@@ -80,17 +80,17 @@ the General queue. First use the Query Builder to build a query with
something like:
Queue = 'General'
- AND Created > '2012-06-30'
- AND Created < '2012-08-01'
+ AND Created >= '2012-07-01'
+ AND Created <= '2012-07-31'
This search will give you tickets for July because the criteria uses before
-and after for the dates. You could also use C<< >= >> and C<< <= >> if you wanted
-to use the first and last days of the month.
+and after for the dates.
This search shows one of the initial things you'll want to consider, which is
the element of ticket metadata you want to use as the basis for time. In
the example we're using Created, but depending on what you are reporting
on you might want Started, Resolved, or any of the other ticket time values.
+
When selecting the criteria for the time search, make sure it
is appropriate to the report you want to see and be consistent so you
are looking at the right set of tickets in the search and the resulting
-----------------------------------------------------------------------
More information about the Rt-commit
mailing list