[Rt-commit] rt branch, 4.4/category-level-cf-groupings, repushed

[? sunnavy]

The branch 4.4/category-level-cf-groupings was deleted and repushed:
       was d0d1e7fe96dae3f6fb7c0722b8daf210702b88c1
       now 26ee26d1b6179f7940376c6e77aed39679a92f6e

1: cddf1191c = 1: cddf1191c Reduce code duplication of checking formats of CustomFieldGroupings
2: a57fcc270 = 2: a57fcc270 Update cf groupings tests for code duplication cleanup
3: 09d42d613 ! 3: 094cb5172 Support different custom field groupings at category level
    @@ -221,6 +221,21 @@
     --- a/lib/RT/CustomFields.pm
     +++ b/lib/RT/CustomFields.pm
     @@
    + (usually via the empty string), limits to custom fields which appear in no
    + grouping.
    + 
    ++When there are 3 arguments supplied, they are supposed to be:
    ++
    ++    1. Object or Class name
    ++    2. Queue/Catalog name
    ++    3. Grouping name
    ++
    ++See also L<RT::CustomField/Groupings>
    ++
    + I<Caveat:> While the record object or class name is used to find the
    + available groupings, no automatic limit is placed on the lookup type of
    + the custom fields.  It's highly suggested you limit the collection by
    +@@
      
      sub LimitToGrouping {
          my $self = shift;
4: 3ef3684c1 = 4: 546c2c0b5 Update tests for the new canonicalized format of CustomFieldGroupings
5: d0d1e7fe9 = 5: 26ee26d1b Add tests for queue level cf groupings