How to name a custom field?

Hi,

I’m using REST API to create a ticket. And see that I can pass
CF_: to create custom field for that new
ticket. However, when I pass “CF_EmailAddress: tester@company.com” as the
part of post data, my company’s RT tell me EmailAddress is not valid. I
searched from Internet and no document has more detail about this. Please
give me guide. Thanks!

Chenxiong Qi

I’m using REST API to create a ticket. And see that I can pass CF_:
to create custom field for that new ticket. However, when I pass

Actually, you want CF.{EmailAddress} or the old old style of
CF-EmailAddress. I’m not aware of CF_EmailAddress being valid in any
part of RT. If you found this documented on the wiki, I’d appreciate
it if you fixed the documentation there.

-kevin

I’m using REST API to create a ticket. And see that I can pass
CF_:
to create custom field for that new ticket. However,
when I pass

Actually, you want CF.{EmailAddress} or the old old style of
CF-EmailAddress. I’m not aware of CF_EmailAddress being valid in any
part of RT. If you found this documented on the wiki, I’d appreciate
it if you fixed the documentation there.

CF.{EmailAddress}: qcxhome@gmail.com
Above line is included in the post data, and RT still tells me EmailAddress
is an invalid custom field name.

-kevin

“CF_EmailAddress: [1]tester@company.com” as the part of post data,
my company’s RT tell me
EmailAddress is not valid. I searched from Internet and no document
has more detail about
this. Please give me guide. Thanks!


We’re hiring! http://bestpractical.com/jobs

A Python developer living in Beijing

Hi

Do you actually have a Custom Field called EmailAddress
(listed in http://your.server.domain/Admin/CustomFields/index.html)
or are you trying to set the email address of the requestor/owner/Cc ?

GerardOn 2012-11-29 06:42, tkdchen wrote:

On Thu, Nov 29, 2012 at 1:18 AM, Kevin Falcone <falcone@bestpractical.com mailto:falcone@bestpractical.com> wrote:

On Wed, Nov 28, 2012 at 09:49:54PM +0800, tkdchen wrote:
>    I'm using REST API to create a ticket. And see that I can
pass CF_<CustomFieldField>:
>    <FieldValue> to create custom field for that new ticket.
However, when I pass

Actually, you want CF.{EmailAddress} or the old old style of
CF-EmailAddress.  I'm not aware of CF_EmailAddress being valid in any
part of RT.  If you found this documented on the wiki, I'd appreciate
it if you fixed the documentation there.

CF.{EmailAddress}: qcxhome@gmail.com mailto:qcxhome@gmail.com
Above line is included in the post data, and RT still tells me
EmailAddress is an invalid custom field name.

-kevin

>    "CF_EmailAddress: [1]tester@company.com
<mailto:tester@company.com>" as the part of post data, my
company's RT tell me
>    EmailAddress is not valid. I searched from Internet and no
document has more detail about
>    this. Please give me guide. Thanks!

Hi gfeelon,

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.

Chenxiong Qi

Hi

Do you actually have a Custom Field called EmailAddress
(listed in http://your.server.domain/Admin/CustomFields/index.html)
or are you trying to set the email address of the requestor/owner/Cc ?

Gerard

I’m using REST API to create a ticket. And see that I can pass
CF_:
to create custom field for that new ticket. However, when I
pass

Actually, you want CF.{EmailAddress} or the old old style of
CF-EmailAddress. I’m not aware of CF_EmailAddress being valid in any
part of RT. If you found this documented on the wiki, I’d appreciate
it if you fixed the documentation there.

CF.{EmailAddress}: qcxhome@gmail.com
Above line is included in the post data, and RT still tells me EmailAddress is
an invalid custom field name.

-kevin

“CF_EmailAddress: [1]tester@company.com” as the part of post data, my
company’s RT tell me

EmailAddress is not valid. I searched from Internet and no document has
more detail about

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

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 QiOn Fri, Nov 30, 2012 at 11:30 AM, Kevin Falcone falcone@bestpractical.comwrote:

On Fri, Nov 30, 2012 at 10:09:06AM +0800, qcxhome@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

A Python developer living in Beijing

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.

GerardOn 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 <falcone@bestpractical.com mailto:falcone@bestpractical.com> wrote:

On Fri, Nov 30, 2012 at 10:09:06AM +0800, qcxhome@gmail.com <mailto:qcxhome@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

This is clear. Thanks very much! :)On Fri, Nov 30, 2012 at 9:00 PM, Gerard FENELON (EVE) <gfenelon@eve-team.com wrote:

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 <falcone@bestpractical.com wrote:

On Fri, Nov 30, 2012 at 10:09:06AM +0800, qcxhome@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

A Python developer living in Beijing

This is clear. Thanks very much! :)On Fri, Nov 30, 2012 at 9:00 PM, Gerard FENELON (EVE) <gfenelon@eve-team.com wrote:

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 <falcone@bestpractical.com wrote:

On Fri, Nov 30, 2012 at 10:09:06AM +0800, qcxhome@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

A Python developer living in Beijing

I’m using REST API to create a ticket. And see that I can pass CF_:
to create custom field for that new ticket. However, when I pass

Actually, you want CF.{EmailAddress} or the old old style of

The name enclosed by {} can contain space character, such as
CF.{CustomeField Name}?
Thanks!

CF-EmailAddress. I’m not aware of CF_EmailAddress being valid in any
part of RT. If you found this documented on the wiki, I’d appreciate
it if you fixed the documentation there.

-kevin

“CF_EmailAddress: [1]tester@company.com” as the part of post data, my company’s RT tell me
EmailAddress is not valid. I searched from Internet and no document has more detail about
this. Please give me guide. Thanks!


We’re hiring! http://bestpractical.com/jobs

A Python developer living in Beijing