From a098c49a0e460e4ec2f2d3f601e499b2bd455d2f Mon Sep 17 00:00:00 2001 From: Aleksandr Nogikh Date: Thu, 8 Dec 2022 15:44:44 +0100 Subject: dashboard: support reporting and unreporting of multiple crashes Previously we could only report a single crash ID for each reporting stage. That is enough for email reporting, but it unnecessarily restricts the interface available to external reporting methods. Instead of relying just on the Reported field of the Crash entity, introduce the list of other entities that reference the Crash. It lets us track the moment when the crash has been released by everyone else. --- dashboard/dashapi/dashapi.go | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-) (limited to 'dashboard/dashapi') diff --git a/dashboard/dashapi/dashapi.go b/dashboard/dashapi/dashapi.go index afdbacb7a..0c2db1ac7 100644 --- a/dashboard/dashapi/dashapi.go +++ b/dashboard/dashapi/dashapi.go @@ -444,7 +444,13 @@ type BugUpdate struct { ResetFixCommits bool // Remove all commits (empty FixCommits means leave intact). FixCommits []string // Titles of commits that fix this bug. CC []string // Additional emails to add to CC list in future emails. - CrashID int64 + + CrashID int64 // This is a deprecated field, left here for backward compatibility. + + // The new interface that allows to report and unreport several crashes at the same time. + // This is not relevant for emails, but may be important for external reportings. + ReportCrashIDs []int64 + UnreportCrashIDs []int64 } type BugUpdateReply struct { -- cgit mrf-deployment