A feature request board for WordPress is a page where visitors submit ideas, vote on others, and see a status for each request. With Changeloger you can set one up in five steps: install the plugin, create a product, add categories, insert the shortcode, and manage requests from the admin.

This is a practical setup guide for plugin and product owners. If you are more interested in how to invite users to participate, read how to collect feature requests from plugin users. For a comparison of the plugin landscape, see the WordPress feature request plugin guide.

What you need before you start

You need a WordPress site, the Free Changeloger plugin, and a page where the board will live. Everything in this guide works on Free unless it is marked Pro.

Step 1: Install Changeloger and create a product

Install and activate Changeloger from your WordPress dashboard. Changeloger organises feedback per product, so create the product that your feature requests belong to. Free includes one product; Pro supports unlimited products, each with its own board.

Step 2: Set up categories for your board

Categories group requests so they are easy to browse. The defaults are Feature Requests, Bug Reports, Integrations and Languages. You can add, rename or delete them. Keep the list short, because every extra category adds a decision for the user who is submitting an idea.

Step 3: Add the feature request board for WordPress with a shortcode

Open the page where you want the board, add a Shortcode block and paste this line, using your own product ID:

In Changeloger, Feedback there is a Shortcode button that generates the code for you, plus a one-click preview of the live board. You can also show the board as a tab in the Release Hub block. Embedding the board on an external site through an iframe is a Pro option.

Step 4: Understand what users will see

The public board is a clean list of cards. Each card shows a vote count, a status badge, a title, a short description, the author and a category tag. Visitors can sort by New, Top or Trending, filter by status, category and date, and search live. Long lists use pagination.

Statuses you can use

Every request carries one of these status badges:

• In Review for new ideas you have not decided on.
• Planned for confirmed work.
• In Progress for work that is underway.
• Completed for shipped features.
• Rejected for ideas you will not build.

Step 5: Moderate requests from wp-admin

Under Changeloger, Feedback you get summary cards (Total Feedback, In Review, In Progress, Completed) and a sortable table with title, category, status, votes, date and author. From there you can search, filter by visibility (Public or Private), edit any item, change statuses in bulk, delete in bulk, moderate comments and manage categories.

You can also add requests manually. That is helpful for ideas that arrive by email or support ticket: add them, set a category and status, and keep them public or private.

Where to place the board

A feature request board for WordPress works best on a page that is easy to reach. Good options are a dedicated “Feature requests” page linked from your plugin documentation, a tab inside a product updates page, or a page linked from the footer of your site. Because the board responds to screen size and loads without page reloads, it works on mobile as well as desktop.

If you already publish releases with Changeloger, the Release Hub block lets you show Releases, Feedback and Roadmap as tabs on one page. That way users can read what shipped, request what is next and follow progress without leaving the page.

How to keep spam and clutter down

A feature request board stays useful only if it stays tidy. Use these habits:

• Keep categories few and clearly named.
• Mark internal notes or unfinished ideas as Private instead of deleting them.
• Review the In Review queue on a schedule, then set a real status.
• Use bulk actions to tidy old items in one step.
• Reply to comments to keep discussions useful (comments are a Pro feature on the public board; admins can moderate them).

Free plan limit and what Pro adds

The Free plan supports up to 20 feedback items per product. When you reach the limit, the submit button is paused and a prompt appears. Pro removes the limit.

Free includes the public board, upvoting, categories, sorting, filters, search, status badges and the admin tools above. Pro adds downvoting, guest voting, public comments, in-page login and registration, Google login, embeds and unlimited products. The Free vs Pro page has the full comparison.

Best practices for a healthy board

• Seed the board with a few real ideas so visitors see how it works.
• Merge your own support inbox into it by adding requests manually.
• Answer new items quickly and update statuses.
• Link completed items to your release notes; our guide to a professional feedback board in WordPress shows a good layout.
• When you are ready, promote top items to a roadmap (Pro Kanban board).

Example: a board for a booking plugin

Suppose you maintain a booking plugin. You create a product called “Booking Plugin”, keep the four default categories, and add the shortcode to a page named “Feature requests”. You then add three requests yourself, taken from recent support tickets, and set each to In Review. Within days, users find the page, upvote the ideas that match theirs, and post new ones. You sort by Top, move the leader to Planned, and the status badge tells every voter what happened. No extra tool and no spreadsheet are needed.

That small loop is the reason to run a feature request board for WordPress on your own site: requests, votes and admin tools all sit in one place. When you want to show the plan visually, the Pro roadmap builds on the same data.

Frequently asked questions