[rt-users] Question about REST interface and status

Thu Jun 21 14:01:26 EDT 2012

I’m using a C# web site and request to create tickets as well.
I’m using the AppendLine function of a stringbuilder object in C#.  I ended up adding doing a find and replace on my comment and removing \n before I send the request.
Msg.ToString().Replace("\n", "")

This might not be the most elegant solution, but it is working for me.
-Jennifer

From: rt-users-bounces at lists.bestpractical.com [mailto:rt-users-bounces at lists.bestpractical.com] On Behalf Of Jeff Konnen
Sent: Thursday, June 21, 2012 1:25 PM
To: rt-users at lists.bestpractical.com
Subject: Re: [rt-users] Question about REST interface and status

does anybody use REST to create tickets in RT
am I the onlyone having this carriagereturn issue?

--
Jeff Konnen

On Monday 18 June 2012 at 07:51, Jeff Konnen wrote:
Hi,
this is the way we are creating the ticket, by using a HTML form:

<html>
<form method="POST"
action="http://xxx/REST/1.0/ticket/new/">
  User: <input type="text" name="user" size="20"><br>
  Pass: <input type="text" name="pass" size="20"><br>
  Content: <textarea rows="10" name="content" cols="30">id: new
Text: This is the ticket text
Subject: This is my ticket
Status: resolved
Queue: 6</textarea><br>
  <p><input type="submit" value="Submit" name="B1"><input type="reset"
value="Reset" name="B2"></p>
</form>
</html>

Thanks
Jeff
On Sat, Jun 16, 2012 at 2:19 AM, Kevin Falcone <falcone at bestpractical.com<mailto:falcone at bestpractical.com>> wrote:

On Fri, Jun 15, 2012 at 11:23:27PM +0200, Jeff Konnen wrote:
>    # Could not create ticket.
>    # Status 'resolved
>    ' isn't a valid status for tickets in this queue.
>
>    Is this error due to the carriage return and how can I avoid it?
There's a good chance that it dislikes the carriage return.
However, we'd need to know how you're creating the ticket and what
you're sending across the wire to make suggestions.

-kevin

--
Jeff Konnen

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bestpractical.com/pipermail/rt-users/attachments/20120621/3d708e65/attachment.htm>