UX standards - ‘SUBMIT FEATURE REQUEST’ affordance fails to enable user to do so

[anonyms]

Currently in Ru, there is no clear way to provide 'feedback' let alone a suggestion or bug report to Adobe.

Problem description:

User wants to submit feedback, looks for some easy quick way of reporting, scans the screen for an affordance, discovers icon at top that displays a "Submit Feature Request". Decides to use this to attempt to communicate with Adobe. User is sent through the login and Multifactor process, is brought to discussion board feature. Immediately, is baffled since DISCUSSION ≠ "Feedback".

Suggestion AND FEEDBACK:

Make sure your signifiers truly signify. Again, the the word "feedback" does NOT mean "discussion". Use the correct English word for correct signification.

Recommendations: Review the essential UX heuristics ALL developers and designers use in assuring high rates of usability (see platform standards published by Google, Apple, AND ADOBE ITSELF! ...and USE THEM).

Assuming 80% of users (the standard used) will be able to take this essentially 'slang' term for reporting a personal use experience and understand it as inclusive of other capabilities is not recommended not to mention making localization more difficult as well.

Justifying the design with a 'nobody has complained' is one of the common features of amateur and problematic UX design. 

Please take the time to utilize the aforementiined UX standards in designing your UI ...maybe beginning with this feature

[ElizabethOOOG]

I've definitely complained. Rush is a good beginners learning tool. I'm going to have to move on because it's too unstable. There's too many releases. Too much TAC to read between releases. It's BARELY a service. Not an app.

[Kevin-Monahan]

HI @anonyms,

Thanks for writing about your concern about Rush's UX/UI. Unfortunately, these are user-to-user forums without much input from the product team. As a support person, I apologize for this. I will let the developers know about your request, though.

Rush, the app, used to link to User Voice (a separate set of forums designed for bug reporting), where feature requests and bugs were logged and tabulated. The User Voice component was linked to the  "Submit Feature Request" UI, but the team removed that function around a year ago, along with the other Adobe digital video applications. For Rush, the feedback function was linked to these Discussion forums instead.

Bug reports and feature requests have migrated to Adobe forums for other digital video and audio applications, save for Rush (See Premiere Pro's Bugs and Ideas forums, for example). I do not know the product team's reason for not migrating User Voice forums here.

I agree that providing Rush feedback is a less-than-satisfactory experience that needs addressing. As a stopgap measure, I manually label feature requests and internally report bugs to the team. My recent efforts in this regard have had some success in ensuring significant bugs are fixed and feature requests can be tabulated.

I will send a link to this discussion to internal communications so the devs can read your post. I appreciate you taking the time to write about this issue.

Thanks,
Kevin

[anonyms]

The least they might do is to change the label of the affordance to match what it is doing… which is obviously and most definitely NOT taking the user to anything remotely related to the act of providing ‘feedback’ …or even just taking the affordance away altogether vs. misleading users.

[Kevin-Monahan]

Hi @anonyms,

I agree with you, and I have let them know. I appreciate your concern about this.

Thanks,
Kevin