diff --git a/treeherder/perf/fixtures/performance_bug_templates.yaml b/treeherder/perf/fixtures/performance_bug_templates.yaml index 5fb248fd6..987c4b4f3 100644 --- a/treeherder/perf/fixtures/performance_bug_templates.yaml +++ b/treeherder/perf/fixtures/performance_bug_templates.yaml @@ -117,4 +117,19 @@ Details of the alert can be found in the [alert summary]({{ alertHref }}), including links to graphs and comparisons for each of the affected tests. Please follow our [guide to handling regression bugs](https://wiki.mozilla.org/TestEngineering/Performance/Handling_regression_bugs) and **let us know your plans within 3 business days, or the offending patch(es) will be backed out** in accordance with our [regression policy](https://www.mozilla.org/en-US/about/governance/policies/regressions/). + For more information on performance sheriffing please see our [FAQ](https://wiki.mozilla.org/TestEngineering/Performance/FAQ). +- model: perf.PerformanceBugTemplate + pk: 10 + fields: + framework: 12 + keywords: perf, perf-alert, regression, devtools-perf-regression + default_component: General + default_product: DevTools + text: | + Perfherder has detected a {{ framework }} performance regression from push [{{ revision }}]({{ revisionHref }}). As author of one of the patches included in that push, we need your help to address this regression. + + {{ alertSummary }} + + Details of the alert can be found in the [alert summary]({{ alertHref }}), including links to graphs and comparisons for each of the affected tests. Please follow our [guide to handling regression bugs](https://wiki.mozilla.org/TestEngineering/Performance/Handling_regression_bugs) and **let us know your plans within 3 business days, or the offending patch(es) will be backed out** in accordance with our [regression policy](https://www.mozilla.org/en-US/about/governance/policies/regressions/). + For more information on performance sheriffing please see our [FAQ](https://wiki.mozilla.org/TestEngineering/Performance/FAQ).