create and control Issues with email

Probably not possible now. There's some basically dead code in project_issue's mail.inc file to provide mailhandler integration, but no one that I know of has tried using it in at least the 3 years I've been involved. ;) You are more than welcome to try enabling mailhandler and project_issue on a test site, configuring mailhandler properly, and see what happens. Please report back here when you do. Thanks.

Note: I just ripped out the dead mailhandler code in the 7.x-2.x branch, since I'm sure it's broken there due to all the fields changing:

http://drupalcode.org/project/project_issue.git/commit/c463d26

If/when someone has time/motivation to actually test this and get it working again, we can either revert that commit, or better yet, just create a new commit with actually verified working code.

Just out of interest, would mailhandler ever get deployed to d.o or is that completely off the table?

It is possible, but I would want to take a look around the possibilities first. Is mailhandler still the best way to solve this? Is it well-maintained lately?

We have the possibility of using the RestWS API now, #1710850: Deploy RestWS for D7 project issue JSON. Either by testing it very well with issues and relying on 3rd party tools, like Drush; and/or setting up something not-necessarily-Drupal to receive email replies to issues and use the API to update issues. If we are running an email parser on Drupal.org servers, only the part of RestWS used needs to be tested, not everything.

Sometimes I'm thinking my client is the only one that needs to reply to issue via email. Looking at this thread it certainly looks like it is not a popular request.

Has anyone else receive a request like this?