Work Items & Hierarchy
The Projects module in Helpin helps you plan, organize, and track everything your team delivers. This section explains the work items Helpin uses — the building blocks of the hierarchy — and how they fit together, from high-level goals down to day-to-day tasks.
The work-item hierarchy
Helpin organizes work in a simple top-down structure:
Objectives — high-level goals you want to achieve, optionally with measurable Key Results (an OKR-style setup). They connect day-to-day work to a larger outcome.
Epics — a large body of work that delivers a meaningful slice of an objective, such as an initiative, a release, or a customer problem. Epics group the tasks that contribute to them.
Tasks — the smallest tracked unit of work. Every feature, bug, or chore your team works on is a task, moving through your team's workflow states.
Checklists — lightweight to-do steps inside a task, for work that is too small to track as its own task.
Each of these is a distinct page area under the Projects rail: shared My Work, Objectives, Roadmap, and Reports pages, and under Your Teams the Tasks, Epics, and Sprints areas scoped to each team.
How the levels relate
An Objective can group several Epics — and one epic can belong to more than one objective.
An Epic contains many Tasks from the teams doing the work. Tasks keep their own team, workflow, and sprint; the epic provides the larger grouping.
A Task can carry a Checklist for small completion steps. When parts of the work need to move through states on their own, create additional tasks and link them to the parent task instead.
Sprints (time-boxed periods of work) collect tasks across epics and teams — see Planning & Sprints.
Helpin rolls progress up the hierarchy automatically: an epic's progress comes from the tasks inside it, a tactical objective's progress comes from its linked epics, and a strategic objective's progress takes its key results into account.
Choosing the right level
You want to… | Use |
|---|---|
Track a measurable company or team goal, optionally with OKRs | |
Group a large initiative that spans many tasks | |
Track one concrete deliverable through a workflow | |
Break a task into small steps without extra tracked items | |
Signal which task matters most | |
Label work as a feature, bug, or chore |
Next steps
If you're setting up a new workspace, a practical order is: create a team, create tasks to capture the work, group them into an epic, and (optionally) add objectives to tie everything to a goal. See Workflows & Organization for teams and workflows, and Planning & Sprints for time-boxed delivery.
Related
Was this article helpful?