It's all about the answers!

Ask a question
QuestionsTagsUsersBadges
Guidelines | FAQ
Follow this question
Question details

×42,879
×12,005

question asked: Apr 29 '15, 11:44 a.m.
question was seen: 2,627 times
last updated: Apr 30 '15, 2:05 a.m.

Related questions

RTC Bug Introduced vs Pre-existing Defect

1
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

1
permanent link
Krzysztof Kaźmierczyk (7.5k●4●80●103) | 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.

Your answer

Register or to post your answer.


Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.