Track Feature Dependencies in Productboard
Open a Feature’s Dependencies section, use Add dependency and verify the direction. Surface Is blocking and Is blocked by on the planning board.
Before you start: This capability is documented for Business and Enterprise. Have the related Features and their timeframes ready for a small dependency example.
Worked example: Permission model blocks Invite audit. If Invite audit is scheduled before Permission model finishes, the planning view should expose that scheduling conflict.
Step-by-step guide
Choose the real prerequisite
Identify the specific deliverable needed before the other Feature can proceed. Avoid adding a vague team association as a blocker.
Add the dependency
Open the Feature sidebar → Dependencies → Add dependency. Choose the relevant item type and search for the other item.
Verify the direction
Use the relationship dropdown beside the added item. Confirm Permission model is blocking Invite audit rather than the reverse.
Expose it on the grid
Use Add columns → Dependencies and enable Is blocking and Is blocked by. Check both rows in the planning meeting.
Resolve the timeframe conflict
Inspect red conflict indicators. Adjust timeframes on the sidebar or timeline so the dependent work is in the intended order.
Common mistakes
Expecting dependencies to push into Jira
The current guide lists Jira dependency push as unsupported. Keep an explicit delivery handoff for that relationship.
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.