Hi all. A concept for a feature under BugId 359251

[Leon KUKOVEC]

Hi,

My initial idea was to change the DB schema a bit in order to achieve
the grouping as Charlie
was suggesting. After a bit of thinking and seeing that we're already
using e-mail lists in CC field at work - meaning the e-mail
lists are already registered as login_names - I thought reusing
that approach. As a result, a non standard, but doable idea came up
which gives the flexibility to use e-mail list as a part of 'asignee',
'qa', or 'cc'
and should not be that hard to do.

If we focus only on allowing 'BZ groups' in CC field
I support the idea of going 'standard' way and am open to suggestions.

On Jul 9, 5:34 pm, Max Kanat-Alexander <mka... at bugzilla.org> wrote:
> Guy Pyrzak wrote:
> > One problem with that idea is that you kinda break the point of using a
> > group and just turn it into a fast way to get a list of names. The
> > primary use case you'd be breaking is someone new joining a group and
> > then having no way to add them to all the bugs that the group is cc'ed on.
>
>         Well, you could maybe have a group_cc table, and then when $bug->cc is
> called, expand the groups into users. We could then have $bug->cc_users
> and $bug->cc_groups for the unexpanded versions.
>
>         -Max
> --http://www.everythingsolved.com/
> Competent, Friendly Bugzilla and Perl Services. Everything Else, too.
> -
> To view or change your list settings, click here:
> <http://bugzilla.org/cgi-bin/mj_wwwusr?user=dev-apps-bugzi...@lists.mozilla.org>

_______________________________________________
dev-apps-bugzilla mailing list
dev-apps-bugzilla at lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-apps-bugzilla