I have written an application, something completely separate from Drupal. When it fails, it sends me an e-mail with the details. I'd rather have it automatically create an issue to be tracked in Drupal. I can't seem to find a way to this, though it seems a rather obvious thing to want to do. Is there a single form that you can fill out to populate an 'issue node'?
I don't use BugZilla, Mantis, FogBugz or systems like that, but the concept is the same. Application fails, so it logs onto a web page and fills in the details, attaches a file perhaps, and then you have a record. Should use some authentication and it needs to populate at least a few fields in order to categorize by project, issue type and so forth.
Adoption of such a feature would likely be expedited if its interface was 'compatible' with one of the above systems.
(If anyone cares this is for a TurboDelphi app using EurekaLog to handle the exceptions, which interfaces to the above systems fine)
With the project/issues modules so software-centric, this would seem to be an easy thing to implement. Suggestions on where to go?
The same approach could also be useful for handling SNMP data and things like that - just a way to get issues into the system non-interactively. And using a direct insert into the database is likely a non-starter for many reasons.
Thanks!
Comments
Comment #1
ChrisKennedy commentedSee http://drupal.org/project/mailhandler
Comment #2
hunmonk commentedadding mailhandler support is in our long-term plans, but won't happen anytime soon.
in the short term, you might want to check out leveraging http://drupal.org/project/drush -- there's probably a way to use it to submit issues programatically.
Comment #3
dwwproject_issue already implements the mailhandler hooks. i just don't know if anyone's tried it in the last 2 years or so. ;)