Create a Dependency Relation in Fibery
Create a self-relation on the work database and enable Use relation as dependency. Fibery creates Blocking and Blocked By fields for the two directions.
Before you start: Have database configuration access. Use two sample Features, and decide whether one Feature may block several others before choosing cardinality.
Worked example: Permission model must finish before Invite audit begins. On Invite audit, Permission model belongs in Blocked By; reversing that direction would misrepresent the release risk.
Step-by-step guide
Create the self-relation
On Feature add a Relation field targeting Feature itself. Use many-to-many when work can have several prerequisites and several dependents.
Enable dependency behavior
Open Advanced, turn on Use relation as dependency and save the field. Confirm Blocking and Blocked By are present.
Link the concrete blocker
Open Invite audit and add Permission model under Blocked By. Open Permission model to verify the reverse Blocking link.
Visualize on a Timeline
In Timeline Items enable dependencies for Feature. Use one entity per lane to inspect the relationship.
Choose schedule behavior deliberately
Review the timeline shifting strategy before moving dates. Test on the sample pair so an edit does not unexpectedly reschedule active work.
Common mistakes
Using a generic cross-database relation
Only self-relations can be marked as dependencies. A related Team or customer is not a scheduling blocker in this mechanism.
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.