Split posts

How to get there: Click All Posts in the sidebar, open a post, click the More (⋯) menu, then choose Split.

Splitting takes one post and turns it into several. Use it when a single feature request actually covers two or three distinct ideas, and you want each one tracked, voted on, and prioritised separately.

How splitting works

The Split screen shows the original post at the top and a list of rows below where you define the new posts. Each row needs a title and accepts a description, status, and category.

  • The first row overwrites the original post. Whatever you type there replaces the title and description of the post you are splitting.
  • Every additional row creates a brand new post. Status, category, and description are taken from that row.
  • Leave a row's title empty to skip it. At least one row must be filled in.

You can prepare two, three, or as many rows as the original idea actually contains.

What happens to votes, followers, and comments

The split is designed to keep everyone informed without making them re-engage:

  • Votes from the original post are replicated onto every new post. Vote counts carry across, so each new post starts with the same momentum.
  • Followers of the original post are attached to every new post. They will get notifications for whichever ones move next.
  • References (linked posts) are copied to every new post as well.
  • Comments and attachments stay on the original post. They are not duplicated to the new posts, so the conversation history has one home.
  • Status of the original post is not changed by the split. You can pick fresh statuses for each new post in the row form.

ProductLift automatically adds a comment to the original post listing the new posts it was split into, so the trail is visible to admins and followers.

When to split

  • Bundled feature requests. "Dark mode and keyboard shortcuts" really wants to be two posts.
  • Mixed feedback. One submission contains a bug report and a feature idea. Split the bug into its own post on the bug board.
  • Phased work. Break "Mobile app" into "iOS app" and "Android app" so each can move through the roadmap independently.
  • Different owners. When two parts of a request need to land on different teams' boards.

Reversibility

Splitting is not automatically reversible. If you change your mind, you can merge the new posts back together, but the original's comment history will not be duplicated back. Review your rows carefully before confirming.