Skip Menu |

This queue is for tickets about the RT-Client-REST CPAN distribution.

Report information
The Basics
Id: 38592
Status: rejected
Priority: 0/
Queue: RT-Client-REST
People
Owner: Nobody in particular
Requestors: jpierce [...] cpan.org
Cc:
AdminCc:
Bug Information
Severity: Critical
Broken in: 0.37
Fixed in: (no value)

History Show all quoted text
  Tue Aug 19 18:57:38 2008 jpierce [...] cpan.org - Ticket created
Subject: Custom fields ignored
I am passing Ticket->new a reference to a hash of custom fields, but they are not being set for the ticket. my $ticket = RT::Client::REST::Ticket->new( rt=>$rt, queue=>$q{queue}, subject=>$q{_subject}, requestors=>[$q{_email}], cf=>\%cf )->store(text=>$q{comments}); I have verified that %cf is indeed populated, although it is usually ownly sparsely populated (many keys have no values).
  Tue Aug 19 18:59:21 2008 jpierce [...] cpan.org - Correspondence added
Once again, this is for RT 3.8, and there are no errors.
  Tue Aug 19 18:59:23 2008 jpierce [...] cpan.org - Status changed from 'new' to 'open'
  Wed Aug 20 17:25:39 2008 jpierce [...] cpan.org - Correspondence added
The failure to store CFs occurs whether or not the referenced hash is sparse or not. After a gruesome vivisection, I've only been to discover that things seem okay until at least REST->edit. Alas, the module's not very useful if it can't get at custom fields (one might as well email if requestor, subject and body were all that mattered)
  Thu Aug 21 13:04:47 2008 jpierce [...] cpan.org - Correspondence added
Apparently RT non-intuitively requires the ModifyCustomField right to set custom fields, even on creation. So this is in part user error (as well as poor RT documentation) but it would've been easier to figure out if this module exposed RT errors better; I was only able to determine the problem by using the CLI and seeing the error it reported.
  Thu Apr 09 08:46:43 2009 jpierce [...] cpan.org - Status changed from 'open' to 'rejected'