Modules
Project → Modules. A module is a named outcome with tasks in it. Unlike a cycle, it is not a window of time you fill — it is a thing that is either finished or not, and it may take three cycles or half of one.
Milestone, epic, initiative, release. Same idea.
When you want one
Section titled “When you want one”- The work has a shape somebody outside the team asks about: is Payments v2 done?
- The work spans cycles, so a cycle cannot answer for it.
- You want a progress number for an outcome rather than for a fortnight.
When you do not
Section titled “When you do not”If every task in the project is in exactly one module and the modules are called January, February, March — those are cycles. If the modules are called Frontend, Backend, Infra — those are labels. A module that nobody would describe as finished is not a milestone, and it will quietly turn into a second, worse backlog.
What it gives you
Section titled “What it gives you”| Progress | Done over total, in tasks and in points |
| A filter | module = "Payments v2" anywhere, including in a saved view |
| A row on the timeline | Its tasks drawn together, with its own bar |
| A row on the portfolio roadmap | Which is where a module earns its keep — see across projects |
A task in both
Section titled “A task in both”A task can be in a cycle and a module at once, and that is the normal case. Sprint 14 says when somebody is doing it; Payments v2 says what it is part of. Filtering on one does not disturb the other, and the two progress numbers answer two different questions that people routinely confuse:
- The cycle number is are we going to finish what we said we would this fortnight.
- The module number is are we going to finish this thing at all.
A cycle at 90% and a module at 20% is a completely normal and completely healthy Tuesday.