To collect feature requests from plugin users, give them one obvious place to post ideas, let them upvote what others have posted, and show the status of each request. A feedback board on your own WordPress site does all three, and stops requests from getting lost in support threads and email.

This guide focuses on the user side of the process: where your plugin users already are, how to invite requests, and how to keep them engaged. It uses the feedback board in Changeloger. If you want the technical setup of the board itself, see our feature request board for WordPress setup guide.

Why it is hard to collect feature requests from plugin users

Plugin users ask for features wherever it is convenient for them: a support thread, a review, a contact form, a chat message. None of those places rank or count requests, a problem described in this WPShout case study on plugin feature request systems. You end up building from memory, and users who asked never hear back.

A single public board fixes this. Each idea has a page, a vote count and a status, so both you and your users can see how much demand there is.

Step 1: Put the request link where users already look

Collecting requests is mostly a placement problem. Add a clear link to your board in the places your plugin users visit:

• Your plugin documentation and support page.
• The welcome or settings screen of the plugin.
• The footer or header of your product site.
• Your replies to support tickets that are really feature requests.
• Release notes and emails, with a “Suggest a feature” link.

With Changeloger, you can add the board to any page using the shortcode

, or show it as a tab next to your releases using the Release Hub block. Embedding the board on another website with an iframe is a Pro feature.

Step 2: Make submitting easy

The Changeloger submit form asks for a title, a category and a rich-text description. That is enough. Keep the barrier low: users should not need a long form to tell you what they need. If you receive ideas by email or chat, an admin can add them manually from Changeloger, Feedback so they still appear on the board.

Step 3: Use categories to keep ideas organised

Out of the box, Changeloger groups feedback into Feature Requests, Bug Reports, Integrations and Languages. You can add, rename or remove categories to match your plugin. Good categories help users find an existing idea before they post a duplicate, and they help you see patterns, such as many integration requests or language requests.

Step 4: Let plugin users vote

Voting is the simplest way to rank requests. On Free, users can upvote, and they can sort the board by New, Top or Trending. In Pro, you can also enable downvoting for net scores, guest voting without an account, and comments on each item. See the WordPress upvote downvote plugin guide for how these options affect your data.

Step 5: Reply and update statuses

A request that never changes status feels ignored. Changeloger shows a coloured badge on each item: In Review, Planned, In Progress, Completed or Rejected. Update the status when you decide, and use the detail view to give context. Users who see a request move are more likely to post the next one.

What to ask users when they submit an idea

A good feature request explains the problem, not just the solution. Encourage users to describe what they were trying to do, why the current plugin made it hard, and how often it happens. Changeloger’s rich-text description field gives them room to add that detail without an extra form.

This context matters when you prioritise. “Add export” is vague. “I need to send settings to a client every month” tells you who the feature is for and how urgent it is.

Step 6: Turn the best ideas into a public roadmap

Once you have votes and statuses, you already have the raw material for a roadmap. In Changeloger, setting an item to Planned or In Progress adds it to the roadmap, and the Kanban roadmap board is a Pro feature. Our guide on building a user-driven roadmap explains the approach in more depth, and the post on building a professional feedback board in WordPress covers the board design.

Keep the feedback loop alive

Collecting requests is only half the job. The other half is closing the loop. Try this weekly routine:

1. Open the admin Feedback screen and check the In Review count.
2. Sort by Top to see the most upvoted ideas first.
3. Move clear winners to Planned and obvious misfits to Rejected.
4. Reply on items that need more detail.
5. When something ships, set it to Completed and mention it in your release notes.

The admin dashboard shows the total, In Review, In Progress and Completed counts at a glance, and each count is clickable to filter the list. That makes the routine quick enough to do every week.

Free plan limits to know about

The Free plugin includes a public feedback board, upvoting, categories, sorting, filters, status badges and the admin dashboard, with up to 20 feedback items per product. When you reach the limit, the submit button pauses and a prompt invites you to upgrade. Pro removes the limit and adds unlimited products, comments, guest voting and Google login. You can compare them on the Free vs Pro page.

Start collecting requests today

Install Changeloger from WordPress.org, create your product, and add the feedback shortcode to a page. Then share the link with your users. Within a short time, you will have a ranked list that shows what to build next.

Frequently asked questions