►
From YouTube: GitLab 15.8 Kickoff - Monitor:Respond
Description
Monitor:Respond 15.8 Planning Issue: https://gitlab.com/gitlab-org/monitor/monitor/-/issues/178
A
Hi
I'm
Elena
Bellucci,
and
this
is
the
monitor,
respond,
15,
8,
kickoff
call
our
two
goals
for
this
Milestone
are
to
continue
to
work
on
a
production-ready
slack
app
for
Incident
Management.
We
have
something
released
that
is
behind
a
feature
flag,
but
it
is
not
quite
ready
for
users
to
use
it
if
it's
there.
A
If
you
want
to
test
it
and
play
around
with
it,
but
we
are
working
to
make
sure
that
it
is
something
that
will
be
really
useful
for
you
and
I'll
go
into
those
issues
that
we're
going
to
be
working
on
this
Milestone
and
with
the
holidays
coming
up
the
end
of
year,
it's
important
to
take
some
time
to
feel
rested
and
refreshed
and
enjoy
the
holidays
and
enjoy
the
new
year.
Let's
dive
in
and
talk
about
what
we're
going
to
be
working
on
this
milestone.
A
So,
like
I
mentioned,
we
are
working
on
the
slack
app
for
Incident
Management,
and
this
Milestone
will
add
the
ability
to
add
specific
slack
channels
where
users
can
point
to
point
their
incidents
to
so
if
they
do,
if
they
declare
an
incident,
it
goes
to
a
specific,
select
Channel,
as
opposed
to
any
updates
that
were
are
available
for
issues
again.
Incidents
are
just
a
issue
type
and
we
want
to
make
sure
that
those
are
pointed
to
a
specific
slack
channel.
A
In
addition,
we're
going
to
be
working
on
slash,
commands
and
quick
actions
going
both
ways
between
gitlab
and
slack.
So
here
is
an
example
of
what
an
update
would
look
like
coming
from
gitlab
and
then
being
pushed
to
a
specific
SPAC
Channel
and
then
in
git
and
slack.
This
is
what
would
happen
if
a
user
wanted
to
say
something
in
slack
and
then
push
it
to
as
a
specific
comment
on
an
incident
in
gitlab
also
really
exciting.
A
We
are
starting
the
technical
breakdown
for
the
Post
incident
review
MVC,
so
Amelia
did
a
great
job
of
doing
some
solution.
Validations
we've
done
a
problem,
validation
around
post-incident
reviews
and
she's,
designed
something
really
great
I'd
like
to
highlight
some
of
those
features,
but
again
this
Milestone.
We
are
just
doing
the
technical
breakdown.
A
So
let's
take
a
look
at
some
of
the
things
that
are
coming
with
that
post
incident
review.
There
will
be
a
place
in
settings
where
users
will
be
able
to
enable
a
post
incident
review.
They'll
also
be
able
to
create
a
default
template
and
add
the
ability
to
automatically
create
post-incident
reviews
after
they
close
an
S1
incident
within
a
incident
itself.
A
When
the
issue
is
closed,
if
that
again,
if
that
toggle
isn't
turned
on,
users
will
have
a
button
where
they
can
create
the
post
incident
review
for
any
closed
incident,
and
then
they
can.
Also,
if
that
posted
review
is
created,
they
can
view
the
post
incident
review
if
there
is
a
post
incident
review
associated
with
that,
and
then
lastly,
and
also
still
very
important,
we
have
added
a
section
to
our
planning
issue
called
seeking
Community
contributions.
A
So
these
are
groomed
issues
that
we've
identified,
that
we
would
love
Community
contributors
to
consider
they're
broken
down
by
front
end,
and
then
we
have
some
back
end
issues
and
within
each
of
these
we
will
have
an
implementation
guide,
so
you
could
quickly
and
more
easily
get
started
to
help
us
fix
some
of
these
things
or
add
some
of
these
features.
So
that
is
what
we
have
planned
for:
15
8
and
have
a
wonderful
New,
Year
and
a
happy
holidays.
Thank
you.