The only place that I am aware of was the Features & Proposals section of the official wiki.
The challenge we have in general with feature requests is that a good place to ask assumes that there is some chance of developers reading and implementing it (or at least replying to the request).
However, developers get asked for features a lot (personal emails, on blender-chat, mailing lists, on social networks even!) — so chances are, you are not even the first person to ask for it.
The ratio of people asking questions to those who can implement them is so high that its difficult to usefully manage requests.
Especially since Blender is general purpose 3D software, there are so many things you might want to do, depending on your project.
Taking this into account, here are some suggestions:
If nothing turns up:
- Ask on rightclickselect.com
(community run web site, currently in development)
- Find the developer who works on this are and mail them personally, see Module Owners
- You could look into funding the feature, Either by hiring a developer directly or contact the blender institute.
There are some bigger picture topics (adding ~9 years after the this initial post). While not directly related to the question are worth being aware of.
- Often, a single feature request is not enough information for a developer to implement a feature, there are many assumptions by the person asking the questions and surrounding context for the question that isn't part of the request. Some time often needs to be spent going back and fourth - to iron this out.
- Often time needs to be spent evaluating why existing solutions are insufficient, sometimes the person asking the question isn't aware of those solutions and the result of the request is to point to user to the documentation (or improve the documentation / UI for features that aren't clearly exposed).
Regarding the whole topic of feature requests, my impression is people who push for an official site to handle feature-requests hold the assumption that the feature-requests are a bottleneck - if only developers could be contacted and prodded in the "right" direction, the software would improve at a greater pace (in some instances this may be true, yet there is more to it...). I would argue the amount of communication involved in properly handling and responding to requests risks slowing down development - or require employing people to handle such a system that might be better put elsewhere, as with many things though - a balance needs to be struck.
At the time of writing Blender has a studio where artists and developers communicate and developers work on solving artists problems. Understandably this isn't satisfying when developers are not solving your problems, yet - focus is important too, and trying to solve every ones problems at once isn't practical.
Design & contributions are not limited to employees either, there are community members who have an important role in module teams, helping developers make decisions and giving feedback. Again though, the number of people in these roles is limited.
This is not to suggest the current setup is perfect, just that from the perspective of someone working on software - attempting to handle user feedback has tradeoffs. At the end of the day, spending a lot of time communicating about a change that we might not even have time to implement isn't a great use of time. I hope this helps gives some context and keep in mind I'm writing this based on my own experience. Developers who have worked in different areas of the same software will have varying experiences and opinions on how they view user-feedback and the level of community engagement they find works well for them.
See also: handing feature requests discussion on devtalk
If you can put your money where your mouth is, then BlenderNetwork is where you will find people willing and able to commit time and knowledge for addon development or additions to the core. If you go this route then making changes available to the public has the advantage that anyone can help bug-fix and improve such development efforts. Maintaining your own build might not be an option, without paying for long-term support.
Else you are left to the mercy of fellow blender heads to see the merit of your feature request, to the extent that they are willing to commit their own time to making it happen or help you some part of the way. A curated feature request daughter site of SE would be interesting, but don't underestimate the power of BlenderArtists, BlenderStorm, and Twitter hashtags
Requests on the wiki
It's a good idea to hunt through the current collection of feature requests, you might find yours is already on this list. If it's close enough to what you want then consider updating it or make a new one (but explain why the existing one is different).
Presentation and content of feature request
First impressions matter. The presentation and content of the proposal / feature request are going to be deal breakers. A good proposal has several key properties, and includes:
- An unambiguous definition of the request,
- A well written use-case for the request,
- A list of well-reasoned arguments identifying why current methods are not sufficient
- Isn't too ambitious as to require a platoon of coders to implement.
I don't know how important it is to have prominent donating users undersign the proposal, if ideas are good/useful and simple to implement the chances of success does increase.
There's a new 3rd party site designed for this purpose:
The site itself seems to be still very much in development, but it's likely the most active place for feature requests at this time.
I'm not sure how many of these requests are actually acknowledged, but I know that BlenderStorm is one place to request them.
Also, if you can get featured on BlenderNation for some reason (i.e. creating a funny short animation requesting the feature), that's another way.
If you would like to know what features are being added, check out BlenderGuru's "Is it in Blender Yet" list, or chat with the developers on Blenders Developer IRC channel (go to channel #blendercoders).