[Rt-commit] [rtir] 05/05: improved documentation about advanced constituencies

[Kevin Falcone]

This is an automated email from the git hooks/post-receive script.

falcone pushed a commit to branch 3.0-trunk
in repository rtir.

commit c5bcfe5b3f1fbfc93f8c398ddc7b13f4b26d9213
Author: Christophe Vandeplas <christophe at vandeplas.com>
Date:   Tue Sep 10 08:20:20 2013 +0200

    improved documentation about advanced constituencies
---
 docs/Constituencies.pod | 12 +++++++++---
 1 file changed, 9 insertions(+), 3 deletions(-)

diff --git a/docs/Constituencies.pod b/docs/Constituencies.pod
index 2830d53..89c5a20 100644
--- a/docs/Constituencies.pod
+++ b/docs/Constituencies.pod
@@ -93,10 +93,16 @@ rename values, and change the sort order.
 However, to get advanced control over constituencies you have to create additional
 objects in the system. The steps below describe how to do this manually. An
 F<add_constituency> script is also provided which helps add new constituency
-values, along with their associated groups and queues. You'll find this in the
-F<etc> directory in your RTIR distribution.
+values, along with their associated groups and queues. These queues are there only 
+for technical reasons and are only visible for administrators of RTIR.
+The script is located in the F<etc> directory in your RTIR distribution.
 
-=head2 Managing Constituency Values
+Then assign users to their corresponding F<DutyTeam> to give them control over
+objects from their constituency. As the permissions are based on the
+F<constituency> field of the ticket there is no need to move tickets
+from one queue to the newly created constituency queue.
+
+=head2 Manually Managing Constituency Values
 
 In some simple configurations, administrators may use the web interface
 to add, delete, or rename values for the 'Constituency' field, however

-- 
To stop receiving notification emails like this one, please contact
the administrator of this repository.