[Rt-commit] rt branch, 4.0/new-status-pod, repushed

[Todd Wade]

The branch 4.0/new-status-pod was deleted and repushed:
       was 75b3fe10f01acb3a1f12dc06d1299ab520af6e76
       now 6d885610e96775ca60d7e9d5b4e017738160bbc1

1:  75b3fe1 ! 1:  6d88561 instructions for how to add new global status
    @@ -1,6 +1,13 @@
     Author: Todd Wade <todd at bestpractical.com>
     
         instructions for how to add new global status
    +    
    +    In pre 4.0 versions, adding new statuses was documented well enough with
    +    
    +    http://bestpractical.com/docs/rt/3.8/RT_Config.html#ActiveStatus-InactiveStatus
    +    
    +    but with lifecycles this is no longer valid and there is no documentation
    +    on how to achieve this.
     
     diff --git a/docs/customizing/lifecycles.pod b/docs/customizing/lifecycles.pod
     --- a/docs/customizing/lifecycles.pod
    @@ -11,25 +18,29 @@
      
     +=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.
    ++Because Statuses are controlled via lifecycles, you must manipulate the entire
    ++lifecycle configuration to add a status. In earlier versions of RT new statuses
    ++could be added by adding a new element to an array in RT's config file. But
    ++because lifecyles are built around statuses, the entire lifecycle configuration
    ++must be modified even if you only need new statuses.
    ++
    ++=head2 Copy Lifecycle Config
    ++
    ++First, copy the C<%Lifecycles> hash from C<RT_Config.pm> and paste it into
    ++C<RT_SiteConfig.pm>.
     +
     +=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:
    ++Add the status to the set where your new status belongs. This example adds
    ++C<approved> 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:
    ++Now the transitions section must be updated so that the new status can
    ++transition to the existing statuses and also so the existing statuses can
    ++transition to the new status.
     +
     +    new      => [qw(    open approved stalled resolved rejected deleted)],
     +    open     => [qw(new      approved stalled resolved rejected deleted)],