@@ -470,6 +470,10 @@
"Wic",
];
+ const ignoreComponents = [
+ "meta-security",
+ ];
+
// Fields to display (bugzilla field name -> column header)
const fields = new Map([
["id", "ID"],
@@ -544,9 +548,16 @@
reloadButton.classList.toggle('spin')
params.append("include_fields", Array.from(fields.keys()).join());
- params.append("f0", "product",)
- params.append("o0", "notregexp",)
- params.append("v0", `^(${ignoreProducts.map((s) => escapeRegExp(s)).join("|")})$`)
+
+ // Ignore specific products and components. The field numbers are high so
+ // that caller's queries can use fields without conflicts.
+ params.append("f100", "product",)
+ params.append("o100", "notregexp",)
+ params.append("v100", `^(${ignoreProducts.map((s) => escapeRegExp(s)).join("|")})$`)
+
+ params.append("f101", "component",)
+ params.append("o101", "notregexp",)
+ params.append("v101", `^(${ignoreComponents.map((s) => escapeRegExp(s)).join("|")})$`)
var bzlink = document.createElement("a");
var buglistURL = `${serverUrl}/buglist.cgi?${params}`;
These issues are not triaged by the Yocto triage team. This means adding support for ignoring components. To avoid field conflicts with the caller's arbitrary field queries, change the numbering to 100 onwards. This means there is still a theoretical chance of conflicts but it's unlikely, and luckily bugzilla doesn't care that the queries are not numbered sequentially. Signed-off-by: Ross Burton <ross.burton@arm.com> --- scripts/dashboard/bugtriage/index.html | 17 ++++++++++++++--- 1 file changed, 14 insertions(+), 3 deletions(-)