►
From YouTube: GitLab 13.8 Kickoff - Manage
Description
Larissa, Melissa, Matt, and Haris talk about what's ahead for Manage in 13.8.
- Manage:Optimize - 0:33
- Manage:Access - 11:30
- Manage:Compliance - 18:57
- Manage:Import - 22:22
Agenda and issue links available at https://docs.google.com/document/u/1/d/e/2PACX-1vRnN91k9Rx1AyF8cIQga3KGFpjkI-sheTB16Jg-4e8fO3snZas2Th4hJC5C5wKIrNWbzr8aYDjI-T7-/pub
A
Hey
everyone,
I'm
jeremy
watson,
I'm
a
group
manager
here
at
git
lab
we're
here
together
as
the
managed
stage
kicking
off
13.8,
releasing
january
22nd
2020.,
I'm
joined
by
larissa,
melissa,
matt
and
harris,
and
we're
going
to
run
through
our
stages
and
kind
of.
What's
ahead
in
13,
8.,
larissa
you're
going
to
be
talking
a
little
bit
about
the
optimize
group
and
what
you
all
are
working
on
love
to
hear
more
over
to
you.
B
Okay,
so
we're
going
to
take
take
this
time.
The
13.8
milestone
goes
over
the
holidays,
so
we
have
a
bit
smaller
capacity
and
scope
and
we're
going
to
be
focusing
on
some
usability
improvements
and
wrapping
some
things
up
that
we've
been
working
on
so
the
first
one
I'm
going
to
cover
is.
We
are
continuing
to
work
on
the
user
busy
status
and
made
good
progress
in
137
on
this.
So
now,
if
you
go
into
edit
status,
you'll
see
the
busy
check
box
there.
As
of
13
7.
B
B
B
So
you
can
see
it
appear
here,
we're
adding
that
to
a
few
other
places
that
we
think
this
is
going
to
be
really
useful
when
you're
assigning
an
issue.
So
we'll
also
be
adding
that
busy
status
over
here
when
you're
selecting
an
assignee
for
an
issue
and
now
also
we'll
be
enabling
this
by
default
in
13
8.
So
in
13
8,
everyone
will
be
able
to
see
the
busy
status
check
box
and
have
that
show
up
throughout
the
ui.
B
B
B
B
B
B
And
finally,
on
devops
table
right
now,
when
you
look
at
this
data,
you'll
be
getting
data
from
the
last
calendar
month.
So
if
my
api
development
team
was
creating
mrs
in
the
last
calendar
month,
this
will
be
filled
in.
We
want
to
make
that
data
more
up-to-date,
so
we'll
be
adding.
We
will
be
fetching
that
data
daily
and
showing
for
the
current
calendar
month,
which
features
have
been
used.
B
B
So
the
first
step
we're
taking,
is
to
remove
cohorts
from
this
list
of
analytics
we're
going
to
leave
that
in
the
admin
page
for
now,
and
that
will
be
under
overview
users
and
then
we'll
be
able
to
as
a
next
iteration
after
that
move
the
devops
reports
and
the
usage
trends
out
from
the
admin
page
and
for
now
we're
thinking
about
putting
that
back
in
the
more
menu
until
we
have
a
better
solution.
But
I
think
melissa's
going
to
talk
about
where
we
might
be
going
with
the
navigation
for
admin.
Page.
A
A
A
When
you
showed,
when
you
showed
off
the
issues
view,
you
showed
off
that
the
fact
that
you
could
click
on
an
assignee
and
then
you
could
see
the
busy
status
next
to
that
assignee's
name.
But
that
was
in
the
issues
view.
I
was
just
curious
if
we
had
something
similar
for
the
merge
requests
view
so
that
a
merge
requester.
When
the
merge
request
author
can
assign
the
merge
request
to
someone
and
then
visibly
see
that
that
person
is
busy.
A
C
Yeah,
I
was
thinking
along
the
same
lines-
jeremy
as
you,
so
where,
where
else
would
I
like
to
see
this
so
definitely
plus
one
on
being
able
to
see
it
wherever
I
see
people
selection
that'd
be
useful,
so
hopefully
just
updating
the
component
would
give
us
some
of
that
for
free.
I
was
also
curious,
like
would
those
statuses
be
customizable,
or
would
it
be
just
a
set
of
instead
of
standard
statuses,
or
is
it
just
busy
like
what
is
the
big
level.
D
Oh,
I
just
wanted
to
say
that
the
concept
of
segments
is
really
interesting
and
I'm
excited
to
see
where
that
goes
further.
Even
outside
of
you
know
optimize
because
I
know,
for
example,
in
the
recent
usability
feedback
for
groups
and
projects.
Specifically,
it
came
up
that
people
just
have
a
hard
time
finding
the
things
that
they
need
and
one
suggestion
that
came
it
came
up
was.
D
B
Yeah,
I
think
that's
a
really
good
point.
It
could
be
something
that
we
use
throughout
other
features
as
well
for
now
we're
limiting
it
to
just
a
combination
of
top-level
groups,
but
what
one
vision
we
had
was
to
add
any
combination
of
subgroups
or
any
combination
of
projects,
so
it'd
be
really
interesting
to
see
what
use
cases
come
out
for
that.
A
C
Sorry,
sorry,
one
quick
comment
that
was
spread
by
what
was
just
what
melissa
brought
up,
and
that
is
I've
known
from
other
tools
in
previous
life
that
customers
do
like
to
put
together
programs
which
is
kind
of
a
set
of
random
projects
put
together.
So
just
be
able
to
put
you
know
this
and
this
and
it's
not
any
kind
of
a
tree,
and
it's
just
like
these
are
the
things
that
I
work
on
so
my
portfolio
and
they
would
call
that
a
program
and
I
think
that's
even
a
thing
in
safe.
A
Yeah
you're
so
right
and
that's
why
I
think
we
need
to
take
our
time
with
it.
We
wanted
to
start
small
before
we
go
a
little
further,
because
we're
gonna
have
to
take
this
concept,
make
sure
that
it
works
for
plan
that
works
for
manage
it
works
for
other
stages.
So
I
think
we'll
move
slowly
here,
but
once
we
have
a
direction
we'll
make
it
available
to
everyone,
I
think
so,
but
yeah,
that's
that's
a
great
point
program
management.
A
D
All
right,
let
me
share
my
screen,
so
we
also
have
limited
availability.
I
would
say
this
next
milestone,
just
because
a
lot
of
team
members
are
taking
time
off,
so
we're
focusing
on
a
couple
of
issues
and
then
some
pocs
around
big
strategic
items
that
we're
going
to
be
working
on
the
following
milestone.
D
So
the
first
issue
that
we're
working
on
is
a
continuation
of
our
work
on
group
web
hooks.
So
our
mvc
that
launched
this
milestone
was
around
emitting
events.
Whenever
members
were
added
to
a
group-
and
we
took
that
very
small
nvc,
because
there
was
actually
quite
a
lot
of
refactoring
that
had
to
be
done
to
enable
true
group
level
events.
D
To
just
do
things
like
add
them
to
other
groups,
change
their
role,
etc,
and
so
now,
instead
of
calling
the
api,
they
can
just
wait
for
an
event
from
a
web
hook
to
trigger
their
automation.
So
this
will
be
great
for
performance
and
and
just
eliminating
unnecessary
api
calls,
and
this
is
something
that
I've
heard
from
quite
a
few
enterprise
customers
that
they
have.
You
know
a
lot
of
custom
business
logic
that
they
want
to
run
based
on
members
being
added
to
a
group.
D
D
It's
really
easy
to
accidentally
turn
on
enforcement
and
not
realize
that
you
have
a
mistake
in
your
configuration
and
then
they
effectively
lock
themselves
out
of
their
group
and
they
have
to
call
support,
and
you
know,
have
them
do
something
kind
of
embarrassing,
but
I'll
show
you
guys.
Support
has
been
documenting
every
time.
D
So
it's
a.
We
picked
something
very
small
which
was
just
the
boolean
value
of
delayed
project
deletion,
which
is
a
setting
that
applies
exists
today
at
the
project
level,
but
there's
no
way
to
sort
of
default
it
at
any
level
higher.
So,
basically,
if
somebody
wants
to
set
a
specific
value,
they
have
to
go
through
all
projects
and
settings
and
there's
a
value
at
the
group
level
too.
D
D
So
this
is
going
to
be
a
poc
right.
So
engineering
is
going
to
work
on
defining
the
approach
for
this
and
then,
at
the
end
of
this,
we'll
have
a
roadmap
for
building
this
framework
that
not
only
the
access
team
can
use,
but
the
vision
is
that
any
team
that
wants
sort
of
like
a
collection,
managing
collections
of
groups
and
and
settings
for
them
and
features
for
them
can
use
this
framework.
D
So
super
excited
for
this
and
the
other
one
is
around
what
we're
calling
policies,
but
really
it's
the
beginning
of
moving
toward
having
custom
roles
so
being
able
to
toggle
on
and
off
specific
specific
behaviors.
So
now
we
have
predefined
roles
right
and
there's
predefined
actions
that
each
of
them
can
or
can't
do
so.
We
want
to
provide
more
flexibility
in
that,
because
not
every
customer's
workflow
is
the
same
right.
D
People
want
different
levels
of
of
action
and
it's
sort
of
an
expectation
from
tools
today
that
you,
you
are
able
to
create
your
own
custom
role
to
do
whatever
you
feel.
Users
should
be
able
to
do
the
first
action
that
we're
going
to
experiment
with
is
member
management
today,
because
of
how
our
roles
work.
D
If
you
want,
because
they're
not
very
flexible
what
people
end
up
doing,
is
giving
more
people
than
they
would
like.
Maintainer
access
just
so
they're
able
to
do
everything
that
they
need
to
in
their
job,
but
one
gap
with
that
is
that
if
you're
a
maintainer,
then
you
can
make
other
people
maintainers
right,
which
kind
of
takes
away
the
administrative
aspect
of
controlling
like
people's
roles.
A
Nice,
no,
I'm
excited
about
policies.
I
mean
thank
you
for
prioritizing
that
it's
going
to
be
a
huge
improvement
and
usability
improvement
for
our
customers,
and
I
just
wanted
to
say
thanks
for
proceeding
with
the
web
hook
improvements.
I
think
it'll
also
be
helpful
for
our
customers,
but
it'll
also
take
a
lot
of
pressure
off
of
gitlab.com.
So
that's
that's.
What
I'm
really
excited
about
cool
matt
over
to
you
to
talk
compliance.
E
Cool
thanks
before
we
go,
I
just
want
to
say
melissa.
I
am
really
interested
in
following
that
cascading
issue
in
particular
as
you're
well
aware:
yes,
100,
cool
all
right
so
for
the
compliance
group,
given
the
same
capacity
issues,
everyone
else
has
mentioned.
We
have
a
light
load
for
this
milestone,
but
a
couple
of
really
important
ones,
so
we'll
be
finishing
up
the
user
access
report
so
in
the
admin
users
view
providing
an
export
option
to
pull
down
a
list
of
all
the
users
along
with
their
group
and
project
memberships.
E
We
were
originally
going
to
show
all
of
the
inherited
memberships
as
well,
but
ran
into
some
tactical
challenges
there,
which
is
partly
why
this
is
carrying
over
to
13.8.
But
we
do
expect
this
to
ship,
at
least
with
this
mvc
and
that'll
satisfy
this
major
pain
point.
We
hear
from
customers
a
lot
around
that
central
theme
of
getting
data
out
of
git
lab
and
into
their
business
logic,
systems
into
the
hands
of
their
internal
or
external
auditor,
hands,
etc.
E
So
the
other
one
that
I'm
really
excited
about
because
as
everyone
on
this
call
knows,
I've
been
just
like
killing
myself
over
the
last
several
months
trying
to
ship
this.
But
it
ties
into
the
concept
of
group
level,
compliance
pipelines,
and
so
in
order
to
facilitate
this
concept
of
the
required
pipeline
configuration.
E
E
And
it
creates
the
link
between
the
centrally
managed
configuration
and
that
local
ciamel,
but
baits.
So
so
these
two
issues
that
we're
shipping
in
thirteen
eight
are
tied
to
that
solution
and
it's
probably
a
thing
I'm
most
excited
about,
because
I
know
that
there's
a
litany
of
enterprise
customers
just
waiting
for
this.
We
have
some
other
stuff
that
we're
covering
in
this
milestone
that
are
mostly
backstage
improvements
as
well,
but
I
would
say
that
that's
probably
the
highlight
for
me
or
these
two.
A
I
mean
I'm
giddy
too.
That's
all
I
wanted
to
say,
like
I
couldn't
be
happier
to
see
these.
These
improvements
like
finally
scheduled
and
like
they're,
a
combined
weight
of
four,
which
makes
me
like
even
more
static,
because
they're
they're
we've
shaped
them
to
like
really
small
issues,
they're
going
to
be
huge
for
our
customers,
and
I
know
that,
like
some
very
heavy
hitters
have
been
asking
for
this,
and
I
am
like
over
the
moon
that
we're
going
to
be
able
to
move
forward
with
this.
So
thanks
a
lot
for
your
amazing
leadership
here.
C
We
have
about
half
capacity
available
and
we
have
a
good
amount
of
support,
work
and
escalation
work
that
just
happens
all
the
time,
so
we've
kind
of
planned
somewhat
conservatively
this
time
around.
What
I
want
to
talk
about
is
where
we're
going
in
13,
8
and
then
beyond
for
39
as
well.
So
a
lot
of
this
will
apply
sort
of
past
13a
as
well.
C
In
137,
we
are
delivering
a
an
mvc
for
the
gitlab
group
migration,
which
allows
the
user
to
connect
to
another
instance
of
gitlab
and
import
one
or
multiple
groups
over
without
having
to
download
the
file
without
having
to
upload
the
file.
So
that's
that's
gonna
be
really
useful.
It's
been
something
that
our
users
have
been
asking
about,
and
also
something
that
is
going
to
improve
our
stability
and
our
support
ability
for
for
importing
from
gitlab
to
gitlab.
C
So
as
a
follow-up
to
that,
we've
done
some
early
ux
research
and
gotten
some
feedback
on
things
that
were
really
important.
That
we
feel
should
should
be
there
sort
of
as
soon
as
we
can
one
is
is
this:
you
know
as
as
easy
as
kind
of
simple
as
it
looks.
This
is
really
important.
So
the
you
know,
users
were
very
confused
about
what
this
new
group
migration
actually
does,
which
objects
and
entities
do
transfer.
C
This
is
a
feature
that
we've
just
started
and
we're
developing
and
it's
in
no
way
complete,
because
we
don't
want
to
create
that
impression
that
it
does
more
than
it
does,
and
then
you
know
kind
of
have
this
dissatisfaction
and
have
that
first
impression
be
not
a
great
one.
So
we
are
putting
a
warning
there
that
tells
the
user
that
not
everything
is
getting
migrated
this
time
and
here's
a
list
of
you
know
things
that
is,
and
we're
also
using
this
opportunity
to
leave
a
feedback
link.
C
C
In
addition
to
that,
we're
introducing
the
concept
of
of
just
the
beta
badge
for
the
feature,
while
it's
in
progress,
so
all
of
this
communication
will
be
removed
when
we,
when
we
reach,
when
we
get
to
the
level
to
where
you
know,
we're
delivering
what
people
expect
to
see
behind
the
feature,
but
for
now
we're
leaving
that
there.
So
this
is
a
quick
follow-up,
but
it
feels
very
important
because
without
this
we're
going
to
create
some
bad
first
impressions.
C
The
other
follow-up
was
also
kind
of
a
clarifying
confusion
that
we
had
on
the
on
the
page
where
we
listed
groups
where
users
were
not
sure
if
the
groups
that
are
listed
here
are
all
the
groups
that
they
can
see
all
the
groups
that
exist,
whether
they
can
or
cannot
import
them.
Like
everybody,
has
a
different
question
about
what
it
is
and
it
feels
like.
C
In
addition
to
working
to
to
getting
some
of
these
ux
issues
in,
we
do
have
some
non-functional
requirements
that
will
improve
scalability
resilience,
efficiency
usability.
So
it's
like
there's
a
set
of
technical
issues
that
were
discovered
during
the
mvc
that
we're
going
to
need
to
place
sooner
or
later.
We're
going
to
use
this
time,
and
this
kind
of
transitional
milestone
between
two
larger
features.
C
We
currently
have
three
metrics
that
added
together,
you
know,
track
track
our
usage
and
we
need
to
go
back
and
make
that
one
metric,
that's
easy
to
see
and
easy
to
report
off
of
and
finally
the
stretch
goal,
we
are
going
to
be
refining
some
issues
within
the
epic
that
is
next
up
for
the
group
migration
and
our
next
goal
is
parity
with
the
group
export
imports.
So,
with
the
completion
of
this
epic,
we
hope
to
have
a
viable
feature
that
will
do
all
the
same
things
that
the
current
group
export
import
does.
C
That
is
going
to
change
the
dynamic
on
how
we
and
how
we
engage
and
invest
in
this
feature,
because
we're
going
to
have
to
we're
going
to
be
able
to
stop
maintaining
the
feature,
currently
exists
and
take
it
off
the
docket,
and
that
should
speed
up
the
our
ability
to
to
deliver
the
new
feature
which
will
eventually
replace
both
the
group
export
import.
As
well
as
the
project
export
import,
but
then
go
beyond
that,
so
it
will
do
things
that
the
current
group
export
import
and
project
export
import
cannot
do.
C
We
will
be
able
to
get
there,
but
on
the
way
there
we're
going
to
be
actually
deprecating
and
taking
some
of
the
existing
features
out,
because
they
will
no
longer
be
needed.
So
that's
that's
the
goal.
So
the
goal
for
this
for
13
8
is
really
to
just
do
refinement
on
this
and
make
sure
that
we're
ready
to
start
picking
up
issues
from
here
in
thirteen
nine
jeremy
had
the
first
question.
A
C
I
think
I
think
we
should
be
able
to
remove
the
beta
when
we
deliver
this
epic,
so
when
we
get
to
viable
and
we
get
to
being
able
to
have
on
par
kind
of
a
feature
set
between
the
the
file
based
group,
export
import
and
the
new
group.
Migration
is
when
this
is
out
of
beta
until
it
actually
does
less
than
the
existing
functionality.
I
think
I
would
leave
that
that
warning
there
just
to
make
sure
that
we
create
correct
expectations.