Tom Schulenburg
07-16-2003, 03:43 PM
"Eric" <egDfAusenetE5fz@verizon.net> wrote in message
news:1fy6odz.vxiu9gsxlclcN%egDfAusenetE5fz@verizon.net... It seems pretty obvious to me that when entering bugs into a bug database, that they should be single issue entries...i.e. if one found multiple problems, each problem should be in a separate entry in the database. Is this obvious to everyone else here as well? If you disagree, I would be interested in learning why.
I'll agree, but only if you're talking about bugs that will each require a
separate fix. If there are five typo's on a screen, don't enter 5 bugs,
enter one bug for the screen and list the typo's. If a calculation is wrong,
such as "xyz total", and it's displayed on multiple screens, don't enter a
bug for each screen that it's displayed on, enter a bug to fix "xyz total".
You should never combine bugs that have no relation - "Total is wrong and
link is broken", etc.
-T
news:1fy6odz.vxiu9gsxlclcN%egDfAusenetE5fz@verizon.net... It seems pretty obvious to me that when entering bugs into a bug database, that they should be single issue entries...i.e. if one found multiple problems, each problem should be in a separate entry in the database. Is this obvious to everyone else here as well? If you disagree, I would be interested in learning why.
I'll agree, but only if you're talking about bugs that will each require a
separate fix. If there are five typo's on a screen, don't enter 5 bugs,
enter one bug for the screen and list the typo's. If a calculation is wrong,
such as "xyz total", and it's displayed on multiple screens, don't enter a
bug for each screen that it's displayed on, enter a bug to fix "xyz total".
You should never combine bugs that have no relation - "Total is wrong and
link is broken", etc.
-T