Use Fibery Lookups for Feature Context
Add a Lookup field to display a field from a related record. It exposes existing context without creating another editable relationship.
Before you start: Have Feature → Epic → Objective relations and configuration access. Each Feature in this example has a single Epic so its Objective is unambiguous.
Worked example: Invite audit belongs to the Access Epic, which belongs to Improve onboarding. A Feature-side lookup displays that Objective without maintaining a second direct relation.
Step-by-step guide
Check the relation path
Open the Feature and confirm its Epic, then the Epic’s Objective. Repair missing links before adding a display field.
Add the Lookup
On the Feature database or an entity, select + New Field → Lookup. Choose Epic in the Relation selector.
Choose the source field
Select Objective from Epic and save. Give the lookup a name that distinguishes it from an editable direct relation.
Verify the example
Open Invite audit and check Improve onboarding appears. Change the source Epic’s Objective on a sample case and inspect the resulting display.
Check the reader’s context
Test a normal collaborator’s access, especially for Rich Text source fields. A lookup is not a substitute for deliberate source permissions.
Common mistakes
Editing a lookup as if it were a relation
Lookups are read-only. Change the underlying relationship or source field instead.
Sources and verification
Based on product documentation checked on 2026-11-04. This is a documentation-based guide, not a hands-on benchmark. Features and availability can change.