andymckay / bugzilla-triage-helper Goto Github PK

Firefox nightly, Windows 10, gfx.webrender.all set to true. If the add-on is enabled, seems the keyboard input is ignored - I cannot manually type into the comment section in the bug, for example.

Currently when we make any meta-data changes to bugs, we are being added to the CC list of the bug, which can be quite annoying based on the CC settings of different bugzilla users.

Unchecking this might be preferable for some persons.

Need to get the appropriate query for the number of bugs that a user has to triage. This would mean:

• figuring out the logged in user
• querying bugzilla to find the number
• sticking that number in a few places
• updating that number on a regular interval
• limiting the query to a time limit

Although a user can't create new actions, it would be nice to filter down the list of actions for a user since only some might be relevant.

And possibly idle as well...

Keyboard command shortcuts per action would be nice. Since the list of actions and commands is static, this is just a pile of boilerplate code.

Should move that down a bit.

Let's allow the additional actions to be based on product and component rather than a hard coded user selection. This will support #21, but will be a pain when people change those.

I struggle to remember what "Backlog" means, but I know what P3 means. Just showing P3 might help me remember.

For example:

• if you do Defer, it will set some firefox release flags.
• if you then do "Accept patch" it doesn't reset those flags.

This makes it cool to quickly do additive things, like "Backlog and Accept Patch", but might be confusing if people change their mind.

I did the settings page, but not the actual code inside the content script.

When the keyword list contains any of "crash", "regression", "sec-*". I do not think it makes sense to call it an "enhancement", but maybe one of "normal", "major", "critical" or "blocker".

Clicking the browser action should take the user to the bugs to triage, as defined in #5.

When the addon is enabled the "add comment" text box is completely disabled, no input would appear in the textbox, which prevent the user from typing text such as adding question as part of the comment in addition to a need-info.

The work-around is to disable the addon to get access back to the textarea (even without reloading).

That's available here:

https://product-details.mozilla.org/1.0/firefox_versions.json

So then we can set the right flags for release etc

Using Travis CI, possibly?

Let's avoid any surprises for the user as to what the action will do by trying to put this into the UI somewhere.

It would be nice to be able to customize additional buttons, or attach actions to existing buttons. For example, when triaging WebRender, I have to also add a blocker bug, in addition to assigning P1-P3, and in that case, there are two possible blocker bugs for P1, and three possible blocker bugs for P2. Being able to have the shortcut buttons for the most common permutations would really help.

I noticed the sync team ignore bugs in their triage that have need infos on them, until they've sat unchanged for 14 days. In triages, I often assign out need infos to other members of the team to evaluate, investigate or reply and that sometimes takes a couple of days. A need info is a nice way of assigning out a task without holding up the triage.

@jandem mention this issue to me on IRC:
https://bugzilla.mozilla.org/show_bug.cgi?id=1435570#a225523_422187

Which will support #21.

You can't do anything if you are logged out, so no point in showing it.

Or maybe show it with a simple "Go log in" message.

It would be nice to have some canned responses. Most people will have different canned responses per project, so similar to issue #21, we should have something quick and easy to do that.

What the title says.

Namely:

Wontfix
Set status to RESOLVED
Set resolution to WONTFIX
Add a comment?
Incomplete
Set status to RESOLVED
Set resolution to to INCOMPLETE
Comment “Not enough information to move forward with this bug.”
Invalid
Set status to RESOLVED
Set resolution INVALID
Comment?
Works for me
Set status to RESOLVED
Set resolution WORKSFORME
Comment “Unable to reproduce on platform listed, please reopen if issue persists”
Backlog
Set priority to P3
Set status to NEW
Add comment “Moved to backlog by ”
Feature Request
Set severity to ‘enhancement’
Set status to NEW
P1
Set priority to P1
Set status to NEW
Set status flag for current release cycle to affected
Accept Patch
Set priority to P5
Set status to NEW
Add comment “We’ll accept a patch”
Needinfo
Prompt with an autocomplete (there’s an API) for a person
Capture comment
Defer
Set priority to P2
Set status to NEW
Set status flag for current release to wontfix
Set status flag for current release+1 to affected

Just select it automatically.