A forum for technical support discussion related to Fogbugz.
I posted this question a while back and I did not follow up on it. We are trying to have the ability to create a new case from our developers when they check in code not associated with an existing case. I understand that this falls a bit outside the normal way one should use FogBugz, I while I agree it is unfortunately the realities of the world I find myself stuck within,
Anyway a few responded that it was possible to do this with the API. I wonder if you could or would be willing to share any API code that would demonstrate how to do this (or anything similar)?
Thanks in advance!
I haven't done this, and therefore haven't got any code to share, but I think you should be able to do this quite easily.
In your post-commit trigger, call a script that does the following:
If commit description contains "BugzID:", call normal script for submitting to FogBugz as you already have 1 or more cases to submit against.
Otherwise, create an email body that contains the description and any other text you desire, and email it to FogBugz with an appropriate subject line (first line of commit description?) and from address (user or admin user maybe).
Although you'll be able to have the list of files changed in the body of the email, you won't be able to update the case with a proper list of committed files (unless you do some seriously funky stuff with catching new case notification emails on a server that scans the subject line for commit ids and then sends a cvsSubmit request to FogBugz for that commit and case number). Brittle.
In a UNIX/Linux environment this is pretty easy stuff, and I guess under Windows it isn't going to be too hard either.
Ian M. Jones (CaseDetective)
Monday, February 9, 2009
This topic is archived. No further replies will be accepted.Other recent topics