It was a word doc that support emailed me to fill out on a previous issue. You can also get the gist of what they need by looking at the RFE doc in the Support Policy section of supportweb.
-----Original Message----- From: Action Request System discussion list(ARSList) [mailto:[email protected]] On Behalf Of Joe Martin D'Souza Sent: Thursday, April 28, 2011 2:28 PM To: [email protected] Subject: Re: RFE (No Plans to Implement) From the sales perspective, I guess an RFE with the biggest 'wow factor'... From where did you get that RFE form? Joe -----Original Message----- From: Grooms, Frederick W Sent: Thursday, April 28, 2011 3:19 PM Newsgroups: public.remedy.arsystem.general To: [email protected] Subject: Re: RANT: RFE (No Plans to Implement) I'm not as bothered about how an RFE is created. A short while back I opened a ticket with BMC. The ticket was simply "Please create an RFE for me. Attached is a completed RFE form" (I had taken an earlier RFE form and changed it up to how I wanted this RFE to be). Later I received an email from support stating "We have created your RFE #### as requested." (along with the usual follow-ups of is there anything else needed and such). Like Guillaume, Andrew, and Danny (and probably the rest or you too) I wonder how demand for an RFE is determined. That is the part of the process I believe could use improvement. Fred -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:[email protected]] On Behalf Of Joe Martin D'Souza Sent: Thursday, April 28, 2011 1:34 PM To: [email protected] Subject: RANT: RFE (No Plans to Implement) I feel that way too.. I do see why they took away that ability when support once explained it to me. Apparently when it was available for the rest of us to submit RFE's, they would get a number of unreasonable requests that would be disqualified as a reasonable RFE right off the bat.. I feel it might have probably been a better idea if they had to limit where those RFE's that are submitted online came from. Users of the support web that had a particular group membership should still have had the ability to submit as they were less likely to submit something that would be disqualified as an RFE right off the bat.. These would be users who may have completed some sort of recognized training such as RAC or RSP to automatically be a part of that group assuming that BMC Software maintains a database of those who have completed such training.. Also good candidates would be those who may have not done that training but have been working with Remedy applications as developers or consultants for several years.. Restricting RFE's to be submitted just on the the strength of issues that are raised as is the current practice, BMC is automatically eliminating the possibility of RFE's coming from non-issues. Such as a 'flash of genius'... A new idea could well be born from just that - an idea.. There doesn't have to be a limitation or an issue for an idea to be born.. And right now thats pretty much how I see new RFE's are raised.. Joe -----Original Message----- From: Danny Kellett Sent: Thursday, April 28, 2011 2:02 PM Newsgroups: public.remedy.arsystem.general To: [email protected] Subject: Re: RFE (No Plans to Implement) David, The one massive short fall I always see with BMC is that the current list of RFEs are not easily visible. So lets take this example. We could have all thought this was a great idea and thus you would have got your "High Demand" value. Kind regards Danny Single Sign On (SSO) for BMC Remedy AR System and ITSM http://www.javasystemsolutions.com/jss/ssoplugin -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:[email protected]] On Behalf Of Easter, David Sent: 28 April 2011 18:58 To: [email protected] Subject: Re: RFE (No Plans to Implement) The phrasing is, admittedly, a little confusing - but the general message being conveyed is that the RFE was put in several releases ago and the RFE has been considered but deferred several times. If an RFE is considered and deferred multiple times, it is an indication that the enhancement request isn't going to be of high enough demand or priority to justify implementation. Rather than just leave the RFE in a nebulous state, BMC feels it appropriate to be honest with customers and just close the RFE with "No plans to implement" - because there are no plans to implement it. -David J. Easter Manager of Product Management, Remedy Platform BMC Software, Inc. The opinions, statements, and/or suggested courses of action expressed in this E-mail do not necessarily reflect those of BMC Software, Inc. My voluntary participation in this forum is not intended to convey a role as a spokesperson, liaison or public relations representative for BMC Software, Inc. -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:[email protected]] On Behalf Of Terje Moglestue Sent: Thursday, April 28, 2011 02:16 AM To: [email protected] Subject: Re: RFE (No Plans to Implement) It sounds like - if you wait long enough - you can close the ticket! Or - they think it is just like cheese - it's getter better with time - until it is out of date! ~ Terje ________________________________________ From: Action Request System discussion list(ARSList) [[email protected]] On Behalf Of Jarl Grneng [[email protected]] Sent: 27 April 2011 19:40 To: [email protected] Subject: RFE (No Plans to Implement) This one is a new one.... "Our RFE Review Committee has re-reviewed this RFE and, unfortunately, decided to reject this RFE due to the fact the version this RFE was filed on is no longer supported." -- J
