7

1

Is it possible to resolve a case using a commit message -- i.e. have Kiln do it for me when it sees a certain type of message?

Fog Creek Case FC1928776

flag
This would be a great way to tie FogBugz more tightly to Kiln, and could also be very powerful. There are potentially lots of things that could be done to a FogBugz case based on a commit, and I am sure lots of developers would rather live inside Kiln and touch real cases less, since it requires less mental switching. – cdeszaq Aug 12 2010 at 15:08
Completely agree with @cdeszaq. And I think it's not only great convenient feature (I mean tight integration with FogBugz in whole). I believe it has huge positive side effect - it forces to make more descriptive and accurate commit comments, especially for beginner programmers or even for programmers with great experience, but not really eloquent. – Anton Moiseev Aug 12 2010 at 19:31

3 Answers

3

You can add "BugzId:#" or "Case:#" to commit comment and you will have nice bidirectional link between the changeset and specified case. But it doesn't "resolve" the case in terms of FogBugz, you should do it explicitly.

See:

link|flag
1

The only way to do this that I am aware of is to have a commit hook that will look for specific things in a commit message and based on what it finds use the FogBugz API to modify related cases.

link|flag
We did this in our current revision control tool. We were hoping Kiln would have this built in already.. oh well. We would type ##1234 in our check-in message to automatically mark the Case fixed. I guess we would have to learn how to port this to Kiln too... – M. Esh Aug 17 2010 at 19:38
1

The bugtraq api can do that from your local commit into Mercurial. See my question at the Fogbugz exchange. I don't know of a plugin that does it ... yet.

More details about Bugtraq from the TortoiseSVN site. This has been ported to TortoiseHg.

link|flag

Your Answer

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