►
From YouTube: UX Showcase: Dedicated Incidents
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
All
right,
hello,
everyone,
as
nadia
mentioned,
I'm
amelia,
and
I'm
a
product
designer
for
monitor
health.
I'm
going
to
give
the
second
half
of
the
updates
for
monitor,
which
is
a
super
quick
walkthrough
of
the
improvements
we're
making
to
the
incident
management.
Workflow.
A
So
during
monitor's
last
ux
showcase,
I
walked
through
our
process
for
designing
the
new
alert
workflow
and
since
we
spoke
last
time,
alerts
have
now
officially
been
introduced
to
gitlab
and
what
you're
seeing
on
the
screen
now
is
essentially
what's
been
built
and
the
last
pieces
were
released
at
the
end
of
13.2.
So
this
is
all
live
and
out
in
the
wild.
A
A
A
Essentially,
an
issue
for
an
incident
is
currently
a
totally
standard
issue
with
an
incident
label.
Over
many
months
we've
been
discussing
whether
or
not
issues
are
the
right
fit.
For
instance,
are
they
providing
people
with
the
relevant
context
that
they
need
to
resolve
incidents
which
are
they're
very
inherently
stressful,
and
it's
very
time,
sensitive
effort.
A
So,
realistically,
the
process
of
creating
an
entirely
new
entity
to
replace
issues
was
going
to
be
tricky
to
do
in
any
reasonable
time
frame.
But
we
started
asking
ourselves:
can
issues
be
adapted
to
better
suit
incidents
and
issues
right
now,
you
kind
of
get
what
you
get
in
terms
of
content
can't
really
be
customized
in
any
meaningful
way
for
particular
use
cases,
but
what
if
they
could
be
customized
if
they,
if
that
was
possible,
we
could
start
asking
different
questions.
Like
is
all
of
the
content
we're
seeing
here
necessary.
A
A
A
So
what's
different,
the
very
exciting
thing
for
us
is
customizable
sidebars
in
the
process
of
creating
incident
issue
types
we'll
be
creating
widgets
for
sidebar
items
so
that
people
can
choose
which
are
the
most
relevant
to
display,
for
instance,
we'll
be
introducing
a
new
lynx
sidebar
item
and
the
ability
to
publish
incident
to
the
status
page
you'll
also
notice
a
tab
structure
which
is
similar
to
the
mr
page.
A
This
will
allow
us
to
surface
alert,
details
metrics
logs
and
run
books
directly
within
the
incident,
and
the
final
new
detail
is
the
ability
to
add
other
related
content
beyond
just
issues.
So
if
people
want
to
link,
for
example,
multiple
alerts
to
the
same
incident
because
they're
all
part
of
the
same
problem,
they
can
now
do
that
so
building
an
entirely
new
issue
type
is
going
to
be
a
ton
of
work
that
will
take
a
while
and
we're
starting
on
some
of
the
back
end
pieces
in
13.3.
A
I
expect
it
will
take
us
several
milestones
to
get
to
the
point
where
we're
seeing
changes
in
the
ui,
but
this
is
an
exciting
step
forward
for
us
and
likely
for
other
teams
as
well,
because
it's
a
step
towards
more
customizable
issues,
which
is
something
we've
been
talking
about
for
ages
and
has
been
a
requested
feature
for
a
really
long
time.
So
it's
exciting
for
us
and
for
hopefully
other
people
too,
and
that's
all
we
had
to
share
for
today.
A
As
all
the
monitor
updates,
thanks
for
listening
and
as
nadia
mentioned,
please
feel
free
to
send
us
a
message.
If
you
have
any
questions
thanks
so
much
for
your
time,.