<?xml version="1.0" encoding="UTF-8"?>
<ticket>
  <author>Fran&#231;ois Montel</author>
  <content>Currently, a milestone shows up as "incomplete" until it's given a "finished on" date. Maybe it's just me, but in my mind a milestone is complete if all the tickets that belong to that milestone are "complete". 

If I go to the Milestones page, I only want to see those milestones that are active, in that they have tickets that need to be worked on. Otherwise, the screen gets cluttered with milestones that are done but just don't have a "finished on" date. Of course, I could set a "finished date" on those milestones, but then another ticket surfaces for that milestone, the finished date on that milestone needs to be removed in order for the milestone to show up.

Of course, the other side could be argued that a milestone that has no pending tickets isn't necessarily "complete", and should remain visible on the milestones page. 

Of course part of my thinking is based on the fact that I'm used to how Trac displays things ,with the "tickets by milestone" where it only shows milestones that have active tickets. 

So I would propose that the default view be "milestones with open tickets". Then there would be links to "closed milestones" (all tickets are closed) or "completed milestones" (all tickets are closed and has a "finished on" date). 
</content>
  <created-at type="datetime">2009-04-01T23:02:29+01:00</created-at>
  <id type="integer">559</id>
  <milestone-id type="integer">5</milestone-id>
  <summary>Suggestion regarding expected behavior of "completed milestones".</summary>
  <updated-at type="datetime">2009-04-02T15:39:04+01:00</updated-at>
  <assigned-user>
    <id type="integer">2</id>
    <name>Dimitrij Denissenko</name>
    <username>dim</username>
  </assigned-user>
  <status>
    <id type="integer">1</id>
    <name>Open</name>
  </status>
  <priority>
    <id type="integer">2</id>
    <name>Can have</name>
  </priority>
</ticket>
