Difference between revisions of "Dynamic Bug List"

From Audacity Wiki
Jump to: navigation, search
(New steps.)
(No difference)

Revision as of 14:09, 22 September 2018

An example of the Dynamic Bug List can be seen at Release Notes 2.3.0/Issues

The Raw Issues

The raw issues are captured as follows:

1. Go to our bugzilla page, and click on the 'ExportAll' link at the foot of the page, and then choose CSV.
   CSV is at the foot of the page.

   It's this [https://bugzilla.audacityteam.org/buglist.cgi?columnlist=bug_id%2Cpriority%2Cbug_severity%2Ccomponent%2Ccf_issue_collection%2Cop_sys%2Cbug_status%2Cresolution%2Cshort_desc%2Ckeywords%2Cchangeddate%2Clongdescs.count%2Ccf_workaround%2Ccf_releasenotetext%2Copendate%2Ccf_date_closed&limit=0&query_format=advanced&ctype=csv&human=1 link]

   This should get you a full list of all bugs, open or closed.

2. Go to the CSV to JSON converter, and paste in the CSV https://www.csvjson.com/csv2json

3. Paste the updated JSON into wit-html/js/issues.js

Maintaining Dates

Bugzilla has a field it maintains for the date a bug was opened, but the closed date field is maintained by us. The javascript has functions you can run that will update the closed date field from the last-changed date field, IF a bug has been closed AND it is missing the closed date.

1. Enable the showClosed() function in the buglist.htm page.
2. Use Ctrl+Shift+I to get the chrome debugger.
3. Cut and paste the console output

It will have entries like these:

Closed[ 295 ]="2018-09-08 09:55:29";
Closed[ 231 ]="2018-09-13 09:29:34";
Closed[ 139 ]="2018-08-24 15:31:45";
Closed[ 33 ]="2018-08-24 15:31:45";
Closed[ 29 ]="2018-09-08 09:25:26";

Remove the line numbers and paste into issues.js

Issues.js now has updated end dates for the items missing end dates.