RTC Bug Introduced vs Pre-existing Defect

Jamie Schena (53●15●21) | asked Apr 29 '15, 11:44 a.m.

We have pre-existing defects (that may have been introduced in a previous code drop) and then new defects that are created when developers are trying to fix that bug. Any suggestions as to how to differentiate between a bug that is introduced vs a new defect to fix a pre-existing issue (i.e. the issue has been around since the application was first developed)?

Thanks!

One answer

Most liked answers ↑|Newest answers|Oldest answers

permanent link

Krzysztof Kaźmierczyk (7.4k●3●54●99) | answered Apr 29 '15, 11:49 a.m.

Hi Jamie,
You can simply create new attribute in defect indicating that it has been introduced by fix of another defect.

Comments

Ralph Schoon commented Apr 30 '15, 2:05 a.m.

FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER

You can also create a new type based on defect and call it regression or something like that. I would likely go with Krysztof's suggestion to keep the numbers of types low though.

It's all about the answers!

Related questions

RTC Bug Introduced vs Pre-existing Defect

One answer

Your answer