Sometimes users submit feedback that contains several ideas, unrelated requests, or a long list of issues all bundled into one post. To help you manage these more efficiently, FeatureOS allows you to split a single feedback post into multiple separate child posts, by keeping the parent post untouched.
Why Split a Feedback Post?
You may want to split a post when:
A user submits multiple feature requests under one entry
A long description contains several independent issues
You want to assign different parts of the feedback to different teams
You need cleaner, structured items for prioritization or roadmap planning
Splitting ensures every idea becomes its own trackable post, while still keeping the relationships intact.
How to Split a Post
Follow these steps to create a new post from text within an existing one:
Open the feedback post from your Dashboard.
Highlight the portion of the description that you want to split out.
Click “New Post From Selection.”
A popup will appear, allowing you to review and create the new post.
Once created, the new item becomes its own standalone post, with its own votes, status, buckets, and assignee.
Parent and Child Issue Relationships
To maintain full clarity and context, FeatureOS automatically creates a parent–child relationship between the original post and any posts created from it.
How it works:
The Parent Post
Displays a list of all its child posts underneath.
Helps you see everything that was split out from the original entry.
The Child Post
Shows a reference to the parent post just below the title.
Makes it easy to understand where it originated.
Benefits of Splitting Posts
Splitting posts gives your team a clearer, more efficient way to manage feedback. Instead of working with one long, mixed submission, you can convert each idea into its own actionable item. This leads to:
1. Cleaner, more structured feedback : Each idea becomes a separate post with its own description, status, and context. This prevents important requests from getting buried inside longer messages.
2. Better alignment across teams: Different teams (Product, Engineering, Design, Support) can take ownership of the specific parts relevant to them.
3. More accurate prioritization: When ideas are split, each one can be scored, ranked, and sized separately, helping your roadmap reflect the true importance and impact of each request.
4. Improved traceability and context: Parent–child relationships ensure you don’t lose connection to the original submission. Everyone can see where a piece of feedback came from and how it relates to the bigger picture.
5. Easier planning and sprint preparation: Breaking feedback into smaller, actionable items makes grooming sessions smoother. Teams can estimate, plan, and schedule work without unnecessary complexity.
6. A cleaner feedback pipeline: Your feedback boards stay organized, making it easier for stakeholders to browse and understand user requests without confusion or duplication.
Was this helpful?