A broad discovery like "Improve dashboard performance" often turns into several pieces of work. Sub-discoveries let you split it without losing the big picture: each piece gets its own state, fields and engineering issues, while the parent keeps the full count of customer demand.
When to use them
Splitting a topic that grew too big: when feedback on a discovery covers several distinct needs.
Exploring solutions: the parent holds the problem, each sub-discovery is an option you're considering.
Shipping in steps: one sub-discovery per release or per team.
Don't split too early, though: a few broad discoveries with lots of feedback are easier to prioritize than dozens of small ones. See Best practices for structuring your discoveries.
Create a sub-discovery
Create one wherever you are:
From the discovery: open it and click Add sub-discovery.
From the table: click + next to a discovery's title.
While categorizing feedback in the Inbox: when you link a piece of feedback, create the sub-discovery right from the pop-up, without leaving the Inbox.
Turn an existing discovery into a sub-discovery
Drag and drop it onto another discovery in the table.
Select one or more discoveries in the table and use the bulk actions menu to move them under a parent.
From the discovery itself, open its ⋯ menu, click Move discovery, and pick the parent.
To make it a regular discovery again, move it back under a component.
Sub-discoveries go one level deep. A sub-discovery can't have sub-discoveries of its own, and a discovery that already has some can't become a sub-discovery.
How feedback and fields add up
You can link feedback to the parent or to any sub-discovery. At the parent level, everything adds up: its feedback count includes its sub-discoveries, and so do its rollup fields, like the total ARR of the customers asking. Prioritizing on the parent still reflects all the demand.
Hover the feedback count in the table to see the split between the parent and its sub-discoveries.
See them in your views
In the table, expand a parent to show its sub-discoveries.
In a kanban view, turn on View sub discoveries in the view options to show them as cards of their own.
Deleting a parent deletes its sub-discoveries and their feedback links too. To keep a sub-discovery, move it under another discovery or a component first.