Update all code site issue tracker links to point to bug.skia.org

site/dev/sheriffing/index.md

 Tree Sheriffs Documentation
 ===========================
 
 ### Contents ###
 
 *   [What does a sheriff do?](#what_is_a_sheriff)
     +   [Skia tree](#skia_tree)
     +   [DEPS rolls](#deps_rolls)
     +   [Gold and Perf](#gold_and_perf)
     +   [Documentation](#sheriff_doc)
@@ skipping 16 matching lines @@
 
 Below is a brief summary of what the sheriff does for each task:
 
 <a name="skia_tree"></a>
 ### Skia tree
 * Understand the [buildbots infrastructure](https://skia.org/dev/testing/buildbot).
 * Start watching the [status page](https://status.skia.org) for bot breakages.
 * Track down people responsible for breakages and revert broken changes if there is no easy fix.
 * Close and open the [tree](http://skia-tree-status.appspot.com).
 * Keep the builder comments on the [status page](https://status.skia.org) up to date.
-* File or follow up with [BreakingTheBuildbots bugs](https://code.google.com/p/skia/issues/list?q=label:BreakingTheBuildbots). See the tip on [when to file bugs](#when_to_file_bugs).
+* File or follow up with [BreakingTheBuildbots bugs](https://bug.skia.org/?q=label:BreakingTheBuildbots). See the tip on [when to file bugs](#when_to_file_bugs).
 
 <a name="deps_rolls"></a>
 ### DEPS rolls
 * Ensure that [AutoRoll Bot](https://skia-tree-status.appspot.com/set_arb_action)'s DEPS rolls land successfully.
 
 <a name="gold_and_perf"></a>
 ### Gold and Perf
 * Pay attention for new [Perf](https://perf.skia.org/) and [Gold](https://gold.skia.org/) alerts (by clicking on the bell at the top right of the [status page](https://status.skia.org)).
 * The sheriff's duty here is to make sure that when developers introduce new images or new perf regressions, that they are aware of what happened, and they use these tools to take appropriate action.
  
@@ skipping 20 matching lines @@
 
 
 <a name="tips"></a>
 Tips for sheriffs
 -----------------
 
 <a name="when_to_file_bugs"></a>
 ### When to file bugs
 
 Pay close attention to the "Failures" view in the [status page](https://status.skia.org).
-Look at all existing [BreakingTheBuildbots bugs](https://code.google.com/p/skia/issues/list?q=label:BreakingTheBuildbots). If the list is kept up to date then it should accurately represent everything that is causing failures. If it does not, then please file/update bugs accordingly.
+Look at all existing [BreakingTheBuildbots bugs](https://bug.skia.org/?q=label:BreakingTheBuildbots). If the list is kept up to date then it should accurately represent everything that is causing failures. If it does not, then please file/update bugs accordingly.
 
 
 <a name="how_close_tree"></a>
 ### How to close or re-open the tree
 
 1. Go to [skia-tree-status.appspot.com](skia-tree-status.appspot.com).
 2. Change the status.
  *  To close the tree, include the word "closed" in the status.
  * To open the tree, include the word "open" in the status.
  * To caution the tree, include the word "caution" in the status.
@@ skipping 63 matching lines @@
   * Add # comment about what has changed 
   * Add line(s) like the following after the comment:
       * crbug.com/<bug#youjustcreated> foo/bar/test-name.html [ NeedsRebaseline ]
         * (if you took the second option above you can just edit the existing line(s))
 
 * If you took the first/dispreferred option above:
   * Wait for the Blink patch to roll into Chrome
   * Create a Chrome patch that removes your suppressions from skia/skia_test_expectations.txt