►
From YouTube: GitLab 12.6 Kickoff - Plan:Certify
Description
Overview of the Certify portion of the Plan group's 12.6 functionality.
Plan Group 12.6 Overview Issue - https://gitlab.com/gitlab-org/plan/issues/27
A
Good
day,
everybody
and
welcome
to
the
plan
stage,
certify
group
kickoff
here
for
12.6
I'm
mark
wood,
I'm
super
excited
to
be
presenting
this.
We
have
a
lot
of
exciting
things
going
on
in
this
release,
so
I'm
happy
to
share
them
with
you.
Let
me
go
ahead
and
share
my
screen
here
and
we'll
walk
through
some
of
the
exciting
features
we're
gonna
be
presenting
here
in
12.6.
A
So
one
of
our
big
focuses
over
the
past
couple
releases
and
it
will
continue
going
forward-
is
to
improve
the
service
desk
to
make
it
a
more
robust
solution
and
a
more
customizable
solution
for
businesses.
So
a
few
of
the
things
that
have
been
noted
as
concerns
from
our
users
were,
we
were
unable
to
change
the
full
name
of
the
service
desk
user.
It
used
to
say,
get
lab
bot,
and
that
was
a
little
confusing
when
customers
would
email
a
organization
service,
that's
gonna
receive
an
email
back
from
the
get
lab
bot.
A
There
was
an
urge
to
change
that
to
something
more
representative
of
the
business,
so
we
have
opened
up
an
issue
here.
It's
been
open
for
a
while
and
we're
pretty
excited
to
get
this
into
this
release.
So
you
can
see
here
some
of
the
details,
we're
hoping
that
the
email
from
name
so
it'll
come
from.
You
know
something
from
your
organization
so
required.
So
they'll
be
a
very
nice
addition
to
you,
the
Service,
Desk
and.
A
Then,
if
we
back
to
the
12.6
issue
here,
the
other
thing
we
wanted
to
do
is
allow
email
responses
from
the
Service
Desk
to
include
some
more
templatized
type
response.
In
other
words
right
now
they
are
very
generic,
and
a
lot
of
organizations
would
love
to
put
their
logo
or
signature
or
a
tagline.
That
has
some
words
in
it
says
you
know
for
further
help.
Please
contact
this.
A
So
here's
that
issue
it
received
a
lot
of
votes
from
the
community.
It's
a
very
popular
issue
and
we're
very
excited
to
implement
this
here
in
12.6.
Hopefully
this
will
allow
businesses
to
better
represent
themselves
and
utilize
the
service
desk
in
a
manner
that
will
really
represent
their
business
as
well
as
solving
the
customers
issues.
A
Also,
there's
a
couple
outstanding,
technical
issues
that
we
wanted
to
fix
on
these
words.
One
of
these
is
a
bug
and
then
I
when
it's
just
sort
of
lacking
information.
Currently,
when
PDFs
or
emails
via
the
service
desk,
some
some
of
our
users
were
experiencing
an
issue.
It
could
not
be
viewed
in
the
browser
they
had
to
be
downloaded
and
open
in
an
external
program
which
obviously
is
not
ideal.
A
So
this
issue
here
71005,
was
written
to
sort
of
state
that
and
address
this
problem,
so
we're
hoping
to
get
this
resolved
also
at
twelve
point
six
to
streamline
the
workflow
for
our
existing
users
and
then.
Finally,
the
other
issue
was
that
some
people
had
reported
and
they're
correct
that
very
little
service
desk
was
exposed
via
the
project's
API.
A
So
our
goal
is,
as
we
move
forward
to
always
add
you
know
relevant
features
to
the
API
as
we
introduce
features
some
of
those
were
missed
in
the
past
and
we're
trying
to
bring
the
service
desk
back
up
to
standards
and
allow
some
of
the
API
calls
to
query
things
such
as
there's
a
list
here
basically
wanted
to
view
and
edit
product
information.
Basically,
they
want
to
turn
on
the
service
desk.
They
want
to
see
what
email
address
the
service
desk
is
currently
utilizing.
A
Some
of
those
things
that
would
love
to
be
a
scriptable
so
that
you
can
write
scripts
around
it
to
enable
the
service
desk
check
the
email
address,
and
then
you
know,
file
a
report
or
something
along
those
lines.
It
would
be
very
beneficial
to
have
the
API
functional,
so
we're
going
to
fix
that
here.
A
In
addition,
we're
still
working
to
move
forward
on
our
requirements
management,
it's
a
really
exciting
feature.
We
get
lab.
We
can't
wait
to
roll
this
out
to
our
users
in
order
to
make
sure
we're
doing
this
correctly.
We've
really
wanted
to
take
our
time
and
ensure
that
we're
not
just
duplicating
existing
solutions,
but
we're
actually
providing
useable
features
that
excite
our
users
and
that
allow
our
users
to
really
reach
the
maximum
potential
utilizing
requirements.
A
So
they're
not
a
roadblock
they're,
not
in
the
way
but
they're
beneficial
to
our
users,
and
they
can
see
the
value
in
that
in
order
to
create
the
best
possible
experience.
We've
opened
up
a
user
experience,
research
issue
for
this,
and
that
can
be
seen
here,
and
that
is
an
issue
that
we're
actively
working
to
do.
Some
research
from
our
users
figure
out
exactly
what
the
users
are
interested
in
and
sure
that
we're
providing
the
best
possible
solution.
This
has
been
an
ongoing
issue
and
it
probably
will
not
be
complete
before
12.6.
A
However,
we
are
in
parallel,
hoping
to
implement
our
minimum
viable
change
to
allow
users
to
create
requirements.
We
know
that
we
need
that
feature.
We
know
we
need
that
experience
for
our
users.
We
want
to
make
sure
that
they
can
create
requirements
at
a
requirements
and
that's
sort
of
the
core
feature
and
as
we
move
forward,
this
UX
research
issue
will
help
us
understand
which
directions.
A
We
should
go
first,
linking
requirements
or
reports
what
is
most
valuable
to
our
users
to
provide
the
most
value
in
their
workflows,
and
so
we
really
need
to
understand
user
workflows,
so
I
encourage
anybody
who
has
questions
or
has
experiences
with
that.
Please
feel
free
to
leave
comments
in
these
issues.
We
greatly
appreciate
that
the
more
information
we
receive
from
our
users,
the
better
we
can
make
our
product
so
there's
any
questions,
go
ahead
and
leave
them
in
any
of
the
issues
linked
here.
Thank
you
so
much
and
have
a
wonderful
day.