►
From YouTube: 12.3 Release Kickoff: Manage
Description
Jeremy and Virjinia discuss what's in store for Manage in 12.3.
Please share your feedback by following the links in our Kickoff document: https://docs.google.com/document/d/1ElPkZ90A8ey_iOkTvUs_ByMlwKK6NAB2VOK5835wYK0/edit#heading=h.x6m3oc1e4wun
A
Hey
thanks
a
lot
for
joining
us
for
the
tool
belt,
dirty
kickoff,
I'm,
Jeremy
and
I'm
joined
by
Virginia.
Both
probably
managers
hurry
get
loud,
representing
and
manage
things
about
life
cycle.
I've
got
a
lot
of
really
exciting
improvements
in
store
for
you
in
this
release,
specific
to
Analytics
configuration
compliance
and
more
and
Virginia's
gonna
kick
us
off
by
talking
through
two
really
awesome
improvements
of
the
insights
that
we
delivering
gitlab.
Thanks
to
our
analytics
features
Virginia
over
here,
Thank.
B
You
Jeremy
I'm,
starting
with
our
one
of
our
issues
from
the
major
management
world
map.
Some
of
you
remember
from
4.2
we
extended
psycho
analytics
to
multiple
projects
and
group
level.
We
decided
to
allow
for
the
extermination
of
the
different
stages
according
to
customers,
software
development
life
cycles
and
we
started
work
on
a
child
with
essentially
showcases.
Hopefully,
improvements
across
the
life
cycle
and
at
the
time
that
issues
and
merge
question
on
each
in
each
stage.
B
What
we're
going
to
do
during
12.3
is
shed
further
light
into
the
process
and
hopefully
help
with
the
problem
which
is
very
dear
to
us.
It
lab
as
well.
More
specifically,
we
want
to
help
the
prioritization
and
optimization
between
bugs
risks,
security,
risks,
technical
that
and
features
for
engineering
managers
and
allow
for
better
communication
and
discussions
between
them,
their
leadership
and
pro
managers.
We
also
essentially
have
a
community
flow
diagram
which
is
going
to
showcase
how
many
tasks
are
sitting
at
each
stage
on
a
particular
day.
B
Second
issue
that
we'll
be
working
on
will
be.
It
is
part
of
our
:
latex
roadmap
is
some
of
you
might
remember
from
in
12.2.
Our
first
issue
would
basically,
in
this
area,
was
focused
on
identifying
called
hotspot
because
code
stability,
general,
is
very
correlated
with
code
quality.
Another
issue
that
has
been
a
particular
interest
to
our
community
and
our
enterprise
customers
was
the
ability
to
visualize
the
number
of
lines
of
codes
contributed
across
different
languages
over
time.
B
So
during
4.3
we
actually
going
to
work
on
extending
this
functionality
on
the
project
level
and
hopefully
along
the
next
type
of
milestones
to
through
group
and
instance
level.
We
also
hope
that
by
connecting
these
two
groups,
some
of
the
other
analytics
that
we're
building
companies
are
going
to
be
able
to
measure
the
impact
code,
quality
and
velocity
across
time
by
deploying
different
over
to
you.
Jeremy
thanks.
A
A
lot
Virginia
and
that's
really
exciting
stuff
I'm
particularly
excited
for
the
work
type
distribution,
I,
think
being
able
to
see
the
issue
type
flow
over
time
is
going
to
lead
to
some
really
powerful
insights.
That
engineering
managers,
especially,
are
generally
benefit
from
so
I'm
going
to
talk
through
fight
issues
and
I'm
particularly
excited
about
I.
Think
of
the
first
three
are
really
related
to
compliance
and
and
how
we
can
get
to
maintain
oversight
over
what
users
are
doing.
A
Do
we
want
to
solve
this
problem
by
actually
creating
and
introducing
an
API
to
be
able
to
retrieve
audit
events
like
on
the
fly
and
be
able
to
query
an
endpoint
to
return
just
the
what
you
kind
of
like
what
this
enables
you
to
explore
things
a
little
bit
better
and
with
using
an
API
to
do
this,
and
also
to
type
that
into
like
an
SDI
M
system
like
Splunk
to
be
able
to
do
ongoing
model?
So
I
think
this
is
really
going
to
extend
the
ability
of
instances
to
understand.
A
What's
going
on
on
their
instance,
I
think
other
feature
that
I'm
really
excited
about
is
extension
of
like
IP
address
filter.
We
first
introduced
this
in
12.2
in
our
last
release,
but
it
was
restricted
to
a
single
IP
subnet
mask
as
well
as
the
UI,
and
what
we're
gonna
do
in
this
release
and
call
about
three:
is
we're
going
to
extend
that
restriction
beyond
just
the
UI
to
both
API
and
get
activity,
as
well
as
the
truce,
the
ability
to
specify
multiple
IP
subnets
using
a
comma
delimited
structure?
A
So
the
idea
here
is
that
if
you
go
ahead
and
apply
a
bolt-on,
subnet
mask
you'll
be
able
to
rely
on
this.
A
single
source
of
truth
in
terms
of
what
IQ
addresses
are
able
to
access
your
instance
both
and
the
UI,
but
as
well
as
for
any
KPI
and
good
activity
for
a
very
watertight
compliant
solution.
Also
related
to
this
set
of
problems
is
using
LDAP
lock.
A
A
The
last
thing
I'm
really
excited
to
talk
about
is
a
new
focus
on
imports
here
in
gitlab,
and
imports
are
particularly
important
for
us
because
it
helps
people
kind
of
get
started
with
the
product
and
on
board
their
existing
code
and
projects
into
the
application,
and
we've
actually
created
a
new
group,
the
import
group
or
the
help
move
more
quickly
in
this
area.
One
of
the
first
things
that
we're
going
to
start
with
is
the
ability
to
start
filtering
projects
in
our
existing
project
importer
tool,
we're
going
to
start
with
a
bit
Bukkit
server
importer.
A
But
this
is
a
pattern
we're
going
to
start
applying
to
all
of
our
importers.
You
can
see
it
kind
of
worked
here
in
this
gift
below
where
we
actually
are
able
to
list
out
number
of
projects
filter
exactly
what
we
want
to
and
string
in
the
upper
right
hand
corner-
and
this
allows
us
to
special
in
the
case
of
instances
with
hundreds,
if
not
thousands,
of
projects
to
just
import
the
projects
that
you
want
and
kind
of
cut
down
on
that
noise.
A
So
those
are
the
five
things
I'm
really
excited
about,
there's
plenty
more
on
the
way,
but
what
we
would
love
your
input,
your
feedback
and
contributions
on
are
those
issues
here,
so
you
can
feel
free
to
kind
of
click
into
these
issues
and
they're
12:3
kick-off
document
here
feel
free
to
click.
On
these
to
these
issues,
we
would
love
to
get
your
contributions
and
feedback
on
what
we're
doing
right.