Artifacts
Artifact Types
Spruce ships with five built-in artifact types. Each has its own template, a schema that defines its fields, status options, display color, and icon. Pick the type that matches how you think about the work.
The built-ins
| Type | Use for | Notes |
|---|---|---|
| Feature | User-facing work: new capabilities, improvements, enhancements | Has tasks and bugs relationship fields |
| Task | A concrete, implementable unit of work | Can stand alone or belong to a feature |
| Bug | A defect, regression, or unexpected behaviour | Can stand alone or link to the feature where the bug originated |
| Chore | Internal work with no direct user impact: build upgrades, dependency bumps, operational excellence, CI/CD, refactors, docs | Distinguishes maintenance from feature development |
| Memo | Top-level container for grouping related work: written thinking, epics, PRFAQs, roadmaps, decision records | Has a features relationship field; use it where other tools would use an "epic" |
Colors and icons are defined in each type's template and can be customized per project. See Display properties.
Custom types
You can create your own artifact types (e.g. incident, rfc, design-review). Each gets its own template file in the project's templates/ folder. See Creating a Template.
Related
- Fields, Status, and Priority — the common fields on most types.
- Artifact Relationships — how types link to each other.
- Creating a Template — defining your own type.
- Editing Built-in Templates — customizing the shipped types.