There are a number of different sources of information that we use when planning future versions of our tools, including, but not limited to, feedback gathered via pre-release programs, customer surveys, sync-dev meetings, product forums and in-person discussions at conferences, etc.
For Flash Builder, we also actively request that developers log bugs and feature requests using JIRA, which is hosted at bugs.adobe.com. We review all the feature enhancements that are logged and pay particular attention to those requests that have community support, by way of the number of votes received.
The current top 10 feature requests are listed below, with the full list visible here (note: you will need to login or create an account first as anonymous browsing is currently disabled).
If you have already logged a feature request or voted then thank you! If you haven’t and can spare half an hour, now would be a great time to review the list of requested features, vote for your favourites and add features that you’d like to see in Flash Builder.
Whilst we can’t guarantee to implement every feature request in the next version of the product, we do take the feedback you give us very seriously and it is all used to help shape the future direction of Flash Builder.
If you haven’t used bugs.adobe.com before then you’ll find a quick guide to getting started here.
Andrew Shorten's Blog 
The biggest problem with Flex Builder is it’s inability to work for large projects without build time being a major issue. Having a large code base in Flex Builder requires you to modulize your application in ways you wouldn’t normaly do just because the build process becomes extremely slow…
My question is if I can file this as a bug? Or whether this is more a feature request?
Andrew,
One of the glaring issues in Flex 3 is the mediocre/poor print support for content spanning multiple pages.
I’m not going to add it as an issue because I saw this reported in issue 13895 (from 2007), but I didn’t know whether it’s going to get addressed in FB4. I’ve been pulling my hair out trying to nice multipage print out, and in the end, have to punt–very frustrating. In my tests with PrintDataGrid, it virtually always crops content on variable sized rows, even using the examples in the documentation. I’ve been using BentBit to produce better results, but it still is all graphics and hence big print files. At least client-side native support into PDF would be nice (perhaps integrating work from AlivePDF).
I wonder about the number of bug submissions marked ‘Unresolved’ for the Flash Player. In the past year and a half, there have been 2,000 submissions, but more than 1,400 of them are still unresolved.
Interesting the most top 10 feature requests for FlashBuilder are already part of the current version of FDT from Powerflasher 😉
@espen – You could log \Support for large Flex projects\ as a feature request if you think we should be tracking that as a seperate item. If you do, it would be helpful if you can share some detail about the size, structure and complexity of the project you are working on. Thanks!
@jonathan – this is an issue which is related to the FlexSDK (rather than Flash Builder) and I believe that resolution is dependent upon getting improved support for printing within the Flash Player. Not sure of the status of that I’m afraid.
@marco – We receive a huge number of reported bugs/issues and it takes a significant amount of time to triage each and determine whether it is a bug, non-reproducable, a duplicate of another bug, etc. For most of the bugs coming in from the community, we rely upon others voting for reported issues, so as to bubble the most important ones to the top of the list, for many of the others they will continue to be listed as ‘unresolved’ because they have not been verified as actual bugs.
Pingback: Andrew Shorten @ Adobe » Please complete the Flex survey!
Pingback: Life As An Evangelist » Please complete the Flex survey!
Pingback: Flex Labs » Post Topic » Zukünftige Flash Builder Features