2

1

Okay so I think there should be a point of reference on how to cross-link / associate / relate cases to and from each other within FogBugz, Kiln, the Wiki, Discussions etc...

Because linking Cases in FogBugz and Kiln is awesome.

The Basics:

http://kiln.stackexchange.com/questions/491

review 123
case 123
bug 123

http://fogbugz.stackexchange.com/questions/4405 & http://fogbugz.stackexchange.com/questions/4417

BugzID: 1234

Assuming these works too?

Review: 123
Case: 123
Bug: 123

How bout plural?

Cases 123
Bugs 123

Advance stuff:

http://kiln.stackexchange.com/questions/1320/

If you haven't made a commit yet, simply mention the case in the commit message. For example, "Fixes case 123", "bugzid: 123", "Solves some bugs (bug ids 123, 456, and 789)" all work just fine, and will cause bidirectional linking.

bug ids 123, 456, 789

I tried to make this clear, but apparently I failed. You need the word "case", "bug", "bug id", "bugz id", or "review" in front of the case number. All of the examples above follow that. The only pseudoexception is that, if enumerating multiple cases, you only need to have the word appear in front of the first. Thus, "Fixes cases 123 and 456" will work, but "Fixes 123 and 456" will fail.

cases 123 and 456

...but not

Case 123 & 456

How about...

BugzId: 123 456 789    
Cases 123, 456, 789

Sadly some of the advance linking only works from Kiln to FogBugz but doesn't work from within FogBugz itself.

The point is, I'm not sure which does work, and which doesn't work... the fact that you can say:

Case #blah #blah

and have it show up auto-magically in FogBugz under "See also" related cases field is awesome and amazing. (should be easy to unlink though)

I just think it should work the same way throughout FogBugz & Kiln, or at least have a definitive reference for all the syntax in the docs somewhere.


Editted:

Ben Pollack was nice enough to release the RegExp for Kiln here:

\b(?<case>(review|case|bug[zs]?(\s| )*(id)?:?)s?(\s| )*([#:; ]| )+)((([ ,:;#]|and)*)(?<bugid>\d+))+
flag

1 Answer

0

There is one catch! It does not LOCALIZE gracefully. We're a Brazilian team and our checkins are in Portuguese. It sounds very strange to have to use an English term in the middle of the commit message or case's text just to link.

I think that you could have used a "language" agnostic sintax in addition to the "natural" sintax. @BUG_ID, #BUG_ID, or something similar should immediately create the references to cases. This would work in any language and would not look strange in a comment like this:

"Esta mudança resolve os problemas reportados no caso 999999 (bug 999999)"

I'm required to add the "bug", "case", "review" English words to the message... If a "simple" link method existed I could write:

"Esta mudança resolve os problemas reportados no caso #999999"
link|flag

Your Answer

Not the answer you're looking for? Browse other questions tagged or ask your own question.