tag:help.lighthouseapp.com,2008-09-20:/discussions/problems/13193-ticket-ids-are-being-reusedLighthouse: Discussion 2014-04-07T18:16:26Ztag:help.lighthouseapp.com,2008-09-20:Comment/256729182013-03-07T14:52:40Z2013-03-07T14:52:40ZTicket IDs are being reused<div><p>Yes, that's always been the case. The number code just does this
(ruby)</p>
<pre>
<code>def self.next_number_for(project_id)
Ticket.maximum(:number, :conditions => ['project_id = ?', project_id]).to_i + 1
end</code>
</pre>
<p>I suggest you don't delete tickets, just close them with a
custom close state. Even if it's "invalid" or "duplicate". Since
you're clearly relying on the tickets being there with references
from other tickets and external apps, it seems like a really bad
idea to be deleting them.</p></div>Tiger Teamtag:help.lighthouseapp.com,2008-09-20:Comment/256729182013-03-07T15:08:38Z2013-03-07T15:08:40ZTicket IDs are being reused<div><p>Am I reading this right? You are telling <em>me</em> to not use
a functionality of <em>your</em> platform because it breaks
ticket/commit refs on <em>your</em> platform?</p>
<p>I mean – where's the point in supporting ticket/commit
refs at all when it clearly doesn't work persistently, or at all,
even within lighthouse?</p>
<p>As I see it, that's a bug – not my fault for using
provided default functionality.</p></div>Jonas Hermsmeiertag:help.lighthouseapp.com,2008-09-20:Comment/256729182013-03-07T15:17:05Z2013-03-07T15:17:05ZTicket IDs are being reused<div><p>Pretty much. We have a lot of features than can conflict with
each other; for example you can turn on priorities, set a bunch of
things to high priority, turn off priority again, and you've lost
the ability to view that information.</p>
<p>So, why are you deleting tickets when they contain important
information?</p></div>Tiger Teamtag:help.lighthouseapp.com,2008-09-20:Comment/256729182013-03-07T15:42:56Z2013-03-07T15:42:56ZTicket IDs are being reused<div><p>Just to be clear, I'm not disagreeing with the fact that there's
a bug; I'm not trying to be facetious, either. It's a refactor I
don't think we're going to get done in any reasonable amount of
time. There are just two of us working on lighthouse and we have a
huge few releases taking all our time.</p>
<p>So the easiest answer is "don't delete tickets if you rely in
their information" which includes ticket numbers. Moving to a state
workflow that includes invalid-type closed states is what we did a
while back and it works well particularly when we reference tickets
that were later marked as invalid because we can track why they
were "removed" whereas deleting tickets you lose that info.</p></div>Tiger Team