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
bugzilla_guidelines [2009/05/04 14:11]
rivett
bugzilla_guidelines [2009/05/04 14:17] (current)
rivett
Line 1: Line 1:
 The proposed usage is as follows: Many of these options can be configured or deleted (e.g. severity values) The proposed usage is as follows: Many of these options can be configured or deleted (e.g. severity values)
  
-Product: Model Interchange Test Suite (fixed value) +**Product**: Model Interchange Test Suite (fixed value) 
-Component: one of the following which will be enumerated: Test case N, Tool T, Validator, Standard (one of: UML, XMI, SysML, MOF, UPDM) + 
-Version: release of the test case or tool or standard +**Component**: one of the following which will be enumerated: Test case N, Tool T, Validator, Standard (one of: UML, XMI, SysML, MOF, UPDM) 
-Severity: one of the following:+ 
 +**Version**: release of the test case or tool or standard 
 + 
 +**Severity**: one of the following:
             Enhancement – normally for test cases to improve the test             Enhancement – normally for test cases to improve the test
             Blocker – prevents the interchange running at all (typically for imports) with no workround             Blocker – prevents the interchange running at all (typically for imports) with no workround
Line 12: Line 15:
             minor – problem with unimportant element, deviation from standard that has no interchange implication (e.g. default value serialized)             minor – problem with unimportant element, deviation from standard that has no interchange implication (e.g. default value serialized)
             trivial – insignificant problem that does not affect interchange e.g. spelling, XMI documentation             trivial – insignificant problem that does not affect interchange e.g. spelling, XMI documentation
-Platform: ignored +**Platform**: ignored
-OS: ignored +
-Priority: P1 thru P5 with P1 being the highest. Subjective ordering that is initially set by the raiser but can be changed by the assignee (e.g. tool vendor) +
-Initial State: NEW or ASSIGNED (depending on next field) (see below for other values) +
-Assign To: email address if known of person to which it should be initially assigned. We have one official contact point for bugs per tool. And an official author per test case +
-CC: others who might be interested+
  
-Estimated hoursignore +**OS**ignored
-Deadline: if there is one+
  
-URL: reference to the file in SVN which is wrong where relevant. Does not need to be a dereferenceable URL. Should include the SVN version number. E.g. trunk\Tests\UML2.1.1-XMI2.1\Test-Case-1\Submissions\MagicDraw-16.5\ our-export.xml[18424] +**Priority**:​ P1 thru P5 with P1 being the highest. Subjective ordering that is initially set by the raiser but can be changed by the assignee (e.g. tool vendor) 
-Keywords: it’s possible to configure keywords, though you do not get a list to tick when editing bugs (just an error if you try to use a bad one). We have the following.+ 
 +**Initial State**: NEW or ASSIGNED (depending on next field) (see below for other values) 
 + 
 +**Assign To**: email address if known of person to which it should be initially assigned. We have one official contact point for bugs per tool. And an official author per test case 
 + 
 +**CC**: others who might be interested 
 + 
 +**Estimated hours**: ignore 
 + 
 +**Deadline**:​ if there is one 
 + 
 +**URL**: reference to the file in SVN which is wrong where relevant. Does not need to be a dereferenceable URL. Should include the SVN version number. E.g. trunk\Tests\UML2.1.1-XMI2.1\Test-Case-1\Submissions\MagicDraw-16.5\ our-export.xml[18424] 
 + 
 +**Keywords**: it’s possible to configure keywords, though you do not get a list to tick when editing bugs (just an error if you try to use a bad one). We have the following.
             Export – problem with XMI submitted by a tool for a test case             Export – problem with XMI submitted by a tool for a test case
             Import – problem with import of a submission XMI             Import – problem with import of a submission XMI
             Diagram – problem with a diagram (either the original test case diagram or the ability of a tool to reproduce it)             Diagram – problem with a diagram (either the original test case diagram or the ability of a tool to reproduce it)
  
-Summary: headline for issue +**Summary**: headline for issue 
-Description:​ should be complete and not assume the Summary. For issues on standards include the OMG issue number(s). + 
-Attachment: should not normally be needed if we reference the SVN file +**Description**: should be complete and not assume the Summary. For issues on standards include the OMG issue number(s). 
-Depends on: Number of other issue which must be fixed before this one can be. For example an error in the test case. + 
-Blocks: Inverse of above+**Attachment**: should not normally be needed if we reference the SVN file
 + 
 +**Depends on**: Number of other issue which must be fixed before this one can be. For example an error in the test case. 
 + 
 +**Blocks**: Inverse of above
  
 Once a bug has been raised, anyone can add additional comments to it (these are kept separate). And the following fields are available Once a bug has been raised, anyone can add additional comments to it (these are kept separate). And the following fields are available
  
-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.  
-            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)+                     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)
             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 ​values for **Resolution**:
             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