Admin: 1 revision imported

2016-04-06T20:52:58Z

1 revision imported

← Older revision		Revision as of 16:52, 6 April 2016
(No difference)

82.198.197.57: Created page with "First, the custom field must be created inside RT, the REST API does not create new custom fields. It only fills existing ones. Second, the prefix CF- seems to be wrong. Try ..."

2014-05-19T10:04:01Z

Created page with "First, the custom field must be created inside RT, the REST API does not create new custom fields. It only fills existing ones. Second, the prefix CF- seems to be wrong. Try ..."

New page

First, the custom field must be created inside RT, the REST API does not create new custom fields. It only fills existing ones.

Second, the prefix CF- seems to be wrong. Try using CF.{FieldName}, that works for me (I'm using Java). So in PHP this should be:

$content = array( "CF.{admin-keywords}" => "Keyword name" );

If you request info about a ticket, the custom fields are written like this instead of the documented CF- prefix.

Talk:REST/@comment-84.88.66.194-20140407152544/@comment-82.198.197.57-20140519100400 - Revision history

Admin: 1 revision imported

82.198.197.57: Created page with "First, the custom field must be created inside RT, the REST API does not create new custom fields. It only fills existing ones. Second, the prefix CF- seems to be wrong. Try ..."