Home › Forums › Feature Requests & Roadmap › How to request a feature (and how we decide what to build)

How to request a feature (and how we decide what to build)

We read every request here and use them to plan the roadmap, so the more specific, the better.

Describe the problem before the solution. "Add scatter charts" is a request. "We plot response time against satisfaction for 400 survey entries a month, and we export to Sheets to do it" is a problem we can design for, and it may lead somewhere better than the first idea.

Include:

  • Which plugin, or "a new one"
  • Your current workaround: custom code, another tool, manual work
  • How often you hit it, and at what volume (entries, forms, sites)
  • Whether it's for your own site or for client sites

One request per topic. That way others can add their use case to the right thread. A reply that describes your situation counts for more than "+1."

How we decide. We look at how many people hit the problem, whether it fits the plugin's job, and what it costs to build and maintain. When a request is planned, shipped, or declined, we'll say so in the thread, with the reason.

Signed-in members can also vote on the GravityOps roadmap.

<p>We read every request here and use them to plan the roadmap, so the more specific, the better.</p><p><strong>Describe the problem before the solution.</strong> "Add scatter charts" is a request. "We plot response time against satisfaction for 400 survey entries a month, and we export to Sheets to do it" is a problem we can design for, and it may lead somewhere better than the first idea.</p><p><strong>Include:</strong></p><ul><li>Which plugin, or "a new one"</li><li>Your current workaround: custom code, another tool, manual work</li><li>How often you hit it, and at what volume (entries, forms, sites)</li><li>Whether it's for your own site or for client sites</li></ul><p><strong>One request per topic.</strong> That way others can add their use case to the right thread. A reply that describes your situation counts for more than "+1."</p><p><strong>How we decide.</strong> We look at how many people hit the problem, whether it fits the plugin's job, and what it costs to build and maintain. When a request is planned, shipped, or declined, we'll say so in the thread, with the reason.</p><p>Signed-in members can also vote on the <a href="https://brightleafdigital.io/dashboard/membersroadmap/">GravityOps roadmap</a>.</p>

Leave a Reply

This topic is locked. No more replies are allowed.

Log in or create an account to reply.