Update subscription instructions for Monorail.

net/docs/bug-triage-suggested-workflow.md

 # Chrome Network Bug Triage : Suggested Workflow
 
 [TOC]
 
 ## Looking for new crashers
 
 1. Go to [go/chromecrash](https://goto.google.com/chromecrash).
 
 2. For each platform, look through the releases for which releases to
    investigate.  As per bug-triage.txt, this should be the most recent canary,
@@ skipping 70 matching lines @@
   browser crash) and attach the most specific internals-network label that's
   applicable.  If there isn't an applicable narrower label, a clear owner for
   the issue, or there are multiple possibilities, attach the internals-network
   label and proceed with further investigation.
 
 * If non-network causes also seem possible, attach those labels as well.
 
 ## Investigating Cr-Internals-Network bugs
 
 * It's recommended that while on triage duty, you subscribe to the
-  Cr-Internals-Network label.  To do this, go to the issue tracker and click on
-  [Subscriptions](https://code.google.com/p/chromium/issues/subscriptions).
-  Enter "Cr-Internals-Network" and click submit.
+  Internals>Network component (and its children). To do this, go to the issue
+  tracker, click on "Profile", then go to "Saved Queries".

[mmenke, 2016/02/22 18:52:19]

Profile -> Issues?  It's to the right of the search box.  Think it's better to
mention its location there, since that's more convenient, relative to where
people spend their time.

[eroman, 2016/02/22 19:04:14]

Done.

+  Add a query with these settings:
+  * Project: chromium
+  * Query: component:Internals>Network

[mmenke, 2016/02/22 18:52:19]

Hrm...My old queries were converted to component=Internals>Network.  Is there a
difference between the two?

[mmenke, 2016/02/22 18:52:19]

Should we mention a name being needed?  I've had great luck with "Billy Bob", so
maybe we should suggest that?

[eroman, 2016/02/22 19:04:14]

Or alternately mmenke rulz?

Done: "Network Bug Triage"

[eroman, 2016/02/22 19:04:14]

Yes there is:

It is explained on https://bugs.chromium.org/p/chromium/issues/searchtips

  component:UI will search essentially UI>*

whereas

  component=UI will search just UI

So a bug on UI>Foobar would fire on the colon version, but not the equal
version.

[mmenke, 2016/02/22 19:12:03]

Hrm...I don't think the triager should subscribe to all sublabels?

[eroman, 2016/02/22 19:17:57]

Done.

+  * Subscription options: Notify Immediately
 
 * Look through uncomfirmed and untriaged Cr-Internals-Network bugs,
   prioritizing those updated within the last week. [Use this issue tracker
   query](https://code.google.com/p/chromium/issues/list?can=2&q=Cr%3DInternals-Network+-status%3AAssigned+-status%3AStarted+-status%3AAvailable+&sort=-modified).
 
 * If more information is needed from the reporter, ask for it and add the
   Needs-Feedback label.  If the reporter has answered an earlier request for
   information, remove that label.
 
 * While investigating a new issue, change the status to Untriaged.
@@ skipping 131 matching lines @@
       reproduced or really understood:
         * If it's over a year old, go ahead and mark the issue as Archived.
         * Otherwise, ask reporters if the issue is still present, and attach
           the Needs-Feedback label.
 
 * Old unconfirmed or untriaged Cr-Internals-Network issues can be investigated
   just like newer ones.  Crashers should generally be given higher priority,
   since we can verify if they still occur, and then newer issues, as they're
   more likely to still be present, and more likely to have a still responsive
   bug reporter.