0

1

Assume I have two named branches default and stable.

A bug is reported by a customer so new case is created in Fogbugz (eg Case 123) and is assigned to a developer. The developer fixes the problem in stable and commits with a message "Case 123" so that the changeset is linked to Fogbugz. The developer resolves the case and assigns it to QA.

QA verifies the case has been fixed in stable and closes the case.

QA then merges stable INTO default

Question #1: Will the Kiln history show the case # in both branches? I would assume so because the commit message from stable will be merged into default.

Question #2: Will Case 123 indicate that this bug has been fixed in BOTH branches?

Question #3: Does this workflow make sense?

flag

1 Answer

1

Yes, the case # will be shown in any repository with that changeset. The case in FogBugz will also show that the associated changeset is in both repositories.

As far as I can tell, your workflow makes sense. It is very similar to what we do here at Fog Creek to develop Kiln and FogBugz.

link|flag

Your Answer

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