Milestone management

bump. +1 for this feature.

I see a lot of potential for using this module in project management…
But milestone management is definitely needed if this is to compare with Trac or other robust tracking tools.
Here's my two cents on how milestone tracking should work:

• create milestones for each project (sprint #, target date)
• assign issues to specific milestones
• filter and sort by milestone when viewing lists of issues (similar to how version is a filterable / sortable field when the Project Releases module is enabled)

See the attached image of how a milestone solution might look.

@joe-b: I tried your suggestion (CCK type for milestones) but things get ugly when there are multiple projects. Basically there isn't an elegant way to filter the display of milestones on a per-project basis…due to the inability to pass dynamic arguments when pulling a view into a node-reference field.

On a project management site I'm building with project_issue, I just turned on project_release and created "releases" for various milestones. It's not ideal, but it definitely gets the job done for now. It'd be more complicated on a site that has both releases and milestones, but even then, it seems like using nodes to represent the milestones is still the right approach. Perhaps it'll all get cleaned up and beautifully generalized when we port all of this to D7 field API in the 7.x-2.* series and remove all the hard-coded custom content types...

Meanwhile, I encourage people to at least consider using project_release for this. You can pretty easily hide/alter all the stuff on the project nodes themselves about "releases" as such. See hook_project_page_link_alter() ...