Not getting body and body-html attributes for tickets

peeja's Avatar


24 Jan, 2009 07:27 PM

When I get a list of tickets, they don't contain <body> or <body-html> elements. When I get a single ticket, the ticket itself doesn't have them, though the first (and only) version does.

  1. 1 Posted by peeja on 06 Feb, 2009 08:42 PM

    peeja's Avatar

    I'm still seeing this. Is this expected or a bug?

  2. 2 Posted by Rick on 14 Mar, 2009 02:34 PM

    Rick's Avatar

    It's a workaround for a weird bug. Basically, people were fetching tickets from the API, changing something other than body, and that body attribute would get set as the most recent comment. Perhaps I should send original_body and latest_body then?

  3. 3 Posted by peeja on 16 Mar, 2009 11:07 PM

    peeja's Avatar

    I'm not sure I understand the bug, but yes, that would be helpful.

  4. 4 Posted by Rick on 16 Mar, 2009 11:38 PM

    Rick's Avatar

    The ruby library pulls the data when you do Ticket.find. When saved, it sends all the data to the Lighthouse update action. Lighthouse interprets the body as a new comment (it's how the HTML form essentially works). If I move the fields out to something not named #body, then they'll be ignored. I'll do this as soon as I can... though it will require some Lighthouse downtime. I'm thinking Thursday night (watch Lighthouse for the official announcement).

  5. 5 Posted by peeja on 17 Mar, 2009 02:37 PM

    peeja's Avatar

    That would be awesome. Thanks!

  6. brandi closed this discussion on 29 Jun, 2012 10:10 PM.

Discussions are closed to public comments.
If you need help with Lighthouse please start a new discussion.

Keyboard shortcuts


? Show this help
ESC Blurs the current field

Comment Form

r Focus the comment reply box
^ + ↩ Submit the comment

You can use Command ⌘ instead of Control ^ on Mac