Page History

...

1. If the issue is a duplicate, close it as such.
2. If the issue belongs to a different component, make sure the state is 'New' and transfer it to the correct component.
3. If the issue is incomplete, add a comment noting what is needed and close the bug as 'Resolved' - 'Incomplete'. This is our way of saying "need more information".
4. If the issue is complete:
   1. ensure the priority is correct
   2. ensure the 'Affects Version/s' field is correct (within reason)
      1. this may involve reproducing the bug, if doing so is fast and easy
   3. set the 'Fix Version/s'
      1. a bug should be fixed in the most recent version where it exists
      2. if the bug also exists in older versions it may require backporting to those
         1. the decision to backport should be made in agreement with those responsible for the relevant update release
         2. create backport issue(s) once it is agreed that the bug should be backported

         Note
         Fix version must be a singular value for JBS issues. Unfortunately we can't stop JIRA from allowing it to have multiple values.

   4. make sure the bug has all the required labels
      1. bugs that are new in the current release: 'regression'
      2. bugs that was introduced after the last upstream integration: 'integration_blocker'
      3. bugs that do not affect product code, but only tests: 'testbug'
      4. issues that seems to be really trivial to fix: 'starter'
      5. RFEs that are pure cleanups: 'cleanup'
      6. project specific issues usually have their own labels as well
   5. bring high priority (P1, P2, or integration_blocker) bugs to the attention of the component team; assign the bug to an engineer
   6. 'Triage' the issue so that it moves to the 'Open' state

...