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!
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.
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!
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.commailto: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!
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.
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.
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!
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.
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!
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!
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.
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!
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.
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!