New on the blog: why AI belongs in the feed →

Run a Feature-Request Board for Your Plugin on WordPress

If you make a WordPress plugin or a SaaS product and your site already runs Gravity Forms, you can run your feature-request board on it: users suggest and discuss features, +1 the ones they want, and see what is planned and what has shipped. It takes four parts, each doing one job. Ours runs on this site, so every piece below is live.

The four parts

  • Discussion: GravityOps Forum. Each request is a topic, each comment a reply, and both are Gravity Forms entries. Tag topics by plugin and the forum filters by tag. Ours: Feature Requests & Roadmap.
  • Status: Kanban View for GravityView. A request form whose Status field drives the columns: Received, Planned, In progress, Shipped, Not now. Ours: the GravityOps roadmap.
  • Demand: a +1 form. Forum has no voting or reactions (we checked its code before writing this), so the count lives in a small Gravity Forms form. One entry is one +1.
  • Totals: GravityOps Charts. Charts drawn from the entries of the request form and the +1 form, so the numbers are always current.

Try the +1 tally

Northwind is an invented plugin maker and the numbers below are sample data. Add a +1 and it shows in the chart on the next page load.

Only used to tell you when it ships.

+1s per request (sample data)

+1s by plugin (sample data)

Requests by plugin, from our real roadmap

This one counts every request sent through the form on our roadmap page, approved or not. Only the plugin name is counted; the request text stays private until we approve it.

GravityOps feature requests by plugin

Set it up

1. The discussion forum

In Forum, add a forum called Feature requests. Build a topic form with a title field, a content field and a Plugin dropdown, then assign it as the Topic Form: map Title Field, Content Field, and the Plugin dropdown to Tags Field so every topic carries its plugin as a tag. Assign a reply form with a Content Field. Use the Access tab to decide who can view, post and reply. Moderators can lock, sticky, edit and delete topics. On Forum Premium, logged-in members can follow a topic or a whole forum; to email them, add a notification to the reply form with in Send To, and use and Click here to see the new post in the message.

2. The roadmap board

Make a request form: Plugin (dropdown), What should it do? (one line, it becomes the card title), Why it matters (paragraph), optional name and email, reCAPTCHA, and a Status dropdown with Received selected by default and visibility set to Administrative. Create a GravityView View on that form with the Kanban layout and the Status field as the columns. Turn on Show only approved entries, so a new request stays off the public board until you approve it in the entries list.

3. The +1 form

A Plugin dropdown, a Request dropdown listing the requests you have accepted, an optional email so you can tell people when it ships, and reCAPTCHA. Add a choice to the Request dropdown when you move a request to Planned. A +1 form counts submissions, not people; if double counting matters, require login in the form settings and glance at the entries now and then.

4. The charts

Swap in your form and field IDs. With only x_axis or section set, Charts counts entries per choice. access=”public” shows a chart to logged-out visitors; the default is private.

[gravityops_chart form_id="119" chart_type="horizontal_bar" x_axis="2" title="+1s per request" y_label="+1s" access="public"]
[gravityops_chart form_id="119" chart_type="donut" section="1" title="+1s by plugin" access="public"]
[gravityops_chart form_id="112" chart_type="horizontal_bar" x_axis="1" title="Requests by plugin" y_label="Requests" access="public"]

5. Close the loop

When you ship, drag the card to Shipped, reply in the forum topic with the release, and lock the topic if the discussion is done. With the follower notification from step 1, everyone following the topic gets the reply by email.

What it uses

Forum, Kanban View for GravityView (needs GravityView) and Charts, all on Gravity Forms. All three are in the GravityOps bundle. Building one of these for a client? The Kanban board templates and chart examples have more to copy.