Thanks, Jim. I should have checked the wiki. Progress, but now the server replies
RT/4.2.3 200 Ok
# Could not create ticket.
# Could not create ticket. Queue not set
The user has all ‘Modify’ rights on the queue directly, not through a group. I can tell that RT is consuming all the headers because RT logs the ‘Starts’ and ‘Due’ fields.
Thanks, Jim. I should have checked the wiki. Progress, but now the server replies
RT/4.2.3 200 Ok
# Could not create ticket.
# Could not create ticket. Queue not set
The user has all ‘Modify’ rights on the queue directly, not through a group. I can tell that RT is consuming all the headers because RT logs the ‘Starts’ and ‘Due’ fields.
Any suggestions appreciated.
Confirm the queue name in the call is exactly the same as the queue name
in RT. Also try running it with SuperUser rights. If it works you know
it’s a rights issue and can focus there (confirm SeeQueue, CreateTicket,
etc.).
You are getting a session cookie to authenticate, right? And you still get this error even if the user you authenticate as is one with SuperUser rights? If so that tends to imply that there’s something amiss with passing the session cookie to the server, as a user with SuperUser rights should be able to do anything.
@knation Unfortunately for me I can’t use the REST2.0 version because it’s not implemented in our RT.
@GreenJimll The javascript code is directly loaded from the Display.html web page of RT and when I click on button that execute the Ajax call.
Anyway if the cookie was not present I would have an error like : 401 Credentials required but this is not the case.
As a proof when I make a request in GET ../REST/1.0/ticket/xxxxxx/show it works because I get a return with all the data of the ticket.
So now I don’t understand anything, actually with a GET method and by encoding the line break I manage to create the ticket. Your trick works perfectly !
I was trying to debug the file Ticket.pm with other method to see what args are passed and here is the dump part of result :