It is the other way round :
1- you define CustomFields
2- then you apply them to Queues
3- only then, you may create tickets with values in those CustomFields.
Gerard
On 2012-11-30 05:16, tkdchen wrote:
Hi,
EmailAddress is just for testing the creation of custom field, not for
other purpose. As what you mentioned, if I create a new ticket with
custom fields, that custom fields should be defined in the
/Admin/CustomFields/index.html first. Am I right? Thanks!
Chenxiong Qi
On Fri, Nov 30, 2012 at 11:30 AM, Kevin Falcone
<falc...@bestpractical.com <mailto:falc...@bestpractical.com>> wrote:
On Fri, Nov 30, 2012 at 10:09:06AM +0800, qcxh...@gmail.com
<mailto:qcxh...@gmail.com> wrote:
> Thanks for your guide. I just checked our RT system , the URI
/Admin/CustomFields/index.html
> lists all predefined custom fields. Is it possible to set
some application-specific custom
> fields that are not predefined in /Admin/CustomFields/index.html.
There are no predefined custom fields in RT.
Anything you see on that page is by definition an application-specific
custom field.
You make more by clicking on Create.
As Gerald asked, it's still relevant to know why you have a custom
field named Email Address. Normally Email Addresses would be stored
on a Requestor or Cc or some other User.
-kevin
--------
We're hiring! http://bestpractical.com/jobs
