►
From YouTube: UX Showcase: Incident Management to Complete
Description
Outline of improvements planned to ensure our internal teams can utilize GitLab's incident management features
A
A
A
A
A
In
addition,
there's
an
on-call
scheduling
piece,
which
is
right
here
when
there's
an
alert.
How
do
the
appropriate
people
know
there's
an
alert?
We
don't
really
have
anything
in
place
for
that.
Yet
so
we'll
need
to
figure
out
how
this
piece
works
to
be
properly
competitive
in
the
space
and
allow
our
teams
to
dog
food
or
incident
management
features.
A
We're
going
to
tackle
all
these
items
over
the
next
few
milestones.
I
won't
read
through
this
whole
slide
because
there's
a
lot
there,
but
if
you're
curious,
please
check
out
the
links
on
the
slides
afterwards,
but
in
the
context
of
this
ux
showcase,
I
wanted
to
walk
you
through
some
of
the
updates
that
we're
planning
for
each.
A
A
A
The
proposal
that
we've
been
working
on
is
to
allow
people
to
upload
their
own
metric
screenshots.
You
can
kind
of
see
the
drag
and
drop
feel
down
here.
So
if
a
user
has
a
different
tool
that
they
are
utilizing
for
their
charting
and
their
metrics,
they
can
take
a
screenshot
and
post
it
right
in
this
tab
which
will
allow
anyone
who
comes
into
the
incident
to
see
all
of
the
relevant
metrics
all
in
one
place.
A
A
A
Our
quick
way,
our
mvc
way
of
adding
integrations,
was
a
simple
form
that
allowed
people
to
copy
a
webhook
url
and
an
offer
authorization
key
and
then
input
those
details
into
their
monitoring
tool,
which
would
then
allow
for
the
sending
of
alerts
to
gitlab
in
user
testing.
We
discovered
this
way
of
adding
integrations,
wasn't
particularly
clear
or
scalable.
A
A
We've
come
up
with
a
proposal
to
introduce
an
integration
wizard
so
essentially
we're
going
to
replace
that
original
form
that
you
saw
on
the
previous
slide,
with
the
wizard
that
you
see
here
on
the
left,
as
we
do
so
we'll
be
adding
additional
integration
types
and
right
now
we
have
rest
integration
and
prometheus
as
integration
options
and
as
part
of
this
effort,
we'll
introduce
email
and
custom
integrations
and
that
will
round
out.
Our
initial
offering
for
integrations
to
get
here
is
the
on.
A
A
So
this
is
the
piece
we
haven't
addressed
yet
and
essentially
it
allows
people
to
create
schedules
which
define
who
will
be
contacted
when
an
alert
is
fired.
Many
people
may
have
heard
of
pagerduty.
That's
what
our
team
uses
currently
to
handle
handle
this
situation,
so
we're
not
anticipating
starting
this
work
until
13.6
in
terms
of
when
we're
going
to
start
building
it.
But
we've
started
problem
validation
for
this
feature
and
we've
also
started
some
initial
design
discovery
in
terms
of
the
design
discovery.
A
I've
been
diving
into
some
competitive
analysis
and
I've
been
working
with
sarah
walner
to
outline
workflows
and
define
both
the
mvc
and
subsequent
iterations.
For
this
feature,
what's
shown
here
is
a
screenshot
of
part
of
my
competitive
analysis,
but
if
you
want
to
check
out
the
full
view,
the
mural
length
is
available
in
the
slides.