Chris Thornton
08-Apr-2008, 08:31 PM
The Mantis capability is nice, but too much information is lost. It IS nice
that the dates/counters increment, so I can see the "popular" bugs. But It
only captures the zip file, e-mail address, and platform from the first
user. I'd like to collect more of this stuff, and I'd REALLY like to avoid
logging anything for older releases - I'd prefer to just instruct them to
download the fix.
I'd like to write a "wedge" script in PHP to act as an interface between
EurekaLog and Mantis. This would allow me to have conditional processing,
such as:
If latest app version then
if new bug then
add the bug, but pulling relevant info from the report to make a
better title, log the call stack, other relevant info.
thank user for submitting.
else /* old bug */
Add some stuff to the report, such as end-user e-mail, add another
attachment (maybe conditionally), platform, etc..
Inform user that we'll notify them when it's fixed (because I added
their e-mail to the report!)
else
look up bug in database, see if there is a fix.
If there's a fix, invite the user to download the update.
else , invite them to update anyway!
If I can get documentation on how this works now, or what information is
available to a generic PHP script, I could write something like this.
(Then, all I need is TIME!!). I'd be happy to share it back to the EL
community, or work on it as a collaborative project.
--
Chris
that the dates/counters increment, so I can see the "popular" bugs. But It
only captures the zip file, e-mail address, and platform from the first
user. I'd like to collect more of this stuff, and I'd REALLY like to avoid
logging anything for older releases - I'd prefer to just instruct them to
download the fix.
I'd like to write a "wedge" script in PHP to act as an interface between
EurekaLog and Mantis. This would allow me to have conditional processing,
such as:
If latest app version then
if new bug then
add the bug, but pulling relevant info from the report to make a
better title, log the call stack, other relevant info.
thank user for submitting.
else /* old bug */
Add some stuff to the report, such as end-user e-mail, add another
attachment (maybe conditionally), platform, etc..
Inform user that we'll notify them when it's fixed (because I added
their e-mail to the report!)
else
look up bug in database, see if there is a fix.
If there's a fix, invite the user to download the update.
else , invite them to update anyway!
If I can get documentation on how this works now, or what information is
available to a generic PHP script, I could write something like this.
(Then, all I need is TIME!!). I'd be happy to share it back to the EL
community, or work on it as a collaborative project.
--
Chris