RTC Bug Introduced vs Pre-existing Defect

Jamie Schena

(53●15●21) 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!

1 vote

1 answer

2,763 views

1 vote

One answer

Permanent link

Krzysztof Kaźmierczyk

(7.5k●4●80●103) 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.

1 vote

Comments

Ralph Schoon

FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER Apr 30 '15, 2:05 a.m.

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

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.

Follow this question

By Email:

Once you sign in you will be able to subscribe for any updates here.

By RSS:

Answers

Answers and Comments

Question details

rational-team-concert

× 42,903

usage

× 12,023

Question asked: Apr 29 '15, 11:44 a.m.

Question was seen: 2,763 times

Last updated: Apr 30 '15, 2:05 a.m.

RTC Bug Introduced vs Pre-existing Defect

Jamie Schena

1 answer

2,763 views

1 vote

One answer

Krzysztof Kaźmierczyk

Comments

Ralph Schoon

Your answer

Follow this question

Question details

Related questions