{"id":2377,"date":"2014-05-17T10:38:42","date_gmt":"2014-05-17T14:38:42","guid":{"rendered":"http:\/\/antipaucity.com\/?p=2377"},"modified":"2014-05-17T10:38:42","modified_gmt":"2014-05-17T14:38:42","slug":"a-public-or-white-labelable-rfe-service-a-la-uservoice-but-easier-to-use","status":"publish","type":"post","link":"https:\/\/merikebi.warrenmyers.com\/?p=2377","title":{"rendered":"a public &#8211; or white-labelable &#8211; rfe service a la uservoice, but easier to use"},"content":{"rendered":"<p>I&#8217;ve seen some services that utilize <a href=\"uservoice.com\">uservoice<\/a>\u00a0to handle requests for features, functionality, etc.<\/p>\n<p>And I have seen companies have formal Request For Enhancement \/ Enhancement Request \/ etc processes (generally culminating from support <a href=\"http:\/\/cnx.org\/content\/m40795\/latest\/?collection=col11350\/latest\">cases<\/a>\u00a0(hopefully from good ones)).<\/p>\n<p>What I don&#8217;t see, though, is a way to either limit who can submit requests (uservoice, for example, allows anyone to register and submit ideas to different groups, so far as I can tell), or focus requestors into contributing \/ voting-for \/ etc previous RFEs (the way the <a href=\"http:\/\/stackexchange.com\">SE<\/a> family tries to prevent duplicate questions).<\/p>\n<p>Corporate RFE systems\u00a0<em>tend<\/em> to be completely blind from a requestor\/submitter viewpoint to see whether something similar (or identical) has already been asked for.<\/p>\n<p>The wide-open option uservoice provides has its own pitfalls: finding previously-asked items is hard (unless they&#8217;re already highly voted); getting a previously-refused request reconsidered is difficult (or impossible); the interface is less than desirable.<\/p>\n<p>There needs to be a consistent RFE tool made and used so that filing RFEs for a VMware product becomes more-or-less identical to filing one for WebSphere, or Chef, or AutoZone, or Amazon, etc.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>I&#8217;ve seen some services that utilize uservoice\u00a0to handle requests for features, functionality, etc. And I have seen companies have formal Request For Enhancement \/ Enhancement Request \/ etc processes (generally culminating from support cases\u00a0(hopefully from good ones)). What I don&#8217;t see, though, is a way to either limit who can submit requests (uservoice, for example, &hellip;<br \/><a href=\"https:\/\/merikebi.warrenmyers.com\/?p=2377\" class=\"more-link pen_button pen_element_default pen_icon_arrow_double\">Continue reading <span class=\"screen-reader-text\">a public &#8211; or white-labelable &#8211; rfe service a la uservoice, but easier to use<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_jetpack_newsletter_access":"","_jetpack_dont_email_post_to_subs":false,"_jetpack_newsletter_tier_id":0,"_jetpack_memberships_contains_paywalled_content":false,"_jetpack_hide_featured_image":false,"_jetpack_featured_image_duplicate_dismissed":0,"_jetpack_feature_clip_id":0,"_jetpack_memberships_contains_paid_content":false,"footnotes":"","jetpack_post_was_ever_published":false},"categories":[22,41],"tags":[636,675],"keyring_services":[],"class_list":["post-2377","post","type-post","status-publish","format-standard","hentry","category-ideas","category-technical","tag-rfe","tag-service"],"jetpack_sharing_enabled":true,"jetpack_featured_media_url":"","_links":{"self":[{"href":"https:\/\/merikebi.warrenmyers.com\/index.php?rest_route=\/wp\/v2\/posts\/2377","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/merikebi.warrenmyers.com\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/merikebi.warrenmyers.com\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/merikebi.warrenmyers.com\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/merikebi.warrenmyers.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=2377"}],"version-history":[{"count":0,"href":"https:\/\/merikebi.warrenmyers.com\/index.php?rest_route=\/wp\/v2\/posts\/2377\/revisions"}],"wp:attachment":[{"href":"https:\/\/merikebi.warrenmyers.com\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=2377"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/merikebi.warrenmyers.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=2377"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/merikebi.warrenmyers.com\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=2377"},{"taxonomy":"keyring_services","embeddable":true,"href":"https:\/\/merikebi.warrenmyers.com\/index.php?rest_route=%2Fwp%2Fv2%2Fkeyring_services&post=2377"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}