►
From YouTube: GitLab 12.7 Kickoff - Plan:Certify
Description
Here we'll walk through the features we're excited to implement in for the Plan:Certify group in GitLab 12.7.
Plan 12.7 Planning Issue - https://gitlab.com/gitlab-org/plan/issues/35
A
A
So
here's
the
plan
issue-
four
in
the
certify
section-
is
right
here.
So
we're
start
with
our
design
priorities.
There
are
a
couple
features
or
a
couple
issues
that
are
really
sort
of
been
a
big
sticking
point
for
the
service
desk,
and
that
is
that
it's
just
not
quite
to
the
point
where
people
feel
they
can
stop
using
their
current
help
desk
software
and
switch
over
to
the
service
test.
So
we've
heard
the
feedback
there
have
been,
and
some
really
good
issues
raised
by
the
community.
A
We've
had
some
issues
raised
by
our
own
internal
customers
as
well.
We're
gonna
work
really
hard
through
this
release
cycle
to
understand
the
means
of
our
customers
and
some
little
missing
features
and
work
hard
to
sort
of
augment
the
current
features
to
provide
a
more
enterprise
ready
service
desk.
We're
also
really
working
hard
to
provide
meaningful
requirements,
management
functionality.
I
know
this
is
but
an
ongoing
theme.
A
Over
the
last
couple
of
releases
we've
conducted
so
user
interviews,
we've
gotten
some
really
good
feedback
from
our
users
had
some
great
conversations,
we're
tracking
all
of
that
in
a
UX
research
issue
here
and
that's
been
an
enlightening
time
for
us,
we're
really
enjoying
that
and
we're
very
excited
to
start
rolling
out.
Some
of
these
wonderful
features
that
people
have
requested
for
this
release.
A
The
features
were
wishing
to
implement
we're
very
excited
to
advance
our
blocking
issue,
support
we
rolled
up
blocking
issues
in
12
6
or
are
planning
on
rolling
it
out
in
a
couple
days
here
in
twelve
six,
which
is
very
exciting.
For
us.
This
will
allow
users
to
say
that
an
issue
blocks
another
or
more
issues.
We
want
to
build.
On
top
of
that,
make
this
really
a
fantastic
feature
for
our
users
and
one
of
the
ways
to
do
that.
A
Is
we
want
to
make
sure
that,
when
we're
viewing
issue
boards,
you
can
visually
differentiate
a
block
issue
so
that
people
know
this
issues
block
that
need
some
attention.
There's
an
issue
out
there
for
that.
We
have
a
proposed
block
issue
icon
here.
This
is
the
proposed
design
for
that.
We're
very
excited
to
rule
this
out.
We
think
this
will
really
help
with
planning
and
ensuring
the
block.
Two
issues
are
getting
the
appropriate
level
of
attention.
A
They
need
we're,
also
going
to
start
trying
to
find
a
way
to
raise
a
warning
when
closing
an
issue
with
open
blockers.
What
this
basically
means
is
if
a
person
goes
to
close
an
issue
and
it
is
being
blocked
by
other
issues.
A
warning
will
be
raised,
something
unobtrusive
that
will
let
them
know
that,
are
they
sure
they
want
to
close
this
issue?
It
currently
should
be
blocked.
We
want
to
make
sure
that
that's
done
so
that
people
recognize
the
importance
of
block
issues
and
how
they're
working-
and
this
will
give
people
a
warning.
A
Service
does
punctuality,
we're
also
gonna,
be
giving
further
updates
to
that
one
of
the
futures
that's
been
requested.
A
lot
is
the
assignment
of
a
chosen
email
address
for
the
service
desk
user.
Currently
is
a
a
string
at
a
domain,
and
it's
hard
to
remember
it's
very
difficult
to
use.
So
one
of
the
features
people
have
requested
was
a
way
to
tie
an
email
address
of
their
choosing
to
the
service
desk,
to
make
it
either
more
human,
readable
or
just
simpler
to
utilize.
A
A
Also,
one
of
our
users
found
a
bug
with
some
of
the
email
providers,
which
prevents
the
proper
issue
creation
when
an
email
is
received
by
the
Service
Desk
I
did
not
seem
to
be
widespread,
but
we
definitely
want
to
take
care
of
that
for
our
users
and
so
we're
going
to
go
ahead
and
fix
it
here.
This
was
a
fantastic
issue
raised
by
the
community.
A
You
know
this
lovely
community
involvement,
so
that's
going
to
get
resolved
in
this
version
as
well
and
finally,
I'm
very
excited
to
state
that
we're
gonna
actually
launch
our
requirements
management
functionality.
This
will
be
a
first
iteration
it'll,
be
a
minimum,
viable
change.
We
expect
this
to
sort
of
give
a
taste
of
what
we're
planning
on
doing
in
the
future
and
allow
people
to
start
seeing
our
plans
and
provide
feedback
to
us
which
is
very
valuable
to
us,
so
that
is
going
to
roll
out
in
12.7
as
well.
A
We've
been
working
very
hard
on
this,
we're
very
proud
of
all
the
work
we've
done
and
we're
very
much
hoping
that
this
is
a
widely
accepted
feature
that
people
really
enjoy.
We
do
know
it's
gonna,
take
some
iteration
to
get
there,
but
we're
hoping
to
have
our
community
along
with
us
for
this
journey
and
if
there's
any
questions
or
specific
items
that
people
are
looking
for
for
requirements,
please
let
myself
know
or
add
on
these
issues.
That
would
be
super
helpful
for
us
just
that
we
have
a
better
understanding
of
the
needs
of
our
customers.