In many use-cases, there is a set of jobs which have various configuration
parameters in common. E. g. notifiers, permissions, JDK, etc.
Similar to Project Groups in Continuum, it should be possible to configure those
parameters on a group-level, and assign jobs to a group.

Currently, Hudson offers the view-feature. A view is simply a perspective on a
set of jobs, but there is no way to assign properties to the view which are
common for all jobs belonging to this view.

One could say, ok, let's extend the view in the way that it is possible to
assign properties to it. However it won't work out that way, as a project can be
assigned to multiple views. The configuration of which view should win in such a
case?

So, apparently, Hudson needs a new grouping feature that is either distinct and
complimentary to the view-concept or else replaces the view. In my opinion, it
should replace the view-feature.

Let's call it project-group. A project-group replaces the view by providing two
major differences:
1) a project may be a member of one project-group only (not multiple)
2) a project-group provides various properties that are shared among the
projects belonging to this project-group

Furthermore, a logic is necessary to decide if group-values should overwrite
project-values, or vica versa.
I propose that a project assigned to a project-group offers the value "use
project-group value" for all of the properties that are available in the
project-group configuration.