[Rt-commit] rt branch, 4.0/new-status-pod, created. rt-4.0.19-62-g75b3fe1

[Todd Wade]

The branch, 4.0/new-status-pod has been created
        at  75b3fe10f01acb3a1f12dc06d1299ab520af6e76 (commit)

- Log -----------------------------------------------------------------
commit 75b3fe10f01acb3a1f12dc06d1299ab520af6e76
Author: Todd Wade <todd at bestpractical.com>
Date:   Mon Mar 31 12:44:15 2014 -0400

    instructions for how to add new global status

diff --git a/docs/customizing/lifecycles.pod b/docs/customizing/lifecycles.pod
index 29ab96b..b9d7af8 100644
--- a/docs/customizing/lifecycles.pod
+++ b/docs/customizing/lifecycles.pod
@@ -6,6 +6,38 @@ But there can be any number of workflows where these status values
 don't completely fit. RT allows you to add new custom status values and
 define their behavior with a feature called Lifecycles.
 
+=head1 Adding a New Status
+
+If you want to modify the default lifecycle, you can copy it from
+C<RT_Config.pm>, paste it into C<RT_SiteConfig.pm> and make your
+changes. You can find full lifecycles documentation in L<RT_Config/Lifecycles>.
+This example adds a global 'approved' status.
+
+=head2 Add Status Value
+
+After copying the lifecycle config from C<RT_Config.pm>, add the status to the
+set where your new status belongs. This example adds an 'approved' status
+to the active statuses:
+
+    active => [ 'open', 'approved', 'stalled' ],
+
+=head2 Update Transitions
+
+Now the transitions section must be updated so that the new status will be
+available from the other statuses. Add the new status to each status that can
+transition to the new status, and add the statuses that the new status can
+transition to:
+
+    new      => [qw(    open approved stalled resolved rejected deleted)],
+    open     => [qw(new      approved stalled resolved rejected deleted)],
+    approved => [qw(new open          stalled resolved rejected deleted)],
+    stalled  => [qw(new open approved         rejected resolved deleted)],
+    resolved => [qw(new open approved stalled          rejected deleted)],
+    rejected => [qw(new open approved stalled resolved          deleted)],
+    deleted  => [qw(new open approved stalled rejected resolved        )],
+
+=head1 Order Processing Example
+
 This guide demonstrates lifecycles using an order fulfillment
 system as a real-world example. You can find full lifecycles
 documentation in L<RT_Config/Lifecycles>.
@@ -21,12 +53,6 @@ The detailed configuration options are discussed below. Once you add it
 and restart the server, the new lifecycle will be available on the
 queue configuration page.
 
-If you want to modify the default lifecycle, you can copy it from
-C<RT_Config.pm>, paste it into C<RT_SiteConfig.pm> and make your
-changes.
-
-=head1 Order Processing Example
-
 To show how you might use custom lifecycles, we're going to configure
 an RT lifecycle to process orders of some sort. In our order example,
 each ticket in the queue is considered a separate order and the orders

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