Monorail is a tool that is actively used and maintained by the Chromium community. It is important that we look at issues reported by our users and take appropriate actions.
For the full list of trooper responsibilities, see go/chops-workflow-trooper.
needs:Feedbackand ask the reporter for more information.
Pri-0: assign self as
status:Started, notify team leads, follow the IRM process as Incident Commander.
Pri-1: assign self as owner, mark
status:Startedand work to resolve the issue. Find another owner and make a formal handoff if you are not able to address.
needs:Feedbackfor more than 7 days without response, mark as
status:WontFixwith an explanatory comment.
Pri-0: Critical issue causing failures in production. Major functionality broken that renders a feature unusable for all customers.
Pri-1: Urgent; the issue is blocking a user from getting their job done. Defect causing functional regression in production. Production issue impacting other customers. Any type of security or privacy problem. Finally, any workflow administrative tasks that have been officially asked to the trooper to handle, that includes very explicitly: Monorail API access request, Sheriffbot testing & deployment, and Hotlist removal.
Pri-2: Important; tied to OKRs or near term upcoming release. Bug that should be addressed in one of the next few releases.
Pri-3: We feel your pain: the team would like to fix this, but lacks the resources to do this soon. Desirable feature or enhancement not on the near-term roadmap. Defects that are not regressions, have workarounds, and affect few users.
Pri-4: Ponies and icebox. Unfortunate: it's a legitimate issue, but the team never plans to fix this.