Projects & Roadmaps
Track work as projects through a clear lifecycle and organize them into roadmaps by period.
Projects capture the units of work your organization delivers, and roadmaps group those projects into time periods so everyone can see what is planned and what is in flight. Together they give you a shared, structured picture of delivery.
Projects#
A project is a piece of work with its own members, status, and (optionally) links to a client or ticket. Projects can live at the organization level or be scoped to a specific hackathon, so the same lifecycle works for both ongoing initiatives and time-boxed events.
Who can create a project#
Any member can create a project. New projects start in the suggested status, which keeps the barrier to proposing work low while still giving admins a review step before anything becomes committed. Admins approve suggestions to move them forward.
The project lifecycle#
Projects move through four statuses, displayed as columns in a Kanban view so you can see the whole pipeline at a glance and move work between stages.
| Status | Meaning |
|---|---|
| Suggested | Proposed by a member, awaiting review |
| Approved | Reviewed and accepted, ready to begin |
| Active | Currently being worked on |
| Archived | Closed out and kept for the record |
Use the Kanban board to track flow and reprioritize. Approving a suggested project is an admin action; from there the project can progress to active and eventually be archived when the work is complete.
Members, stars, and links#
- Members: Projects have a many-to-many relationship with members, so a person can belong to multiple projects and a project can have many contributors. This is what feeds capacity and assignment views elsewhere in the platform.
- Stars: Any member can star a project as an interest or favourite marker. Stars are a lightweight signal of enthusiasm or attention, separate from membership.
- Client and ticket links: A project can optionally link to a client or a ticket. This connects delivery work back to the account it serves or the request that prompted it, and that ticket context carries through to related areas such as the planner.
Bulk import#
When you are setting up an organization or migrating from another system, you can bulk import projects rather than creating them one by one. This is the fastest way to seed your workspace with existing work.
Roadmaps#
A roadmap organizes projects into periods so you can plan and communicate delivery over time. Like projects, roadmaps can be organization-level or scoped to a single project, letting you zoom out to a company-wide view or focus on the phases of one initiative.
Periods and quarters#
Roadmaps arrange projects into periods such as quarters (for example, 2026-Q1). Grouping by period turns a flat list of work into a timeline that makes sequencing and commitments clear to stakeholders.
Project status on a roadmap#
Each project placed on a roadmap carries its own roadmap status, which is more granular than the project lifecycle and describes how delivery is tracking:
| Roadmap status | Meaning |
|---|---|
| Planned | Scheduled but not yet started |
| In progress | Actively underway |
| WIP – on target | In progress and tracking to plan |
| WIP – not on target | In progress but at risk or behind |
| Completed | Delivered |
| Cancelled | Dropped before completion |
The two "WIP" states are especially useful for status reporting: they let you flag work that is moving but off track without waiting for it to slip fully.
Priority#
Alongside status, every project on a roadmap has a priority so you can distinguish the critical from the routine:
- Urgent
- High
- Medium
- Low
Combining status and priority makes it easy to spot the work that is both important and at risk.
Bulk import and visibility#
- Bulk import: Roadmaps support bulk import, so you can populate a period plan quickly instead of adding each project individually.
- Visibility: Each roadmap has its own visibility setting. A roadmap can be made public, and a public roadmap can be indexed so it is discoverable outside the organization. Use this when you want to share your plan externally; keep it private when the plan is internal.
Putting it together#
A typical flow looks like this:
- A member proposes work, creating a suggested project.
- An admin reviews and approves it.
- The project becomes active as work begins.
- You place the project on a roadmap period and set its roadmap status and priority.
- As delivery proceeds, you update the roadmap status (planned → in progress → WIP – on target, and so on) to keep the plan honest.
- When the work is done, the project is archived and shown as completed on the roadmap.
For a higher-level rollup of project counts, capacity, and roadmap tracking across the organization, see the Portfolio. To allocate people to this work across a timeline, see the Resource planner.