"What's needed is an intelligent engine for processing email"
They already exist; the normal name for such a thing is "secretary" =D
I don't know about the inductive logic behind your "humans can solve this problem, therefore it is solvable by a computer". To create an algorithm that could classify email as well as a human, you'd need to create an algorithm as advanced as a human.
Furthermore it would not help much.
You still would have to monitor the algorithm decisions.
Otherwise you loose control over your work.
Never ever I would allow an algorithm to decide what is a bug and what is a feature request.
Your argument changes the premise. The email problem persists because it is hard (or impossible) to solve by humans.
Solving the email problem, in so far as it depends upon classifying email, must classify email significantly better than a human. One of the things computers do better than humans is working tirelessly, and at its heart the email problem is Sisyphean.
Google serves personalized advertising. Facebook customizes your feed. Your grocery store prints coupons at checkout.
All without homunculi.
There is sufficient information in the text to determine that the email is for a feature request - otherwise the author wouldn't know it was one.
What's needed is an intelligent engine for processing email. Improving email is an AI problem not one which requires an email to contain more information.
One difficulty I see is that developing a system for intelligently processing email is not necessarily the sort of thing a startup can tackle - the required data set for testing and validation is too large for a small company to obtain naturally and test under real world conditions. It's the sort of problem that lends itself to an "eat your own dogfood" approach - and thus justifiable at an existing large company.
My gut tells me that outside the corporate world, this wants to be a desktop application, not a web based one. The intelligent engine needs to know about the files and documents on my computer to make better sense of the contents of a message - I don't want to have to share all that with a web service and I don't want to enter a bunch of metadata to create rules.
The software should know it's a bug report because I write a lot of code for the product, have other bug reports on my computer, and posted ten bug fixes to the code repository. not because I spent four days writing a CLIPS program to handle bug reports.
It's a nasty problem if one tries to just grep it into submission. The answer to the email problem is a poem, not an equation.