Hello List,
As we have number of queues, how can we configure it as tree rather then
dropdown list?
Thanks
Darshak
-
OTRS mailing list: otrs - Webpage: http://otrs.org/
Archive: http://lists.otrs.org/pipermail/otrs
To unsubsc
Hi all,
I've setup an OTRS (version 3.1.21) on a 3GB / 2 CPU virtual machine.
I have made a CGI to return a ticket list into JSON.
For this, I use the method TicketSearch. There, I have a hge hash to output
as JSON.
use JSON;
print "application/json";
print JSON->new->e
Maybe you're using queues incorrectly if you have so many of them. Queues
should be an agent or groups of agents who can handle a specific type of
request. At most, you should have as many queues as you have agents, but in
practical terms, your customers shouldn't have that much choice.
When you c
ddt... or more explanation of why you need to get all your tickets via JSON
might be helpful.
On Wed, Jul 16, 2014 at 6:38 AM, Marwan Rabbâa wrote:
> Hi all,
>
> I've setup an OTRS (version 3.1.21) on a 3GB / 2 CPU virtual machine.
>
> I have made a CGI to return a ticket list into JSON.
>
> Fo
Hi,
In fact, I have made this CGI cause I need to parse / search (via a cron)
on tickets made since
Regards,
2014-07-16 13:48 GMT+02:00 Gerald Young :
> ddt... or more explanation of why you need to get all your tickets via
> JSON might be helpful.
>
>
> On Wed, Jul 16, 2014 at 6:38 AM, M
How can one reproduce your experience?
On Wed, Jul 16, 2014 at 8:03 AM, Marwan Rabbâa wrote:
> Hi,
>
> In fact, I have made this CGI cause I need to parse / search (via a cron)
> on tickets made since
>
> Regards,
>
>
> 2014-07-16 13:48 GMT+02:00 Gerald Young :
>
> ddt... or more explanati
@crythias: Thanks to help me solving this pb ^^
What I want to do is encode a large number of tickets obtained throught the
search lib.
I made the search with personalized params :
$TicketObject->TicketSearch(
'StateType' => ['open', 'new', 'closed'],
'Result'
Hi Crythias,
Your inputs are always valuable.
We have different org/depts and hence the queue numbers are
higher. Tree view to customers will give better feel.
Is there a way in OTRS or how can this be implemented ?
+ a TicketGet for each ticket, of course
I can do a SOAP call for ticket search, but my original problem was to
avoid HTTP request (TicketGet SOAP) foreach tickets found
2014-07-16 14:21 GMT+02:00 Marwan Rabbâa :
> @crythias: Thanks to help me solving this pb ^^
>
> What I want to do is encode
I wasn't attached to SOAPpy for any reason other than that was the example I
found for connecting to OTRS from Python before the GenericInterface came
along.
Would you be able to post a short snippet of how you are connecting to GI from
suds-jurko?
I am receiving this error:
suds.transport.
Just migrate to the latest version, there you will have a tree view icon next
to the drop down.
--
Nils Leideck
> On 16.07.2014, at 14:34, "Darshak Modi(darshak.modi)"
> wrote:
>
> Tree view to customers will give better feel.
>
> Is there a way in OTRS or how can this be implemented ?
Am 16.07.2014 17:49, schrieb Kristofer Pettijohn:
Did you have to hand craft a wsdl?
No, luckily someone did this already for me ;-)
https://code.google.com/p/otrs-git/source/browse/development/webservices/GenericTicketConnector.wsdl
I changed the hostname in the WSDL file and saved it as con
That worked perfect! Thank you!
I agree that OTRS should deliver the WSDL; maybe some day.
Thanks again for your help, I am happy to have this working now.
- Original Message -
From: "Christoph Zwerschke"
To: "User questions and discussions about OTRS."
Sent: Wednesday, July 16,
13 matches
Mail list logo
