Artifacts
Artifact Relationships
Artifacts can reference other artifacts through relationship fields. These are defined in the template: a feature template has a tasks relationship, a memo template has a features relationship, and so on. Use them to build a hierarchy or draw connections across the plan.
The built-in relationships
| From | Field | To | Meaning |
|---|---|---|---|
| Feature | tasks | Task | Child tasks implementing the feature |
| Feature | bugs | Bug | Related bugs on the feature |
| Memo | features | Feature | Features grouped by this memo (memo-as-epic) |
Editing relationships
Open an artifact and pick a relationship field from the sidebar (e.g. Tasks on a feature). Click Add to search the project for matching artifacts, or Create to make a new one already linked.
Both sides of the relationship update; when you add SPR-abc123 as a task on a feature, the task's file gets a reference back.
Rendering
In the editor, relationships render as clickable chips so you can navigate the graph without leaving the app. In any view, you can show a relationship as a visible field on artifact cards, useful for seeing how many tasks a feature has at a glance.
Common patterns
Epic-style grouping
Create a memo for a larger initiative. Add features to its features relationship. Each feature carries its own tasks. The memo becomes the single place to see progress on the whole effort.
Bug triage
Link every bug reported against a feature to that feature's bugs field. The feature page then shows its open bug count alongside its task list.
Related
- Artifact Types — the built-in types and which relationships they have.
- Relationship fields — defining relationship fields on custom templates.
- The Artifact Editor — the sidebar where relationships are edited.