Task types
Every task in Helpin has a type that says what kind of work it is. Types help teams filter boards, understand the nature of the work at a glance, and keep reporting meaningful.
The three types
Feature — work that changes the product or service: new functionality, UI updates, integrations, or other user-visible improvements.
Bug — something that is broken: a defect that needs to be fixed so the product behaves correctly.
Chore — work that must happen but does not change the product for users: refactoring, dependency upgrades, DevOps, and other maintenance.
Set or change the type
The type is shown next to each task's title on cards and in the task detail view, using a distinct color and icon per type (orange for Feature, red for Bug, blue for Chore).
When creating a task, choose the type from the Type row in the create dialog. New tasks default to the type your team has configured (usually Feature).
On an existing task, open the task and change Type in the detail sidebar. Changing a task's type updates how it is categorized across boards, filters, and reports.
Which type should I use?
Type | When to use | Example |
|---|---|---|
Feature | Delivering something new or changed for users | Add CSV export to Reports |
Bug | Fixing something that is not working as intended | Login fails on Safari when two-factor authentication is enabled |
Chore | Keeping the system healthy without user impact | Upgrade the payments library to v3 |
A task's type is independent of its priority and workflow state. A bug can be low priority (a cosmetic glitch) just as a feature can be urgent (a critical launch requirement). Use Priority for importance, and Severity for how badly a bug impacts users.
Related
Was this article helpful?