►
From YouTube: GitLab 13.7 Kickoff - Plan:Certify
Description
Kickoff video for the Plan:Certify group for GitLab 13.7
Planning Issue - https://gitlab.com/gitlab-org/plan/-/issues/201#certify-mark-kickoff-video
A
Currently
coming
into
this
release.
We
have
our
weights
here
and
given
the
split
of
the
engineering
team
between
certify
and
product
planning,
we've
allocated
a
weight
of
10
to
the
certified
group
for
this
upcoming
milestone,
based
on
the
carryover
work
from
the
previous
milestones
and
then
our
overall
velocity
I'd
like
to
start
by
talking
about
a
couple
things
that
we're
working
on
for
design
throughout
this
13-7
milestone.
A
These
features
are
expected
to
be
developed
during
the
13-8
milestone.
The
first
one
is.
We
want
to
create
designs
for
the
requirements.
Export
we're
working
on
releasing
requirements
import
here
shortly
and
export
would
be
the
next
logical
step
where
we
can
export
requirements
back
out
of
gitlab,
including
some
of
the
functionality
that
we've
built
in
the
gitlab,
like
the
coverage
data
and
whether
or
not
the
requirement
has
been
satisfied
during
testing,
so
we're
happy
to
see
that
moving
along.
A
The
second
thing,
we're
really
working
on
is
support,
filtering
and
sorting
of
requirements
within
the
requirements
list.
This
will
allow
our
users
to
solve
the
problem
of
knowing
what
percent
complete
they
are
by
looking
at
the
requirements
list
alone,
you'll
be
able
to
sort
and
see
which
requirements
are
satisfied
currently
and
which
are
not
and
understand
how
complete
their
product
is,
which
is
very
helpful
to
those
people
in
regulated
industry
and
other
industries
that
are
looking
to
ensure
full
requirements
coverage
for
the
releases.
A
We
recognize
that
we
are
relatively
new
categories
here,
but
we
want
to
ensure
that
we're
not
carrying
technical
debt
forward
with
us
and
addressing
concerns
as
they
come
up.
One
of
the
first
things
to
note
here
is
there's
some
accessibility
concerns
with
the
requirements
drawer
when
we
introduced
the
slide
out
drawer.
That
came
out
from
the
right
of
the
screen
a
couple
things
sort
of
jumped
out
to
us
and
thank
you
all
for
the
wonderful
feedback
on
those
issues.
A
The
first
one
was
fixing
the
focus
state
of
buttons
for
the
requirement
creation
and
edit
form
that
has
actually
been
recently
fixed,
but
the
second
thing
that
we're
looking
to
solve
during
137
is
to
fix
it.
So
when
the
drawer
is
open,
the
keyboard
focus
is
trapped
within
the
drawer
until
the
door
is
closed.
This
has
caused
some
pain
for
some
of
our
users
and
it's
something
we
want
to
clear
up
right
away.
A
A
You
don't
see
how
many
issues
something
is
blocking.
What
we're
hoping
to
add
is
this
nice
little
indicator
that
says
this
issue
is
blocking
four
other
issues.
This
will
allow
people
to
sort
by
the
number
of
issues.
Something
is
blocking
and
better
prioritize
their
work
to
ensure
that
they're
handling
those
things
which
are
blocking
the
most
issues
first.
So
this
is
a
great
quality
of
life
improvement
that
will
really
add
a
lot
of
benefit
to
the
blocking
issue
support.
A
We
do
support
quick
actions
in
the
markdown
field.
The
caveat
is
there
are
certain
quick
actions
which
do
not
apply
to
things
like
test
cases
or
requirements
such
as
to
promote
them
to
an
epic.
You
can't
promote
a
test
case
to
an
epic
nor
a
requirement,
so
we
want
to
make
sure
that
we're
blocking
the
quick
actions
which
don't
make
sense
to
be
handled
within
a
certain
markdown
field,
just
to
keep
our
users
from
having
that
sort
of
confusion
and
having
that
undefined
behavior.