Cross-functional groups

Gervase Markham

unread,

Apr 13, 2015, 2:54:23 PM4/13/15

to mozilla-...@lists.mozilla.org

See https://bugzilla.mozilla.org/show_bug.cgi?id=1112623 , and pir's
explanation of the Infrastructure and Operations workflow, and why they
make everyone move their bugs into I&O components.

Could BMO solve this problem (a group which acts cross-functionally, and
has its own tracking mechanisms, but ideally wouldn't disturb the
mechanisms of those it works with) better?

Gerv

Byron Jones

unread,

Apr 14, 2015, 1:04:03 AM4/14/15

to mozilla-...@lists.mozilla.org

you've described the use-case for component watching's "watch user" feature.

to use it cc your component's watch-user to a bug you file in another
component.

in that bug's case i would move it into the infra component, and cc
discussi...@mozilla-org.bugs. anyone watching the
discussion-forums component will receive notifications for that bug.

--
byron jones - :glob - bugzilla.mozilla.org team lead -

Gervase Markham

unread,

Apr 14, 2015, 8:56:52 AM4/14/15

to mozilla-...@lists.mozilla.org

On 14/04/15 06:03, Byron Jones wrote:
> you've described the use-case for component watching's "watch user"
> feature.
>
> to use it cc your component's watch-user to a bug you file in another
> component.
>
> in that bug's case i would move it into the infra component, and cc
> discussi...@mozilla-org.bugs. anyone watching the
> discussion-forums component will receive notifications for that bug.

That might work for us if I switch to Component Watching that component,
but I'm not sure this solves the more general problem.

I&O work across the project. Say someone files a bug in the Firefox
product which requires work from an I&O person. They require it to be
moved over to their product - but then, all the Firefox-related tracking
UI is (AIUI) no longer visible. Repeat for ten different products and
product groups, all with their own workflows.

Yes, someone could CC gen...@firefox.bugs, but only people whose method
of consuming Firefox-related bugmail was Component Watching, would
continue to be notified about that bug. People who e.g. just searched
for bugs in the relevant components would not see it.

Gerv

Byron Jones

unread,

Apr 14, 2015, 11:20:29 AM4/14/15

to mozilla-...@lists.mozilla.org

Gervase Markham wrote:
> I&O work across the project. Say someone files a bug in the Firefox
> product which requires work from an I&O person. They require it to be
> moved over to their product - but then, all the Firefox-related tracking
> UI is (AIUI) no longer visible. Repeat for ten different products and
> product groups, all with their own workflows.

best solution for that scenario is for a separate i&o bug to be filed,
blocking the firefox bug. both teams can then track the bugs however
they want, and we don't need to add any more complexity to bugzilla.

Gervase Markham

unread,

Apr 15, 2015, 6:07:03 AM4/15/15

to Byron Jones

On 14/04/15 16:19, Byron Jones wrote:
> best solution for that scenario is for a separate i&o bug to be filed,
> blocking the firefox bug. both teams can then track the bugs however
> they want, and we don't need to add any more complexity to bugzilla.

Yes, we could do that. Although two bugs seems overkill for the creation
of a discussion forum.

Gerv