Subfeature

What is a Subfeature?

A Subfeature is a granular piece of work that belongs to a parent feature. When a feature is too large or complex to track as a single item, subfeatures let you break it down into smaller, independently trackable pieces — functional ideas that can be worked on and completed.

Subfeatures behave like features in most ways — they have the same fields, statuses, and can be assigned to releases — but they always live under a parent feature. When pushing to a development tool like Jira, a subfeature usually maps to a story.

When to use it

• Breaking down epics — When a feature represents a large initiative, create subfeatures for each deliverable piece.
• Granular tracking — Track status, ownership, and progress at a more detailed level than the parent feature.
• Integration mapping — Map individual Jira issues or tasks to subfeatures while keeping the parent feature as the high-level story.

Hierarchy

Product
 └─ Component
     └─ Feature
         └─ Subfeature      ← you are here

A subfeature belongs to exactly one feature (parent). Subfeatures are the leaf nodes of the product hierarchy — they cannot have children.

Key fields

Field availability depends on your workspace configuration. Use the Configuration endpoint to discover which fields are available for the subfeature type in your workspace.

Relationships

When creating a subfeature, you must specify a parent feature using a relationship.

Related objects

• Feature — parent of a subfeature
• Release — the release a subfeature is assigned to
• Note — customer feedback linked to subfeatures

Learn more

• Fundamentals of Productboard — Product Hierarchy
• Build your product hierarchy
  .