Organize Productboard Components and Features
Use Library → Products → Product hierarchy to add a Feature beneath the correct Product or Component. Use the Feature’s Hierarchy parent field when its location needs to change.
Before you start: Use a Maker or Admin account with editing access. Start with an existing Product and Component; this guide concerns organization, not a full feedback collection rollout.
Worked example: CSV export belongs under the Reporting Component of Atlas. Keeping one Feature there avoids separate copies under Support and Sales just because both teams requested it.
Step-by-step guide
Locate the intended parent
Open Main menu → Library → Products → Product hierarchy. Find Atlas and its Reporting Component before creating the idea.
Create the Feature
Hover the parent, choose Add under → Add feature, and enter CSV export. Click away when finished adding items.
Define its scope
Open the Feature Detail tab and describe what users can export and which formats are outside this idea. Keep the name specific enough to distinguish another export request.
Correct the location if needed
Use Hierarchy parent in the Feature sidebar to select Reporting. Search the full hierarchy when the recent suggestions do not show the intended parent.
Check the hierarchy and references
Find the Feature under its new parent and inspect linked evidence. Explain the placement to colleagues who previously searched in another area.
Common mistakes
Duplicating one need across departments
A Feature can collect evidence from several teams. Department-specific copies fragment the decision and demand history.
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.