0

Hello, We are using a FogBugz plugin to develop a code review report. Thanks to the feedback in another question, we've made great progress. But now we're getting an odd behavior in that our report sometimes includes the link to the file/line number of the attached lines, but other times this box is missing. When it does appear, it's the green box that is drawn using the RenderHTML() function. But it seems to only draw these little boxes in the first case of our report, and not in subsequent cases.

So, rather than using RenderHTML, I'd like to write our own section for attached lines, and include the filename and the start/end line numbers...but I can't figure out where that information is stored in the database.

Can you point me to the table that contains this info?

Thanks, Mike

flag
Rather than re-implementing so much of the way Kiln renders bug events, could you tell us what kind of report you're trying to generate? It might be something we could fold directly into Kiln. – db♦ May 27 2011 at 14:58
What we are trying to accomplish is to create a report that contains all of the Kiln code reviews that have taken place during a sprint. In this report we would like to have a "structured" listing of Issue->Resolution for each issue raised during each review. This sort of view is available from within the Kiln review screen (in the left hand pane). Then, for issues which have attached lines, I would like to print out the identifiers associated with those lines, specifically the file name and line numbers (with the understanding that line numbers change over the life of the file). – Mike Hedman Jun 10 at 21:04
That attached lines info is available, as it's encoded in the links provided in the left hand frame of the Kiln review screen. Our reports have to be textual, thus, I need to transfer the encoded link info into human readable text. That's my goal - and if this could be folded directly into Kiln...I vote YES!!! – Mike Hedman Jun 10 at 21:06

Your Answer

Browse other questions tagged or ask your own question.