mozilla-bteam / bugzilla-readable-status Goto Github PK

Getting lists of uplifts, affected versions, etc are queries that could be in it's own module.

https://bugzilla.mozilla.org/show_bug.cgi?id=1273668

https://bugzilla.mozilla.org/show_bug.cgi?id=1276183

The bug is a regression found in Firefox 47, but the status says: "NEW regression bug found in Firefox 48 with no priority".

https://bugzilla.mozilla.org/show_bug.cgi?id=1265420

At the very very top, right underneath the summary, it says:

RESOLVED FIXED in Firefox 47

But the readable status underneath it says:

(bug RESOLVED as FIXED for Firefox 49)

Because the bug got uplifted, and the release flags for 47 and 48 are set to 'fixed', I believe the readable status should also indicate the bug was fixed in 47.

Orthogonally, it seems like the status could go on the line that now has the "RESOLVED FIXED in Firefox 47" information as it will most likely be a strict superset of that information...

"NEW Core::DOM bug which should be worked on in the next release/iteration" instead of just "NEW bug which should be worked on in the next release/iteration".

https://bugzilla.mozilla.org/show_bug.cgi?id=1345575

https://bugzilla.mozilla.org/show_bug.cgi?id=1273664

https://github.com/emceeaich/bugzilla-readable-status/blob/master/index.js#L155-L161

getFlags() refers to fields so it should be called getFields()

As of January 1 2019, Mozilla requires that all GitHub projects include this CODE_OF_CONDUCT.md file in the project root. The file has two parts:

1. Required Text - All text under the headings Community Participation Guidelines and How to Report, are required, and should not be altered.
2. Optional Text - The Project Specific Etiquette heading provides a space to speak more specifically about ways people can work effectively and inclusively together. Some examples of those can be found on the Firefox Debugger project, and Common Voice. (The optional part is commented out in the raw template file, and will not be visible until you modify and uncomment that part.)

If you have any questions about this file, or Code of Conduct policies and procedures, please see Mozilla-GitHub-Standards or email [email protected].

(Message COC001)

change "for which no priority has been set" to "with no priority"

This tool has opinions about bug data quality. Make that assessment, return it as part of the object that comes back.

Yes, you have to change the interface for single bugs so that it returns an object instead of a string, but there are worse fates.

P3 should be "backlog"

See http://blog.npmjs.org/post/118810260230/building-a-simple-command-line-tool-with-npm

Lots of bugs just ride the train.

Use the rules: NEW, not in 'general' or 'untriaged', and P1-P3, P4

This needs to be minifyify-ed for including in pages.

https://bugzilla.mozilla.org/show_bug.cgi?id=1300755

has:

(ASSIGNED regression bug found in Firefox 50 which should be worked on in the next release/iteration awaiting an answer on a request for information)

but flags are:

firefox48 --- unaffected
firefox49 --- wontfix
firefox50 --- affected
firefox51 --- affected

so really the bug was found in 49. fix-optional and fixed and verified should probably also affect when we claim the bug was found.

Probably use moz-review here

So that we don't barf on an unanticipated error when trying to parse a bug, trap exceptions in parse and return an error message.