Hello all. I’ve upgraded from RT 3.4.5 to 3.6.0 (clean install directory but the same database; custom patches applied) and I’m having some issues with the cascading select custom fields.
Assume a category “foo” has values “bar” and “baz” in it.
Ticket creation:
If I specify category foo and then select either bar or baz, RT gets confused and displays “foo” as the value of the field in Display.html. This does not happen in a different custom field in a different queue. Are things being processed out of order somewhere? I think CreateTicket in Interface/Web.pm might be getting confused by the -Category field; it doesn’t check for the string Value in the name of the field.
Ticket updating (cosmetic):
RT always throws the error:
User asked for an unknown update type for custom field Testfield for RT::Ticket object
when I submit Ticket/Modify.html for a ticket with a cascading selector. It’s coming from ProcessObjectCustomFieldUpdates in Interface/Web.pm; it looks like it’s just missing an elsif to handle the -Category form field.
I think these should be quick fixes; I’d submit patches but I don’t have any experience with patch creation or test case creation (as per StyleGuide.pod) and I don’t want to waste anybody’s time. Is this the right venue for this sort of thing?
Thanks,
Tim Smith
Office of Compliance
I’ve attached a two-line patch against the 3.6.0 release of lib/RT/Interface/Web.pm that addresses the cascading custom field issues described below.
Tim Smith
Office of Compliance
“Timothy Smith” tsmith@loc.gov 06/19/06 3:08 PM >>>
Hello all. I’ve upgraded from RT 3.4.5 to 3.6.0 (clean install directory but the same database; custom patches applied) and I’m having some issues with the cascading select custom fields.
Assume a category “foo” has values “bar” and “baz” in it.
Ticket creation:
If I specify category foo and then select either bar or baz, RT gets confused and displays “foo” as the value of the field in Display.html. This does not happen in a different custom field in a different queue. Are things being processed out of order somewhere? I think CreateTicket in Interface/Web.pm might be getting confused by the -Category field; it doesn’t check for the string Value in the name of the field.
Ticket updating (cosmetic):
RT always throws the error:
User asked for an unknown update type for custom field Testfield for RT::Ticket object
when I submit Ticket/Modify.html for a ticket with a cascading selector. It’s coming from ProcessObjectCustomFieldUpdates in Interface/Web.pm; it looks like it’s just missing an elsif to handle the -Category form field.
cascades.diff (924 Bytes)
On the conf page to specify values for a selector CF, there’s a “category” field. Assigning values to categories automagically creates a cascading selector.
Tim Smith
Office of Compliance
“Philip Kime” pkime@Shopzilla.com 06/21/06 1:30 PM >>>
How does the cascading thing work? Is this using the Link feature in the
CF configuration page or is there a way of specifying sub-CFs of a CF?
PK
I’ve attached a two-line patch against the 3.6.0 release of lib/RT/Interface/Web.pm that addresses the cascading custom field issues described below.
Tim Smith
Office of Compliance
“Timothy Smith” tsmith@loc.gov 06/19/06 3:08 PM >>>
Hello all. I’ve upgraded from RT 3.4.5 to 3.6.0 (clean install directory but the same database; custom patches applied) and I’m having some issues with the cascading select custom fields.
Assume a category “foo” has values “bar” and “baz” in it.
Ticket creation:
If I specify category foo and then select either bar or baz, RT gets confused and displays “foo” as the value of the field in Display.html. This does not happen in a different custom field in a different queue. Are things being processed out of order somewhere? I think CreateTicket in Interface/Web.pm might be getting confused by the -Category field; it doesn’t check for the string Value in the name of the field.
Ticket updating (cosmetic):
RT always throws the error:
User asked for an unknown update type for custom field Testfield for RT::Ticket object
when I submit Ticket/Modify.html for a ticket with a cascading selector. It’s coming from ProcessObjectCustomFieldUpdates in Interface/Web.pm; it looks like it’s just missing an elsif to handle the -Category form field.
cascades.diff (924 Bytes)