1

Say you have software "abra kadabra" that has been released in version 3.3, 3.4 and 3.5. A tester finds a bug in version 3.4.

How would the tester enter the case in FogBugz and:

  • Keep the knowledge that the bug was found in 3.4
  • Capture the decision to fix the bug in 3.3 and 3.4. But not in 3.5, where its not applicable.
flag

1 Answer

2

We use one of the extra fields, Version, to record the version number for any reported issue. In this situation the issue would be reported with 3.4 in the Version field.

Once the decision was made to resolve the issue, it would be assigned to a developer to be fixed with a Milestone of 3.4.x. Another FB case would be created (and tied to the original case) with a milestone of 3.3.x. Having a separate FB case for each fix let's them be tracked through the rest of the process (including QA) where they may need to be treated differently (one could pass QA, the other not, etc.).

link|flag
What does it mean to tie a bug to another bug. Would it be a subcase of the original case? – Kim Lokøy Nov 5 2009 at 9:28
You've got at least a couple of choices here, Kim. You could make the new case a subcase of the original one, or you could simply reference the original case in the new one (in the text). – Ken Morse♦ Nov 5 2009 at 12:39

Your Answer

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