User Tools

Site Tools


bugzilla_guidelines

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Last revision Both sides next revision
bugzilla_guidelines [2009/05/04 14:07]
rivett
bugzilla_guidelines [2009/05/04 14:11]
rivett
Line 37: Line 37:
  
 The following are values for State that define the lifecycle: see attachment for the valid transitions (this may be configured). The ones I’ve marked as ‘unused’ are for completeness in this email (to show what Bugzilla provides by default) and have be deleted to avoid confusion The following are values for State that define the lifecycle: see attachment for the valid transitions (this may be configured). The ones I’ve marked as ‘unused’ are for completeness in this email (to show what Bugzilla provides by default) and have be deleted to avoid confusion
- UNCONFIRMED unused +            ​UNCONFIRMED unused 
- NEW bug not been processed at all +            NEW bug not been processed at all 
- ​ASSIGNED bug assigned to someone who is responsible for progressing it – which could involve reassigning it +            ASSIGNED bug assigned to someone who is responsible for progressing it – which could involve reassigning it 
- ​REOPENED original raiser or another person is not happy with the closure, or there is a regression +            REOPENED original raiser or another person is not happy with the closure, or there is a regression 
- ​RESOLVED fixed by the person responsible for the item in error e.g. a submitted file. Description should reference the SVN version number. Generally the resolution (below) will be FIXED +            RESOLVED fixed by the person responsible for the item in error e.g. a submitted file. Description should reference the SVN version number. Generally the resolution (below) will be FIXED 
- ​VERIFIED proved by the person raising the bug (e.g. the new submitted file can now be imported OK – or at least any failure is not due to the original problem) +            VERIFIED proved by the person raising the bug (e.g. the new submitted file can now be imported OK – or at least any failure is not due to the original problem) 
- ​CLOSED no further action needed. Could be for many reasons (see below).+            CLOSED no further action needed. Could be for many reasons (see below).
  
 And the following are the possible resolutions:​ And the following are the possible resolutions:​
- FIXED change has been made.  +            ​FIXED change has been made.  
- ​INVALID it’s not a bug in the component identified – i.e. the raiser was wrong. So it might need a new bug raised on another component (it’s not possible to change the component but you can easily ‘clone’ a bug). +            INVALID it’s not a bug in the component identified – i.e. the raiser was wrong. So it might need a new bug raised on another component (it’s not possible to change the component but you can easily ‘clone’ a bug). 
- ​WONTFIX it is a bug but there is no intention to fix it +            WONTFIX it is a bug but there is no intention to fix it 
- ​DUPLICATE there is already a bug for this. In general if 2 tools hit the same problem in a submitted file they should add information to the original bug to that effect rather than raising a new one +            DUPLICATE there is already a bug for this. In general if 2 tools hit the same problem in a submitted file they should add information to the original bug to that effect rather than raising a new one 
- ​WORKSFORME unused +            WORKSFORME unused 
- MOVED unused (but cannot be deleted). This is for exporting bugs to another Bugzilla database altogether.+            MOVED unused (but cannot be deleted). This is for exporting bugs to another Bugzilla database altogether.
  
  
bugzilla_guidelines.txt · Last modified: 2009/05/04 14:17 by rivett