►
From YouTube: GitLab 13.5 Kickoff - Plan:Certify
Description
GitLab 13.5 Kickoff Video for the Plan:Certify Stage.
We welcome collaboration, so please feel free to view the planning issue here: https://gitlab.com/gitlab-org/plan/-/issues/159
A
Hey
everyone
and
welcome
to
the
get
lab
13.5
kickoff
for
the
plan
certified
group.
We
planned
things
out
a
little
differently
this
month,
and
hopefully
that's
reflected
here.
We
had
an
initial
set
of
planning
done
up
front
prior
to
setting
priorities
with
the
stable
counterparts
from
engineering
and
the
ux
group,
and
so
some
of
this
information
at
the
top
of
this
planning
issue
is
that
discussion
we
had
back
and
forth
based
on
the
priorities
we
had
set
in
the
end.
A
Therefore,
for
new
features
this
month
you
can
view
all
of
our
priorities
and
planning
at
the
portfolio
management
certified
planning
board
if
you're
so
interested.
The
link
is
here
in
the
issue
and
for
new
features.
We
are
prioritizing
finishing
the
quality
management
mvc,
so
there's
a
couple
things
left
to
do
before
we
can
release
this
one
is
that,
because
test
cases
are
built
upon
issues,
there
are
certain
quick
actions
that
we
allow
in
our
issues
that
don't
make
sense
for
test
cases,
namely
the
promote
quick
action
which
would
promote
an
issue
to
an
epic.
A
The
second
thing
we
need
to
do
to
release
that
feature
is
to
remove
the
feature
flag
and
roll
it
out
to
everyone
who's
using
our
product,
and
that
issue
is
here
and
there's
a
set
of
steps
required
for
removing
a
future
flag.
You
can
see
in
this
issue
that
has
a
weight
of
two,
as
does
the
quick
action
resolution,
so
we're
looking
at
a
weight
of
four
to
release
and
finalize
the
quality
management
mvc.
A
In
addition,
we're
very
excited
to
add
the
ability,
a
couple
features
to
requirements,
management.
One
is
the
ability
to
mark
a
requirement
satisfied
manually,
and
this
is
something
that
a
lot
of
people
have
asked
for.
When
people
are
doing
manual
testing,
it
would
be
nice
to
be
able
to
click
on
a
button.
That's
a
satisfied
or
check
box
and
hit
save
changes,
and
you
can
mark
your
requirements,
satisfied
after
performing
a
manual
testing
or
some
sort
of
acceptance
criteria
testing.
A
We
are
also
looking
to
be
able
to
include
a
long
description
for
requirements
to
provide
additional
context
or
to
talk
about
the
acceptance
criteria
of
those
requirements.
So
the
design
for
that
looks
something
like
this.
Where
you
have
the
opportunity
to
type
into
a
very
familiar
markdown
style
editor,
you
can
use
titles
mobile
italic,
all
the
formatting
we're
used
to
this
will
enable
the
users
to
add
descriptions
to
those
requirements,
mainly
for
things
like
acceptance,
criteria
or
implementation
details
that
they
wish
to
add.
A
A
The
final
feature,
we're
rolling
out,
is
support
for
multiple
email
participants
in
service
desk,
and
what
this
does
is
this
is
the
next
step
needed
to
be
able
to
add
issue
participants
via
email
address
to
issues
you
can
see.
That's
part
of
the
epic
here,
so
this
is
the
portion
of
the
epic
we're
choosing
to
tackle
in
13.5
we're
very
excited
for
this
feature
to
complete,
but
we're
trying
to
tackle
it,
one
step
at
a
time
and
iterate
on
what
we
already
have.
So
we're
very
happy
that
that's
coming
in
13.5.
A
We
also
talked
about
some
performance
enhancements
and
technical
debt
to
resolve.
There's
some
cleanup
to
the
requirements
database
that
we're
planning
on
doing
which
has
a
weight
of
one
as
well
as
some
cleanup
on
the
blocking
issue,
relationships
in
the
database
as
well,
which
has
a
weight
of
three,
and
these
are
both
scheduled
to
eliminate
technical
debt
from
our
backlog
and
to
allow
for
a
cleaner
and
more
efficient
future
implementation
of
newer
features.
A
A
As
always,
please
feel
free
to
comment
on
this
issue
or
any
of
the
issues
linked
here.
I
will
leave
a
link
to
this
issue
itself
in
the
youtube
comments
field
below.
I
look
forward
to
collaborating
and
if
there's
any
questions
or
problems,
please
reach
out
to
me
directly
or
on
any
of
the
issues
you
see.
Thank
you
so
much
for
your
time.