#1 Bug History

open
nobody
None
5
2001-06-19
2001-06-19
No

Each Bug should get a Bug-History where is stored who
redirects the bug,
adds a comment, changes a status and when he did it.

Maybe like that

Bug-headers
like id, description,..
bug-history
step 1: new Status=open, user=tester, comment='i
found the bug,...'
step 2: new Status=open, user=project-admin,
comment='developer has to fix
it'
step 3: new Status=fixed, user=developer, comment='i
have changed code'
step 4: new Status=open, user=tester, comment='can't
verified'
step 5: new Status=fixed, user=developer,
comment='you must get it
there...'
step 6: new Status=closed, user=tester,
comment='FIXED in Version x.x'

A bug should always have an 'active person', who has
to act.
The action can be redirect the bug to another person,
fix the bug or close
it(tester).

Discussion


Log in to post a comment.

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:

JavaScript is required for this form.





No, thanks