Skip to main content

Feature Requests & Roadmap

Convert feedback into feature requests and build a public roadmap. Show your community that you're listening and prioritizing based on their input.

What Are Feature Requests?

Feature requests are feedback converted into actionable items. They appear on your public roadmap and community members can upvote them to help you prioritize.

Example:

Feedback: "The export feature only supports CSV. Adding JSON export would be helpful for developers."

Feature Request: "Add JSON export support"

Converting Feedback to Feature Requests

Step 1: Find Feedback

Go to your product page and click the "Feedback" tab.

Step 2: Select Feedback

Find feedback you want to convert into a feature request.

Step 3: Convert

Click "Convert to Feature Request" on the feedback.

Step 4: Edit

Edit the title and description:

  • Title: "Add JSON export support"
  • Description: "Support JSON format in addition to CSV for data export. This would help developers integrate with their tools."

Step 5: Create

Click "Create" and the feature request is added to your roadmap.

Public Roadmap

Your roadmap is public. Community members can:

  • View all feature requests — See what you're working on
  • Upvote requests — Vote for features they want
  • Comment — Discuss implementation details
  • Track progress — See which features are in progress or completed

Roadmap Statuses

  • Planned — You've decided to build this
  • In Progress — You're currently working on it
  • Completed — You've shipped it
  • Declined — You've decided not to build it

Updating Status

Update feature request status as you work on them:

  1. Go to your roadmap
  2. Click on a feature request
  3. Change the status
  4. Community members are notified of updates

Linking Updates to Feature Requests

When you ship a feature, link it to the original feature request:

  1. Publish an update
  2. Click "Link to Feature Request"
  3. Select the feature request
  4. The update appears on the feature request page

Example:

Feature Request: "Add JSON export support" Update: "JSON export is now available. Go to Settings → Export to choose your format."

Community members see that their request was implemented.

Roadmap Best Practices

Be Transparent

Show your community what you're working on. This builds trust and engagement.

Prioritize Based on Feedback

Feature requests with more upvotes should be prioritized. Show that you're listening.

Update Regularly

When you ship features, update the roadmap. Show progress.

Communicate Decisions

If you decline a feature request, explain why. Community members appreciate transparency.

Link feedback to feature requests, and feature requests to updates. Create a clear feedback loop.

Roadmap Analytics

Your workspace shows:

  • Total feature requests — How many you have
  • Upvotes — Which features are most wanted
  • Completion rate — How many you've shipped
  • Community engagement — Comments and discussions

Frequently Asked Questions

Can I delete a feature request?

Yes, but it's not recommended. Deleting a feature request removes it from your roadmap and community members lose visibility.

Can I make my roadmap private?

No. Roadmaps are always public. This is part of the transparency that builds trust.

Can community members create feature requests?

No. Only you can create feature requests. Community members can upvote existing ones.

How do I prioritize feature requests?

Consider:

  • Upvotes — What does the community want?
  • Impact — How many users will benefit?
  • Effort — How much work is required?
  • Strategic fit — Does it align with your vision?

Can I reorder feature requests?

Yes. Drag and drop to reorder them on your roadmap.

How do I communicate delays?

Update the status and add a comment explaining the delay. Community members appreciate transparency.