[rt-users] Display custom fields in a ticket

[Jeffrey Pilant]

Joop wrote:

> In 4.2 BP introduced the concept of CustomFieldGrouping where you can

> add CFs to other metadata blocks like Dates or People thats why

> ShowSummary is different.

> Could it be that the configuration variable todo wiht CF-Grouping has

> been modified (incorrectly)??
>
> Joop

That probably explains it.  Here is the substance of my RT_SiteConfig.pm file:
  Set($rtname, 'XXXXX.COM');
  Set($WebDomain, 'XXXXX');
  Set(@ReferrerWhitelist, qw(AAA.BBB.CCC.DDD:80 XXXXX:80 xxxxx:80));
  Set($WebPath, "/rt");

We don't use the email side at all (the server cannot even send mail), only the web side.

Can you give me the CustomFieldGrouping I need?  We have CF's of the following patterns:
  LookupType  #  Name  Added   Type   Pattern  Status
  Articles    #  CF    XX      ZZZZZ           Enabled
  Articles    #  CF    XX, YY  ZZZZZ           Enabled
  Tickets     #  CF    XX      ZZZZZ  [WWW]    Enabled
  Tickets     #  CF    XX      ZZZZZ           Enabled
  Tickets     #  CF    Global  ZZZZZ  [WWW]    Enabled
  Tickets     #  CF    Global  ZZZZZ           Enabled
With a total of 5 article and 20 ticket CFs.  Two of the latter are test entries.

The RT_Config.pm suggests something of the form:
  Set(%CustomFieldGroupings,
      'RT::Ticket' => [
          'Grouping Name'     => ['CF Name', 'Another CF'],
          'Another Grouping'  => ['Some CF'],
          'Dates'             => ['Shipped date'],
      ],
      'RT::User' => [
          'Phones' => ['Fax number'],
      ],
  );

If I have to add to a predefined group, I would like to add to "Basics".

After adding to RT_SiteConfig.pm, I will bounce the web server to verify.

Thanks for your assistance.

/jeff


________________________________________________________________________
The information contained in this e-mail is for the exclusive use of the 
intended recipient(s) and may be confidential, proprietary, and/or 
legally privileged.  Inadvertent disclosure of this message does not 
constitute a waiver of any privilege.  If you receive this message in 
error, please do not directly or indirectly use, print, copy, forward,
or disclose any part of this message.  Please also delete this e-mail 
and all copies and notify the sender.  Thank you. 

For alternate languages please go to http://bayerdisclaimer.bayerweb.com
________________________________________________________________________
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bestpractical.com/pipermail/rt-users/attachments/20160329/4b801ecd/attachment.htm>