FeatureQuest documentation

Everything you need to set up your feedback board, public roadmap, and Pro features. New here? Start at the top; the whole plugin runs from one shortcode.

Getting started

  1. Install the free plugin from Plugins → Add New (search "FeatureQuest"), or get it from WordPress.org. For Pro, upload the zip via Plugins → Add New → Upload Plugin, then activate.
  2. Create a page and add the shortcode [featurequest].
  3. Visit Feature Requests → Settings to set your board title, sign-in mode, limits, moderation, and email notifications.

All data lives in your own WordPress database. Nothing is sent to any external service unless you enable the optional captcha.

The shortcode

Drop [featurequest] on any page or post to render the full board: submission, upvoting, search, sorting, and tabs. It works in the block editor, in Classic Editor, and inside every page builder that accepts shortcodes.

Shortcode options

Pass attributes for filtered or compact embeds, for example [featurequest title="Roadmap" tab="active" sort="trending" tabs="false"].

AttributeValuesWhat it does
titleany textOverrides the board heading.
tabactive, complete, mineWhich tab opens first.
sortpopular, recent, trendingDefault sort order.
tabstrue, falseShow or hide the tab bar (for a compact embed).

Sign-in modes

Choose how visitors take part under Feature Requests → Settings:

  • Account login (default): visitors register and log into a WordPress account. You can point the "Log In" and "Create Account" buttons at any custom URLs (for example a membership plugin's login page).
  • Email verification: visitors submit and vote with just their email and confirm via a link, no account required. Nothing is saved until the link is clicked, so unconfirmed submissions never clutter your board. Confirming sets a private 30-day identity so they can keep voting and managing their own requests. This mode needs your site to be able to send email.

Boards & settings

Run as many boards as you want (unlimited, even in the free version): one for features, one for bugs, one for ideas. Each board has its own subtitle, accent color, moderation toggle, pause switch, and per-user request limit. Manage them under Feature Requests in the admin, and point a shortcode at a specific board from its settings.

Roadmap

Add [featurequest_roadmap] to show a public roadmap: a timeline of milestones plus columns grouped by status (planned, in progress, shipped). Configure milestones and the layout on the roadmap item in the admin. Pro adds custom statuses and colors.

Voting & limits

  • One vote per user per request, enforced by a unique database key.
  • Optional IP Vote Guard: a secondary check comparing a salted, one-way hash of the voter's IP. Raw IP addresses are never stored.
  • Set a per-user request limit to cap how many open requests each person can have.

Moderation & spam

  • Turn on Moderate New Requests to hold submissions in a pending queue until you approve them.
  • Pin important requests to the top of every sort with one click from the admin request list.
  • Per-IP rate limiting is built in. Optionally enable a captcha (Cloudflare Turnstile, Google reCAPTCHA, or hCaptcha) with your own keys.
  • Duplicate detection surfaces similar requests before a user submits; the Vote Log flags IPs that voted from multiple accounts.

Emails

Get notified on every new submission, or as a daily or weekly digest. Requesters can be emailed when their request is marked complete. Under Settings → Email there is a "Send a Test Email" panel so you can preview both messages. Deliverability depends on your site being able to send mail (a transactional SMTP plugin is recommended).

Gutenberg block

Prefer the block editor? Insert the FeatureQuest block to place the board visually, with the same options as the shortcode in the block sidebar.

Pro features

Pro adds:

  • Kanban board , drag requests across stages. Shortcode [featurequest_kanban].
  • Custom statuses with your own colors, per board.
  • Comments & official replies, with moderation.
  • Quick polls , shortcode [featurequest_poll].
  • Per-status notifications with follow / subscribe.
  • Integrations: Slack, Discord, Trello, Asana, GitHub, Jira, Zapier, with status sync.
  • Importers: Canny, UserVoice, Nolt, and CSV.
  • Private / internal boards, image uploads, custom fields, front-end moderation, related requests, WooCommerce product feedback tab, analytics, and white-label.

Page builders

The shortcode and Gutenberg block work everywhere. Pro adds native drag-and-drop widgets for Elementor, Bricks, Beaver Builder, and Oxygen. No page builder is required, the shortcode works on its own.

Caching

FeatureQuest works with page caching out of the box. There is nothing to configure, on any caching plugin, CDN, or managed host.

The board page is identical for every visitor. Nothing about who is viewing it is written into the page, so there is nothing for a cache to get wrong. Once the page has loaded, the board quietly asks the site who you are and updates itself. That request is never cached.

This applies to both sign-in modes, including email verification, so your board page can stay fully cached, you do not need to add cache exclusions or bypass cookies, and a visitor who has signed in is never shown a cached page telling them to sign in again.

Multisite networks

FeatureQuest runs on WordPress multisite. Network activate it once and every sub-site gets its own boards, requests, settings, and data, kept separate from the rest of the network.

Each sub-site counts as one site against your license, so a network of five or fewer fits Studio and a larger one needs Agency. Development, staging, and local installs do not count toward your total.

Removing the plugin from a network is handled per site: each sub-site keeps or deletes its own data according to its own Delete Data setting.

A note on updates. Network activating is the smoothest option. If you instead activate FeatureQuest on individual sub-sites, updates need one extra step, because WordPress manages updates at the network level while the update check can only run on a site where the plugin is active. Open that sub-site, go to FeatureQuest → Account, and use the update button there. The update then appears in Network Admin as usual.

License & updates

The free version updates through WordPress.org. For Pro, enter your license key under Feature Requests → License to enable one-click automatic updates and support. Every Pro feature works immediately; the key governs updates and support, never the features themselves.

Deactivating a license on a site does not cancel your subscription. It releases that site so you can move the license somewhere else, which is what you want when changing host or domain. If you actually want to stop billing, cancel from your account page instead.

After a new version is released it can take up to 12 hours to appear, because WordPress caches update checks. To see it immediately, visit Dashboard → Updates in your admin, which forces a fresh check.

Developer hooks

Filter the notification emails in code. Each filter receives an array with subject and body keys plus the request post:

add_filter( 'fquest_admin_email', function ( $email, $post ) {
    $email['subject'] = 'New idea: ' . $post->post_title;
    return $email;
}, 10, 2 );

The requester email uses fquest_requester_email with the same shape.

FAQ

Do users need an account to vote?

By default yes, but you can switch to Email verification so visitors take part with just a confirmed email, no account required.

Where is the data stored?

Requests are a private custom post type and votes live in a dedicated table, both in your own database. Deleting the plugin removes its options, tables, scheduled events, and request posts.

How are duplicate votes prevented?

A unique database key allows one vote per user per request; the optional IP Vote Guard adds a salted-hash secondary check.

Back to FeatureQuest Still stuck? Contact us