►
From YouTube: UX Overview for Group Environments Page
Description
See more at https://gitlab.com/gitlab-org/gitlab/-/issues/241506/
A
Hey
everyone:
this
is
daniel,
I'm
the
senior
designer
on
the
release
team
and
this
video
is
a
quick
overview
of
our
current
and
newest
design
proposal
for
the
group
environments
page
to
give
a
quick
context.
Context
on
this.
For
those
who
don't
know
the
group
environments
page
is
part
of
a
bigger
epic
to
share
production
environments
across
projects
within
a
gitlab
group.
So
the
idea
here
is
to
make
an
interface
that
would
allow
our
customers
to
see
all
of
the
environments
and
all
of
the
deployments.
A
There
are
part
of
the
projects
within
one
given
group
as
a
whole
at
a
high
level.
This
is
mostly
useful
for
tracking
all
production
environments
at
once.
So
this
is
the
focus
of
this
proposal,
but
it's
not
the
only
thing,
that's
part
of
it,
so
the
current
proposal
that
we
have
right
now
on
the
issue
is
this:
you
have
an
entry
point
on
the
group
navigation
here
deployments
and
group
environments
from
there.
You
would
get
to
this
page
that
if
you
have
more
than
one
shared
or
group
environment,
it
would
give
you
a
list.
A
If
you
only
have
one,
it
will
take
you
straight
to
the
one
you
have,
but
the
important
part
here
is
that
you
have
a
button
right
to
create
your
new
group
environment,
your
new
shared
environment
or
where
you
would
essentially
choose
a
name
and
a
tier
and
a
tier
is
a
deployment
tier.
It's
a
metadata
that
is
attached
to
an
environment
that
can
be
attached
to
an
environment
that
describes
what
type
of
environment
it
is
right.
A
We
have
a
few
tiers,
so
some
of
them
are
production,
development,
testing,
staging
and
others
as
well
other
kind
of
tier,
and
once
you
get
into,
let's
say
the
production
group
environment,
it
would
show
you
the
name
which
tier
it
refers
to
then
how
many
projects
are
in
there
and
then
one
of
two
views
right.
These
are
ongoing
proposals.
We
have.
A
One
of
them
is
this
view
where
it's
the
deployments
are
organized
per
project,
so
here
within
the
gitlab.org
organization
for
environments
that
have
production
tier,
we
have
the
give
that
project
with
these
deployments
into
production
and
then
these
other
projects,
which,
if
you
expand
them,
they
would
also
show
other
deployments
to
production.
And
here
you
can
see
these
could
be
part
of
different
environments,
but
these
are
all
to
the
same
environment
called
main,
whose
tier
is
production.
That's
why
it
is
listed
here.
A
A
secondary
view
that
could
also
be
adopted
is
just
this
plain
view
that
shows
all
the
deployments
regardless
of
project.
It
shows
the
project
here
right.
It
has
an
organization,
it
shows
the
the
group
and
then
the
project,
but
the
group,
the
project,
sorry,
is
then
just
a
metadata
that
is
part
of
the
deployment,
and
here
again
you
can
see
the
environment
with
the
tier.
The
the
relevant
thing
about
this.
This
proposal
that
I
want
to
discuss
is
the
fact
that
these
shared
environments
in
this
proposal
have
to
be
created
right.
A
We
could
just
go
with
creating
one
for
production
for
the
production
tier
and
that's
the
only
one.
You
have
that's
that's
a
valid
proposal,
but
you
know.
Maybe
you
also
also
want
to
track
all
of
your
deployments
to
staging
and
see
how
that
is
going
across
your
group.
So
we
give
the
possibility
of
creating
a
shared
environment
that
has
a
tear
and
has
a
name.
A
So
all
of
this
context
was
for
me
to
show
a
secondary
proposal
that
I
think
it's
much
more
interesting
for
the
needs
of
this
this
issue.
So,
let's
start
from
the
same
place
here
in
the
group
page,
so
we
would
go
into
deployments,
but
when
we
go
into
deployments
we
don't
go
into
a
list
of
group
environments.
A
Rather
we
go
into
a
flat
list
of
every
single
deployment
that
is
targeting
that
group
within
gitlab.org
for
all
of
its
projects
that
have
a
tier
right.
It
could
be
production,
it
could
be
staging,
it
could
be
development,
it
could
target
any
tier
and
then
from
here
you
have
this
bar
with
different
filters
where
you
can
choose
which
tier
you
want
to
see.
So,
if
indeed
it
is
your
job
to
look
at
all
the
deployments
to
production,
you
can
just
filter
by
production.
These
would
be
saved
to
a
url.
Just
like
a
issue.
A
Search
with
filters
is
also
saved
to
the
url,
and
then
you
can
bookmark
that
you
can
share
it
with
your
team,
all
of
that,
but
it
also
gives
you
other
options
right.
So
if
we
come
back,
you
could
finish
by
statuses,
so
you
want
to
see
every
failed
deployment.
You
filter
by
that.
You
want
to
see,
what's
currently
running
your
computer
by
that,
if
it
is
your
job
to
approve
deployments,
you
could
also
filter
by
the
ones
that
need
approval.
A
So
you
see
a
neatly
organized
list
of
everything
that
needs
approval
and
then
go
one
by
one.
If
that's
what
you
want,
we
could
also
filter
by
project.
So
if
there
is
a
group
of
three
or
four
projects,
you
want
to
keep
an
eye
on,
you
could
also
filter
by
that,
and
we
can
have
additional
view
options
here.
So
the
the
list
grouped
by
project
could
also
be
present
here,
as
a
setting
that
you
turn
on
and
off.
A
Lastly,
sorting,
if
you
want
to
order
by
finish
date
by
creation
date
by
environment
name,
I
don't
know
just
having
this
possibility
and
then
expanding
the
different
ways
to
slice
this
data
based
on
user
feedback
and
and
what
users
ask
for.
I
think
it
would
be
a
very,
very
good
direction
for
us
to
take
this
proposal.
So
let
me
know
what
you
think
and
let's
keep
discussing
in
the
comments
thanks
for
watching.