tag:help.tenderapp.com,2008-11-12:/discussions/problems/411-delay-when-creating-lighthouse-ticketTender: Discussion 2011-04-07T06:08:14Ztag:help.tenderapp.com,2008-11-12:Comment/868892009-03-02T20:58:04Z2009-03-02T20:58:04ZDelay when creating Lighthouse ticket<div><p>The delay there is definitely on purpose. When you create a new
ticket, Tender has to talk to Lighthouse, and Lighthouse has to
talk back to Tender. This process can be slow, and if one service
is having problems, has the capacity to result in an error. For
these reasons, we push this process into a background job so that
errors can be retried, and you don't have 30s-5m pageloads when
creating a ticket.</p>
<p>If you're looking to who to assign it to & who gets
notified, we'll always be improving this form and hopefully you'll
be able to do this right from the inline form eventually. In the
meantime, you <em>can</em> assign Lighthouse tickets using the
bracket syntax. So in the ticket body, you might have something
like this:</p>
<blockquote>
<p>Widget X is broken because of reason Y. [responsible:Kyle]</p>
</blockquote>
<p>If you have a user who starts with "Kyle" (for example, my
Lighthouse name is "Kyle Neath") it will automatically be assigned
to them.</p></div>Kyle Neath (GitHub Staff) tag:help.tenderapp.com,2008-11-12:Comment/868892009-03-03T00:48:29Z2009-03-03T00:48:29ZDelay when creating Lighthouse ticket<div><p>We're looking into polling techniques to update it live while
you're viewing the page... However the time is usually so brief
that it's not a huge deal.</p>
<p>The queuing system came in handy recently when a new deploy
added a bug to ticket creation. It didn't interrupt anyone's flow
in Tender. The jobs just waited patiently for me to fix the bug and
retry.</p></div>rick