All users were logged out of Bugzilla on October 13th, 2018

get CSV data link doesn't work (new front end)

VERIFIED FIXED in 0.3

Status

VERIFIED FIXED
11 years ago
2 years ago

People

(Reporter: anodelman, Assigned: lorchard)

Tracking

Details

(URL)

Attachments

(1 attachment, 1 obsolete attachment)

(Reporter)

Description

11 years ago
Link at the bottom of the page to get csv data for a selection range just reloads the front page.  Does this both if no range is selected and if a range is selected.  If no range is selected it should do nothing, if a range is selected it should provide you with the csv data requested.
Assignee: nobody → lorchard
Summary: get CVS data link doesn't work (new front end) → get CSV data link doesn't work (new front end)
Target Milestone: --- → 0.3
(Assignee)

Updated

10 years ago
Depends on: 445588
(Assignee)

Comment 1

10 years ago
Created attachment 329905 [details] [diff] [review]
code to update the CSV download link in the UI, as well as tweaks to dumpdata.cgi

Looks like the CSV link is now updating, and the dumpdata.cgi script works with this patch.  Some data is missing on my machine, but I think the staging database will actually fill in the gaps (ie. dataset_info within a certain timeframe, buildids, etc)
(Assignee)

Comment 2

10 years ago
Created attachment 329907 [details] [diff] [review]
revised version of last patch to remove some cruft

Left some obsolete code in the CSV link construction, revised patch attached
Attachment #329905 - Attachment is obsolete: true
Attachment #329907 - Flags: review?(laura)

Updated

10 years ago
Attachment #329907 - Flags: review?(laura) → review+
(Assignee)

Comment 3

10 years ago
Patch checked in as changeset 97:352721f081d8
Status: NEW → RESOLVED
Last Resolved: 10 years ago
Resolution: --- → FIXED
Verified FIXED; http://graphs-stage.mozilla.org/server/dumpdata.cgi?show=67,89&sel=1181024474,1181359187 gave me datadump.cgi gave me a valid CSV file (afaict).
Status: RESOLVED → VERIFIED
Product: Webtools → Webtools Graveyard
You need to log in before you can comment on or make changes to this bug.