1463857 - Create an app to give me the next bug I should diagnose

Status: RESOLVED WONTFIX

(Web Compatibility :: Tooling & Investigations, defect, P1)

Description

[Mike Taylor [:miketaylr]]

This bug tracks the work to create a webapp that will do the following:

* gives the user a button they can click that tells them what the next bug is they should diagnose

It should consider the following constraints as ranking criteria (1, 2, and 3 are just some abstract notion of weighted importance):

1. Bugzilla Tech Evangelism::Desktop/Mobile P1 bugs with [needsdiagnosis] whiteboard tag
1. Non-anonymous GitHub webcompat/web-bugs with priority-critical label
2. Non-anonymous GitHub webcompat/web-bugs with priority-important label
2. Anonymous (filed by @webcompat-bot) GitHub webcompat/web-bugs with priority-critical label
2. Anonymous GitHub webcompat/web-bugs with priority-critical label
3. Bugzilla Tech Evangelism::Desktop/Mobile P3 bugs with [needsdiagnosis] whiteboard tag
3. Any other GitHub webcompat/web-bugs with priority-normal label

Let's build something, then figure out how to solve the "don't give the same bugs to different people" problem.

Comment 1

[Kate Manning [:laghee]]

I've figured out all my queries and made a bug object model, but I've run into a couple of questions:

• How do people file GH bugs anonymously (i.e., not with the bot, as in 3rd #2 above)? I can't find an example issue, so I'm not sure what I should be looking for in the "author" field.

• My impulse was to sort so that the oldest bug is offered up first, but many of the oldest GH issues have "sitewait" milestones attached. Is it better to grab those anyway so that they're checked periodically? Or should I discard those (or only grab "needstriage" or "needsdiagnosis") because there's an existing system in place that reminds us when to review that status? Or...?

Comment 2

[Mike Taylor [:miketaylr]]

(In reply to Kate Manning from comment #1)
> I've figured out all my queries and made a bug object model, but I've run
> into a couple of questions:
> 
> • How do people file GH bugs anonymously (i.e., not with the bot, as in 3rd
> #2 above)? I can't find an example issue, so I'm not sure what I should be
> looking for in the "author" field.

Sorry, that's unintentionally confusing. All anon bugs are filed by @webcompat-bot.

> • My impulse was to sort so that the oldest bug is offered up first, but
> many of the oldest GH issues have "sitewait" milestones attached. Is it
> better to grab those anyway so that they're checked periodically? Or should
> I discard those (or only grab "needstriage" or "needsdiagnosis") because
> there's an existing system in place that reminds us when to review that
> status? Or...?

Ah yeah, all of the candidate bugs should be pulled from the "needsdiagnosis" milestone -- sorry for not specifying this. Milestones are mutually exclusive, so you won't get any "sitewait" (or anything else) bugs.

Comment 3

[Kate Manning [:laghee]]

In progress, but online: http://nbo.herokuapp.com/nbo

Todo: 

• Figure out how to avoid giving the same bug(s) to different people (maybe involving PostgreSQL)
• Adapt for needstriage training/testing (e.g., give blocks of 10 bugs filtered by necessary params)
• Make results reload in place with jquery, React, Vue, or other (i.e., be modern), rather than redirect to second page (as though made with duct tape & paperclips)

Comment 4

[BugBot [:suhaib / :marco/ :calixte]]

The bug assignee didn't login in Bugzilla in the last months and this bug has priority 'P1'.
:denschub, could you have a look please?
For more information, please visit auto_nag documentation.

Comment 5

[Dennis Schubert [:denschub]]

Since we no longer have the goal of diagnosing every single issue, I'm afraid this isn't the best thing to be working on right now... Let's close this, we can always come back to this if it becomes relevant again.