Modules
Break a Project down into the pieces your team actually works on.
What is the Modules screen?
Modules sit between Projects and Tasks — each Module belongs to one Project and groups together the Tasks needed for a specific feature, component or phase of that project's work.
Why use Modules?
Big projects are hard to track as one flat list of tasks. Modules let you break a project into manageable chunks (e.g. “Auth”, “Billing”, “Frontend”) so progress can be tracked at that level too, not just project-wide.
When would I use this screen?
- Breaking a new project into logical work areas
- Checking how far along a specific feature/component is
- Finding the right module to attach a new task to
Before you start
A Module must belong to a Project, so create the Project first (see Projects). You'll need access to the Modules screen under ETA.
Reading the stats
| Stat | Meaning |
|---|---|
| Total Modules | Every module on record. |
| Completed | Modules marked Completed. |
| In Progress | Modules currently marked In Progress. |
| Avg. Completion Time | Average number of days from a module's start date to completion. |
How to add a new module
- Open Modules
Go to ETA → Modules in the sidebar.
- Click Add Module
Click + Add Module.
- Choose the Project
Select the Project this module belongs to — this field is required and can't be left blank.
- Fill in the module details
Enter a Module Name, Status and Start Date, then save.
The module table
Each row shows the module's ID, Module Name with a completed/total task count badge, Status, Start Date, and row-level Actions.
Recovering a removed module
Use View Trash to find and restore a module that was removed.
Merging duplicate modules
Use Merge at the top of the page to combine two modules that were accidentally created for the same work.
Example
Video walkthrough
Show transcript
Transcript will be added when the video is published.