Milestones and Modules

Modules are are buckets where time and tasks are attached for reporting and for management. You can run filters to see which tasks are in a certain module as well as run reports on time for that module as well. If you don’t think you need to use modules we recommend creating one general module. When adding time or creating tasks the general module will get auto selected since it is the only item in the drop down menu. If you need to expand and use modules later you can definitely do that. For us, we typically use feature driven modules like ecommerce, admin tools, etc. This allows us to manage those features and run reports on the efforts in those areas.

These discussions about modules and work types might be helpful as well:
https://www.myintervals.com/forum/discussion/82/modules-how-to-use-them/
https://www.myintervals.com/forum/discussion/101/modules-work-types-and-tasks/

A hierarchy diagram is available here as well:
https://www.myintervals.com/forum/discussion/452/adding-a-new-module/

Milestones can be used for a multi task deliverable where all of the tasks that need to be done for the deliverable can be attached to the milestone. Milestones have a quasi scheduling component as well where you can move around other milestones and tasks if a deliverable is delayed. Say for example you have a project with four milestones if the first one runs late you can reschedule the milestone and move all of the tasks and milestones for the project. On the web development side of our business we typically do not use milestones with our maintenance/retainer work but we always use milestones for our full project. If you happen to be doing Agile development milestones can be used for sprints or iterations.

This video introduction to milestones might be worth a look.