RSS Feed

FogBugz Technical Support

I just finished writing some scripts to have our git commits (via GitHub's web hooks) sent to our FogBugz server.  Everything seems to work just fine, but FogBugz doesn't display the git sha1's very nicely.  In fact, it's pretty hard to tell what's going on when you pull up the commit list.

See a screenshot here:
http://skitch.com/johnreilly/kr6x/fogbugz-3083-test-bug

I've got two suggestions...

1) If the 'R2' value is greater than X chars, truncate it and add an ellipsis. This is probably easiest, and would help, but still isn't exactly ideal.

2) Change the commit list to show each R2 on a new line, using indented <ul>'s or something.  Example:

<p>File1.ext</p>
<ul>
<li>rev1</li>
<li>rev2</li>
</ul>
<p>File2.ext</p>
<ul>
<li>rev1</li>
</ul>

That would probably look fine for git, but is probably too tall for "normal" SCM systems :)

I'd be curious to hear other's thoughts.

-John

Yeah, that's kinda ugly.  I think the design assumed that revision numbers would be integers, not big hex codes like that. 

I've opened a case and we'll take a look at doing something about that in a future version.

Thanks Eric. :)

Hi John-
Also, we'd love to have the commit scripts if you don't mind sending them -- that way we can include them in a future FogBugz version.
Thanks!
Brett

Johns work is located here

http://github.com/johnreilly

I posted a link to this on the blog.