tag:help.lighthouseapp.com,2008-09-20:/discussions/problems/856-inaccurate-milestone-ticket-countLighthouse: Discussion 2012-07-20T12:23:49Ztag:help.lighthouseapp.com,2008-09-20:Comment/2212862009-06-26T17:24:01Z2009-06-26T17:24:01ZInaccurate milestone ticket count<div><p>Are you doing any bulk ticket editing? I'm trying to track this
bug down. Believe me, I know how to count properly -- there's just
something that people are doing that doesn't seem to update the
counts. If you need to close a milestone, find a resolved ticket in
that milestone and unset and reset the milestone for it. Or, bug me
with the milestone ID and I'll take care of it.</p></div>Ricktag:help.lighthouseapp.com,2008-09-20:Comment/2212862009-06-26T18:09:01Z2012-07-20T15:35:25ZInaccurate milestone ticket count<div><p>A Lighthouse ticket was created for this discussion</p></div>Systemtag:help.lighthouseapp.com,2008-09-20:Comment/2212862009-06-27T05:10:38Z2009-06-27T05:10:38ZInaccurate milestone ticket count<div><p>I am seeing this issue to with one of my Milestones. The
subheading on the Milestone over page shows: Expected: Jun 15th | 1
ticket remains, 3 tickets total. But there are no open tickets
listed below. As a result I have an overdue milestone that I am
unable to complete.</p></div>jaywesttag:help.lighthouseapp.com,2008-09-20:Comment/2212862009-06-29T12:51:05Z2009-06-29T12:51:08ZInaccurate milestone ticket count<div><p>Milestone id is 40229.</p></div>Kris Wallsmithtag:help.lighthouseapp.com,2008-09-20:Comment/2212862009-06-29T13:03:54Z2009-06-29T13:03:54ZInaccurate milestone ticket count<div><p>I found the issue. You had a ticket with no state, which was
throwing the query off. I moved the ticket to open for you to deal
with.</p>
<p>I'm going to do a few things to fix this for the future:</p>
<ol>
<li>I'm removing the ability to clear the ticket state. That's a
confusing option.</li>
<li>I'm modifying the milestone query to find all tickets not in
the closed state. This will find any tickets with invalid or blank
states as well.</li>
</ol></div>Ricktag:help.lighthouseapp.com,2008-09-20:Comment/2212862009-07-06T17:51:30Z2009-07-06T17:51:31ZInaccurate milestone ticket count<div><p>Hi Rick,</p>
<p>I made the change to that particular ticket, but the invalid
ticket count is back now, on the same milestone...</p>
<p>Thanks,<br>
Kris<br></p></div>Kris Wallsmithtag:help.lighthouseapp.com,2008-09-20:Comment/2212862009-07-07T05:15:08Z2009-07-07T05:15:08ZInaccurate milestone ticket count<div><p>I'm seeing the same issue. The counter in the Milestone dropdown
was 1. I had 8 issues assigned to that milestone. All of them were
added in a bulk edit.</p>
<p>Logging out and logging back in fixed the problem. Maybe a
session or cookie issue ....?</p></div>wbenedetto (at allaccess)tag:help.lighthouseapp.com,2008-09-20:Comment/2212862009-11-04T16:36:10Z2009-11-04T16:36:12ZInaccurate milestone ticket count<div><p>I'm having the same issue with milestone id 53220. The problem
first appeared when I attempted to reopen a ticket and move it to a
new milestone. Logging out/back in and unsetting/resetting the
milestone on an existing resolved ticket have no affect.</p></div>Nathantag:help.lighthouseapp.com,2008-09-20:Comment/2212862009-11-04T17:56:45Z2009-11-04T17:56:45ZInaccurate milestone ticket count<div><p>As a temporary fix, you can do a bulk edit on the milestone,
grabbing all the tickets in that milestone via the search and
setting them to resolved. The 1 remaining ghost ticket is then
cleared out and the next milestone will come up.</p></div>Will Duncan