I think it's confusing and redundant to have milestones and task lists. I would eliminate task lists and just leave milestones so it would be like this:
Projects
Milestones
Tasks
Sometimes when I create a milestone, and the create a task list, it seems like I'm repeating information.
Suppose a milestone is: Get release 0.8.5 out. Maybe you will have 3 task lists then:
1) documentation
2) coding
3) testing
The tasks might be:
1) documentation
1.1) design new table of contents
1.2) perform spell check
1.3) gather documents of others
1.4) integrate into release documentation
1.5) write release notes
2) coding
2.1) design language selection
2.2) change code
2.3) have code reviewed
2.4) integrate into release
3) testing
3.1) test email functionality
3.2) test new functionality x, y and z
I guess it depends.
Yes but with out the ability to add due dates to at least the task list, this is not useful as you only have one due date the final milestone when you want to release the project, but how do you know if you are on time for your task or task list if you have no due dates? so i would say that any one using PP would create 3 milestones anyways, so they could have due dates. So I agree either task list need to be removed or add the ability to have a due date assigned to them.
I think the ability to add a due date to tasks would be the easiest and best.
http://www.projectpier.org/node/1911