Home → Problems →

Inaccurate milestone ticket count

• Edit

Kris Wallsmith

26 Jun, 2009 03:27 PM

My project's "current" milestone is inaccurate because Lighthouse thinks the milestone has 1 ticket remaining but it doesn't... It shows up as having 1 ticket remaining in the Milestones dropdown, but when I click the milestone I see 0 tickets.

1. 1 Posted by Rick on 26 Jun, 2009 05:24 PM

   

   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.

   • Edit

2. 2 Posted by System on 26 Jun, 2009 06:09 PM

   

   A Lighthouse ticket was created for this discussion

   • Edit

3. 3 Posted by jaywest on 27 Jun, 2009 05:10 AM

   

   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.

   • Edit

4. 4 Posted by Kris Wallsmith on 29 Jun, 2009 12:51 PM

   

   Milestone id is 40229.

   • Edit

5. 5 Posted by Rick on 29 Jun, 2009 01:03 PM

   

   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.

   I'm going to do a few things to fix this for the future:

   1. I'm removing the ability to clear the ticket state. That's a
   confusing option.
   2. 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.

   • Edit

6. 6 Posted by Kris Wallsmith on 06 Jul, 2009 05:51 PM

   

   Hi Rick,

   I made the change to that particular ticket, but the invalid ticket count is back now, on the same milestone...

   Thanks,
   Kris
   

   • Edit

7. 7 Posted by wbenedetto (at ... on 07 Jul, 2009 05:15 AM

   

   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.

   Logging out and logging back in fixed the problem. Maybe a session or cookie issue ....?

   • Edit

8. 8 Posted by Nathan on 04 Nov, 2009 04:36 PM

   

   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.

   • Edit

9. 9 Posted by Will Duncan on 04 Nov, 2009 05:56 PM

   

   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.

   • Edit

10. Nicole closed this discussion on 08 May, 2012 07:34 PM.