1473241 - Remove default CC

Status: NEW

(bugzilla.mozilla.org :: General, task)

Description

[Kohei Yoshino]

Once Bug 1472954 is landed, Component Watching will be very handy, just one click of a button on the bug page. As Emma said on Twitter, the default CC functionality can be removed now.

* It’s difficult to maintain the list, increasing the workload of admins

* It’s also a UX issue: people (even me) may be confused to see someone automatically added to the CC list especially when moving a bug to another component

Comment 1

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

For the second point, you'll still have global watchers and people that watch nobody. I think for the second point it might be better to just add a hint why someone received an email.

Comment 2

[Mark Clements]

(In reply to Kohei Yoshino [:kohei] (Bugzilla UX) (FxSiteCompat) from comment #0)

Once Bug 1472954 is landed, Component Watching will be very handy, just one
click of a button on the bug page. As Emma said on Twitter, the default CC
functionality can be removed now.

Please, please, please do not remove this functionality! It is vital for enterprise use. It is not feasible to expect new staff members to have to manually 'watch' every relevant component, particularly as they will not know enough to know which are the relevant components until they've been here for at least a few weeks.

The UI for managing default components is a pain - it should be made a lot easier to setup new staff members and remove old ones. A user-centric editing interface would be better than the current component-centric interface (e.g. by making the list on the user edit page directly editable) and the ability to remove a user from all components would also be a great help for when staff members leave. It would also be great if it were possible to set up a default CC list for a Product, so you don't need to do this for every component (only for those which need a different list to the product default).

So, yes, I agree that there are improvements to be made.

However, as a feature this has very strong use-cases for non-public Bugzilla installations, and should not be removed simply because it is not needed on large community-driven Bugzilla installs.