-
Notifications
You must be signed in to change notification settings - Fork 27
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ticket_search #6
Comments
@ryanbentley: Could you please provide a little more elaboration about this issue please... |
Nevermind. I've sorted it out - my connector was incorrectly configured. I have another question though: EG: client.ticket_get(ticketid, get_articles=True).articles()[0] How do I get the body of an article? |
Similar to the attributes of a ticket itself, the 'attrs' attribute of an article provides you with a dictionary of its attributes. For example: ticket = client.ticket_get(ticketid, get_articles=True) Easiest way to view the names of all available attributes is to play around with the result of a TicketGet operation in an (i)python terminal. |
Is it possible to create a ticket, as an agent, but forcing it as if it was created by a user? I'm trying to allow users to create tickets via my interface without otrs being tied into my user DB, so ideally I'd like to use client.user_session_register with agent credentials, but create a ticket like so: Ticket(CustomerUser=current_user.email) Or something similar. |
I don't fully grasp what exactly you are trying to accomplish... Actually the readme here contains the exact same thing. If you are trying to accomplish something functionally different, I guess the OTRS mailinglist (https://groups.google.com/forum/#!forum/otrs_archive) is a better place to find out if what you want is supported by the soap interface / generic ticket connector and how this request should look like. If I'm not overlooking something, the whole functionality for a TicketCreate for the generic interface is supported by this module. |
$VAR1 = {
'ErrorMessage' => 'Got no OperationType!',
'Success' => 0
};
The text was updated successfully, but these errors were encountered: