Is it okay to open a discussion to explore a feature request idea?

[Jason Burnett]

Although I tend to sound like a grumpy old man, I honestly do have profound respect not only for Adobe Developers but also for the generous Adobe Users that offer support, answer questions, and provide feedback.

What I don't want to do is impede any of the hard work from either of these groups.

I have some ideas that I think would be great features. They are just ideas now and they are certainly not worthy of filling out a feature request. In fact, without any input, they may be terrible ideas and I am just missing something.

I would like to be able to bring up an idea for a feature and get input and feedback from other Adobe Users before compiling a final, well-thought-out feature request with built-in support from the people who contributed. I understand that there is some upvoting and group input in the feature request portion of the forum, but it would be nice to have that discussion beforehand. As a group discussion turned feature-request, it would hold more water.

My thought was that by unchecking the "Mark this discussion as a question" it would allow the Adobe Users providing support to filter these kinds of discussions from the ones where people needed help.

Is this an acceptable thing to do in these forums or is there a better way to collaborate on an idea before submitting it as a formal feature request?

[AxelMatt]

If you have a feature request please post it in the Feature Request/Bug Report Form.

There's still the possibility to discuss about your request.

[Abambo]

Your welcome to suggest what you want. However, some product have a uservoice channel and your suggestions would reach there the developers. Else you have as Axel suggests the wishform. But that‘s quite private.

[Nancy OShea]

Depending on the product, Adobe uses a 3rd party platform called  uservoice to log feature requests and rate them by popularity.  The more votes your idea gets from fellow users, the greater chance it has of getting added to a future release.

For example, this is for Spark

Community feature requests for Adobe Spark!

This is for Illustrator

Illustrator Feature Requests: Top (2512 ideas) – Adobe Illustrator Feedback

This is for Dreamweaver

Adobe Dreamweaver: Feature Ideas

But Photoshop uses a different feature request system.

Photoshop Family Customer Community

[Jason Burnett]

Thank you to everyone that responded. Unfortunately, I am afraid I wasn't clear in my request.

I have inadvertently submitted the same request twice because it seems like such an obvious suggestion but because there are 2100 requests, nobody actually reads numbers 300=2100 unless they are OCD or something.

I would like to discuss a fundamental change to Illustrator and provide a link to the feature request to encourage people to upvote it because it would make like so much easier for everyone. But right now, it's not getting any exposure so there's no real measurement of interest in it. That's a UserVoice problem but it's affecting the efficacy of submitting feature requests.

[Peru Bob]

x

nobody actually reads numbers 300=2100

By @Jason Burnett

All Uservoice requests are seen by at least one Adobe employee.

The number of upvotes is what brings it to the top of the list for consideration.  Adobe decision makers use metrics to determine a course of action.

Post your feature request on Uservoice and then post a link to it in a thread in the appropriate Adobe forum asking users to upvote it.

[kglad]

https://www.adobe.com/products/wishform.html