I can populate the custom field easily enough through the REST interface
with the CF.{field name} format.
Don’t seem to be able to resolve this back to selections in a multiple
entry CF.
The REST interface itself returns comma delimited list when displaying a
ticket with a multiple item CF selection, so it seems sensible to be
able to pass the same result back to RT and have it yield the original
result. This does not appear to work.
More appropriate may be the ability to pass repetitive key definitions
eg
CF.{field name A}: Select Item 1
CF.{field name A}: Select Item 2
…
Regards
Tarek
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
I don’t really have a setup where I can test this but you’ve mentioned that
the REST interface returns comma delimited list, have you tried entering
the CF value with a comma delimited entry? Something like this:
CF-‘Field A’: ‘item 1’, ‘item 2’, ‘item 3’
When I have some time I’ll see if I can test this in my testing environment.
I can populate the custom field easily enough through the REST interface
with the CF.{field name} format.
Don’t seem to be able to resolve this back to selections in a multiple
entry CF.
The REST interface itself returns comma delimited list when displaying a
ticket with a multiple item CF selection, so it seems sensible to be
able to pass the same result back to RT and have it yield the original
result. This does not appear to work.
More appropriate may be the ability to pass repetitive key definitions
eg
CF.{field name A}: Select Item 1
CF.{field name A}: Select Item 2
…
Regards
Tarek
–
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
I don’t really have a setup where I can test this but you’ve mentioned
that the REST interface returns comma delimited list, have you tried
entering the CF value with a comma delimited entry? Something like this:
CF-‘Field A’: ‘item 1’, ‘item 2’, ‘item 3’
When I have some time I’ll see if I can test this in my testing
environment.
I can populate the custom field easily enough through the REST interface
with the CF.{field name} format.
Don’t seem to be able to resolve this back to selections in a multiple
entry CF.
The REST interface itself returns comma delimited list when displaying a
ticket with a multiple item CF selection, so it seems sensible to be
able to pass the same result back to RT and have it yield the original
result. This does not appear to work.
More appropriate may be the ability to pass repetitive key definitions
eg
CF.{field name A}: Select Item 1
CF.{field name A}: Select Item 2
…
Regards
Tarek
–
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
have tried multiple variations on this theme to no avail.
I suspect a delve into the code base will be required.
My best guess is this feature is not yet supported.
One would be fine with this, except for the fact that if one edits the
ticket at a later stage it by default deletes the custom entry field of
content which is not ok.
Regards
Tarek
sorry, noticed the syntax doesn’t make sense O_o
Should be more like this:
set CF-‘Field A’=‘item 1’,‘item 2’,‘item 3’
– Bart
Hi,
I don’t really have a setup where I can test this but you’ve mentioned
that the REST interface returns comma delimited list, have you tried
entering the CF value with a comma delimited entry? Something like this:
CF-‘Field A’: ‘item 1’, ‘item 2’, ‘item 3’
When I have some time I’ll see if I can test this in my testing
environment.
– Bart
Greetings,
Is this possible?
I can populate the custom field easily enough through the REST
interface
with the CF.{field name} format.
Don’t seem to be able to resolve this back to selections in a multiple
entry CF.
The REST interface itself returns comma delimited list when displaying
a
ticket with a multiple item CF selection, so it seems sensible to be
able to pass the same result back to RT and have it yield the original
result. This does not appear to work.
More appropriate may be the ability to pass repetitive key definitions
eg
CF.{field name A}: Select Item 1
CF.{field name A}: Select Item 2
…
Regards
Tarek
–
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
have tried multiple variations on this theme to no avail.
I suspect a delve into the code base will be required.
My best guess is this feature is not yet supported.
One would be fine with this, except for the fact that if one edits the
ticket at a later stage it by default deletes the custom entry field of
content which is not ok.
As far as I know, the test suite has had tests for multiple value CFs
for a while. If you believe you’ve found a bug, a patch extending
t/web/command_line.t would be really helpful.