New issue
Advanced search Search tips

Issue 850192 link

Starred by 1 user

Issue metadata

Status: Available
Owner: ----
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 1
Type: Bug



Sign in to add a comment

Information loss while filing a bug in Sheriff-o-matic

Project Member Reported by lambroslambrou@chromium.org, Jun 6 2018

Issue description

While sheriffing yesterday, I tried to file a new bug for an alert via the associated "File Bug" button.

The button popped up a dialog in which I started entering the bug description (general information, copied log snippets from builders...)

If I recall correctly, I switched to another Chrome tab to gather some information for the new bug. When I returned to the SoM tab, the new-bug entry dialog had disappeared, along with all the information I had entered so far. SoM simply showed its main page with alerts. The alert I was filing the bug for was no longer present in the list.

Fortunately, I had kept a Chrome tab open with a link to the official builder. If I hadn't done that, all the information would have been completely lost, and there's no way I could have found the failing build.

In my case it was no big deal, but I can see this potentially causing a lot of frustration, so I will assign it Pri-1 for now.

I have filed separately bug 850179 for the disappearing alerts. This bug is about the information loss that occurs when an alert disappears (or SoM refreshes itself) while you are filing a bug for it.

Should we disable auto-refresh during bug entry? Or find a way to avoid disrupting the bug-entry dialog?


 
Labels: Milestone-Polish
Disabling autorefresh during bug filing seems like a sensible solution to me here. 
Status: Available (was: Untriaged)

Sign in to add a comment