[Rt-commit] rt branch, 5.0/priority-as-string, updated. rt-5.0.0alpha1-18-g0c2c37e9b

Jim Brandt jbrandt at bestpractical.com
Thu Mar 12 17:13:18 EDT 2020


The branch, 5.0/priority-as-string has been updated
       via  0c2c37e9bfc29f619f53f7d73ff7c91d5b54fc07 (commit)
      from  a7657903172a870b31fab0f860adaeb28948d24f (commit)

Summary of changes:
 etc/RT_Config.pm.in | 30 +++++++++++++++++++-----------
 1 file changed, 19 insertions(+), 11 deletions(-)

- Log -----------------------------------------------------------------
commit 0c2c37e9bfc29f619f53f7d73ff7c91d5b54fc07
Author: Jim Brandt <jbrandt at bestpractical.com>
Date:   Thu Mar 12 17:13:14 2020 -0400

    Revise documentation

diff --git a/etc/RT_Config.pm.in b/etc/RT_Config.pm.in
index 90dcef0a5..35f2707e5 100644
--- a/etc/RT_Config.pm.in
+++ b/etc/RT_Config.pm.in
@@ -2709,11 +2709,15 @@ cut down on page clutter. Once this option is clicked the link will change to
 
 Set($HideOneTimeSuggestions, 0);
 
-=item C<%EnablePriorityAsString>
+=item C<$EnablePriorityAsString>
 
-Priorities are stored as numbers internally. This determines if we should
-convert and render them as strings instead. Set this to C<0> to render them
-as internal numbers.
+Priority is stored as a number internally. This determines whether
+Priority is displayed to users as a number or using configured
+labels like Low, Medium, High. See L<%PriorityAsString> for details
+on this configuration.
+
+The default is enabled, so strings are shown. Set to C<0> to display
+numbers, which was the previous default for RT.
 
 =cut
 
@@ -2721,24 +2725,28 @@ Set($EnablePriorityAsString, 1);
 
 =item C<%PriorityAsString>
 
-Specify a mapping between priority strings and the internal numeric
-representation. E.g.
+This setting allows you to define labels for priority values
+available on tickets. RT stores these values internally as a number,
+but this number will be hidden if C<$EnablePriorityAsString> is true.
+For the configuration, link the labels to numbers as shown below. If
+you have more or less priority settings, you can adjust the numbers,
+giving a unique number to each.
 
     Set(%PriorityAsString,
         Default => { Low => 0, Medium => 50, High => 100 },
-        General => [ Medium => 50, Low => 0, High => 100 ],
+        General => [ Medium => 50, Low => 0, High => 80, 'On Fire' => 100],
         Support => 0,
     );
 
-Key is queue name or "Default", which is the fallback for unspecified
-queues. Values could be ArrayRef or HashRef or C<0>.
+The key is queue name or "Default", which is the fallback for unspecified
+queues. Values can be an ArrayRef, HashRef, or C<0>.
 
 =over
 
 =item ArrayRef
 
 This is the ordered String => Number map list. Pririty options will be
-rendered in the same order.
+rendered in the order they are listed in the list.
 
 =item HashRef
 
@@ -2747,7 +2755,7 @@ rendered in numerical ascending order.
 
 =item C<0>
 
-This is to render priorities as numbers.
+Priority is rendered as a number.
 
 =back
 

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


More information about the rt-commit mailing list