Permalink
Browse files

Update README from lib/ and update lib to be even more explicit

  • Loading branch information...
1 parent 7b74467 commit 443858aec4e5732f45dc17d03a677f1641dab71f @jibsheet jibsheet committed Aug 29, 2012
Showing with 15 additions and 9 deletions.
  1. +10 −6 README
  2. +5 −3 lib/RT/Extension/PriorityAsString.pm
View
16 README
@@ -10,17 +10,21 @@ SYNOPSIS
# numeric representation
Set(%PriorityAsString, (Low => 0, Medium => 50, High => 100));
- # which order to display the priority strings
- # if you don't specify this, the strings in the PriorityAsString
- # hash will be sorted and displayed
- Set(@PriorityAsStringOrder, qw(Low Medium High));
+ # Fine-tuned control of the order of priorities as displayed in the
+ # drop-down box; usually this computed automatically and need not be
+ # set explicitly. It can be used to limit the set of options
+ # presented during update, but allow a richer set of levels when
+ # they are adjusted automatically.
+ # Set(@PriorityAsStringOrder, qw(Low Medium High));
# Uncomment if you want to apply different configurations to
# different queues. Each key is the name of a different queue;
# queues which do not appear in this configuration will use RT's
# default numeric scale.
- # This option means that %PriorityAsString is ignored (no global
- # override, you must specify a set of priorities per queue).
+ # This option means that %PriorityAsString and
+ # @PriorityAsStringOrder are ignored (no global override, you must
+ # specify a set of priorities per queue). You can safely leave them
+ # out of your RT_SiteConfig.pm to avoid confusion.
# Set(%PriorityAsStringQueues,
# General => { Low => 0, Medium => 50, High => 100 },
# Binary => { Low => 0, High => 10 },
@@ -24,14 +24,16 @@ RT::Extension::PriorityAsString - show priorities in RT as strings instead of nu
# set explicitly. It can be used to limit the set of options
# presented during update, but allow a richer set of levels when
# they are adjusted automatically.
- Set(@PriorityAsStringOrder, qw(Low Medium High));
+ # Set(@PriorityAsStringOrder, qw(Low Medium High));
# Uncomment if you want to apply different configurations to
# different queues. Each key is the name of a different queue;
# queues which do not appear in this configuration will use RT's
# default numeric scale.
- # This option means that %PriorityAsString is ignored (no global
- # override, you must specify a set of priorities per queue).
+ # This option means that %PriorityAsString and
+ # @PriorityAsStringOrder are ignored (no global override, you must
+ # specify a set of priorities per queue). You can safely leave them
+ # out of your RT_SiteConfig.pm to avoid confusion.
# Set(%PriorityAsStringQueues,
# General => { Low => 0, Medium => 50, High => 100 },
# Binary => { Low => 0, High => 10 },

0 comments on commit 443858a

Please sign in to comment.