Better way to report problematic URLs reported

VERIFIED INVALID

Status

--
enhancement
VERIFIED INVALID
8 years ago
7 years ago

People

(Reporter: aakashd, Unassigned)

Tracking

Dependency tree / graph

Details

(Reporter)

Description

8 years ago
We need to create a couple of things for reporting out our feedback here:

1. 

I think we need to create a table of URLs reported as problematic with:

URL
# of unique reports
first reported date
last reported date
comments (blob)

We can then use that table to feed into QA.

2. We need a list of "sad" and "happy" topics submitted. A reporting format over a one week period and looking something like the one shown here : http://davedash.com/2010/03/18/finding-the-most-common-firefox-issues/
The former can probably be generated as an RSS feed. The latter could be as well, maybe just cluster as a cron job and then generate a feed from the results?

Updated

8 years ago
Assignee: ddahl → nobody

Comment 2

8 years ago
not my bug, changed it back top default
This bug should be split, for better tracking.

Updated

8 years ago
Blocks: 577766

Updated

8 years ago
Blocks: 577767
(In reply to comment #3)
> This bug should be split, for better tracking.

You're welcome.
Status: NEW → RESOLVED
Last Resolved: 8 years ago
Resolution: --- → INVALID
(Reporter)

Comment 5

8 years ago
:P
Status: RESOLVED → VERIFIED
(Assignee)

Updated

7 years ago
Component: Input → General
Product: Webtools → Input
You need to log in before you can comment on or make changes to this bug.