From 703f643f91e8becd2495f1f102346a0b7fa63867 Mon Sep 17 00:00:00 2001 From: Aleksandr Nogikh Date: Mon, 24 Apr 2023 19:52:41 +0200 Subject: dashboard: support bug labels Let bug labels come in three flavours: 1) Bug labels with multiple values (e.g. `subsystems`). 2) Bug labels with only one value (e.g. `prio`). 3) Flags. Let users configure bug labels via email by issuing the following commands: #syz set subsystems: abc, def #syz set no-reminders #syz unset no-reminders Also let users set tags for invididual bugs in reported bug lists: #syz set <1> some-tag --- dashboard/app/linux_reporting.go | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'dashboard/app/linux_reporting.go') diff --git a/dashboard/app/linux_reporting.go b/dashboard/app/linux_reporting.go index 98220194b..8ddffd433 100644 --- a/dashboard/app/linux_reporting.go +++ b/dashboard/app/linux_reporting.go @@ -8,9 +8,9 @@ package main // canBeVfsBug determines whether a bug could belong to the VFS subsystem itself. func canBeVfsBug(bug *Bug) bool { - for _, subsystem := range bug.Tags.Subsystems { + for _, subsystem := range bug.LabelValues(SubsystemLabel) { // The "vfs" one is left for compatibility with the older matching code. - if subsystem.Name == "vfs" || subsystem.Name == "fs" { + if subsystem.Value == "vfs" || subsystem.Value == "fs" { return true } } -- cgit mrf-deployment