User Voice Endless Loop

Ask general questions here.
Posts: 93
Joined: Wed Sep 19, 2018 10:05 am

User Voice Endless Loop

Post by HansSchl » Mon Nov 09, 2020 2:16 pm

Hello Ranorex!

Some time ago, I asked a question in a forum and received the reply that what I wanted to do was not possible, but I should post a feature request in User Voice. So I did, and received an automated reply:
Thanks for the great recommendation.
We are going to be phasing out User Voice.

Please contact support by filling out the form here:
They will log your request and keep you updated on progress.
So I filled in the contact form (which was quite a struggle) and submitted my suggestion. This was the reply:
Thank you for contacting Ranorex Support.
We get many great ideas like yours, and for that we have our special User Voice section

If you could submit your suggestion there, we would appreciate it and make improvements based on them.
Now what? I'm caught in this User voice/Support loop, and the final outcome was this:
Your support ticket 00064490 has been idle for more than 7 days. It will be closed because there has been no additional activity on it. Please let us know if you are still having issues related to this ticket.
I take this as "keep your ideas to yourself", or am I wrong?


User avatar
Ranorex Guru
Ranorex Guru
Posts: 6545
Joined: Mon Aug 13, 2012 9:54 am
Location: Zilina, Slovakia

Re: User Voice Endless Loop

Post by odklizec » Mon Nov 09, 2020 3:02 pm


As far as I know, all suggestions and feature requests are always checked by Ranorex team, but you should not expect them implemented. As you can find on User Voice platform, many of highly voted requests were already implemented. Sadly, many low voted, but often pretty useful suggestions, were not always recognized and appreciated by Ranorex users or Ranorex team. So yes, making a feature request is like making a bet ;)

Sa for idling ticket, well, it’s a shame nobody answered your ticket yet. Try to resend your request.
Pavel Kudrys
Ranorex explorer at Descartes Systems

Please add these details to your questions:
  • Ranorex Snapshot. Learn how to create one >here<
  • Ranorex xPath of problematic element(s)
  • Ranorex version
  • OS version
  • HW configuration