1361870 - Please create Screenshots components under Cloud Services product

Status: RESOLVED FIXED

(bugzilla.mozilla.org :: Administration, task, P1)

Description

[Jared Hirsch [:jhirsch] (he/him) (Needinfo please)]

The first Screenshots component is for the client part of Firefox Screenshots:

Name: Screenshots
Product: Cloud Services
Description: For Firefox Screenshots system add-on bugs related to security and release tracking.
Triage lead: Ian Bicking (:ianb)


The second Screenshots component is for the server part of Firefox Screenshots:

Name: "Server: Screenshots"
Product: Cloud Services
Description: For Firefox Screenshots server bugs related to security and release tracking.
Triage lead: Ian Bicking (:ianb)


For both components, if possible, I'd like to show the "task-specific bug form" warning message that's shown on the addons.mozilla.org new bug page (https://bugzilla.mozilla.org/enter_bug.cgi?product=addons.mozilla.org). The Github URL for filing Screenshots bugs is https://github.com/mozilla-services/screenshots/issues.

Comment 1

[Emma Humphries ☕️🎸🧞‍♀️✨ (she/they) [:emceeaich] (Pacific Time) use needinfo]

We need a way to redirect to github once the component is selected. Let me open another bug about that.

Comment 2

[Dylan Hardison [:dylan] (he/him)]

Should those components be created before or after the special code emma mentions in comment 1 is written?

Comment 3

[Jared Hirsch [:jhirsch] (he/him) (Needinfo please)]

Attachment: screenshot of github link on AMO bugzilla form

Comment 4

[Jared Hirsch [:jhirsch] (he/him) (Needinfo please)]

Hey Dylan - I'm not sure about auto-redirecting, I was thinking of just exposing the same warning notice that's shown when you open the new bug form for the AMO component, see comment 3 for a screenshot.

Comment 5

[Dylan Hardison [:dylan] (he/him)]

(In reply to Jared Hirsch [:_6a68] (please use 'needinfo' :-) from comment #4)
> Hey Dylan - I'm not sure about auto-redirecting, I was thinking of just
> exposing the same warning notice that's shown when you open the new bug form
> for the AMO component, see comment 3 for a screenshot.

AMO is a product, not a component. The special casing we do for that would only work for an entire product,
e.g. "Cloud Services".

Would it be appropriate to add the components now, and then add the warning/notice after?

Comment 6

[Jared Hirsch [:jhirsch] (he/him) (Needinfo please)]

Hi Dylan - Ah, I see. Is there any other way we could notify people that most bugs belong on Github? A bug template, maybe?

Comment 7

[Dylan Hardison [:dylan] (he/him)]

(In reply to Jared Hirsch [:_6a68] (please use 'needinfo' :-) from comment #6)
> Hi Dylan - Ah, I see. Is there any other way we could notify people that
> most bugs belong on Github? A bug template, maybe?

It's all the same, it requires a minor code change and a push. I can probably get such a change out tomorrow.

Comment 8

[Jared Hirsch [:jhirsch] (he/him) (Needinfo please)]

That sounds great, thank you!

Comment 9

[Dylan Hardison [:dylan] (he/him)]

Figuring out how to do this for components is a rather complicated UX matter, and I think definitely needs to be split off into a new bug. Should I just create the component now, or make it block on the component description bug (yet to be filed)?

Comment 10

[Jared Hirsch [:jhirsch] (he/him) (Needinfo please)]

> Figuring out how to do this for components is a rather complicated UX matter, and I think definitely needs to be split off into a new bug. Should I just create the component now, or make it block on the component description bug (yet to be filed)?

Ah, ok. I probably don't want to create the component without some kind of warning. We are trying to avoid bugs getting filed in two places.

Is there any way we could include a bug template that warns people to file regular bugs on github?

Comment 11

[Emma Humphries ☕️🎸🧞‍♀️✨ (she/they) [:emceeaich] (Pacific Time) use needinfo]

Jared, we're going to make a new bug around redirecting opening bugs to GitHub (and other trackers) but for now the best thing to do is create the component, and as bugs are filed, close them as incomplete and open them on GitHub, using the "see also" field to link to the bug in Issues. 

We don't have the ability to create a bug template as exists on GitHub. 

If the volume of bugs coming in this route becomes unacceptable, we can revisit.

Comment 12

[Emma Humphries ☕️🎸🧞‍♀️✨ (she/they) [:emceeaich] (Pacific Time) use needinfo]

I've created both components with the additional description, "Please file other bugs under https://github.com/mozilla-services/screenshots/issues. Non-security or release management bugs filed here will be closed as incomplete and moved to GitHub Issues."

Comment 13

[Jared Hirsch [:jhirsch] (he/him) (Needinfo please)]

Sounds great, thank you!