►
From YouTube: GitLab 13.0 Kickoff - Plan:Project Management
Description
Release Planning Issue - https://gitlab.com/gitlab-org/plan/-/issues/85
A
This
gate,
weaver
senior
product
manager
of
the
project
management
group
in
the
play
stage,
gate
lab
doing
our
13.0
major
kickoff
for
a
lease
video
for
this
particular
release.
We
got
some
exciting
things:
coming
high-level,
we're
gonna
start
with
the
second
iteration
of
the
dirt
importer.
The
thing
we're
going
to
be
focusing
on
with
this
is
going
to
be
mapping
to
your
issue.
Author
itis
I
need
to
get
lap
users.
A
What
this
will
enable
us
to
do
is
more
or
less
take
the
issues
that
are
in
JIRA
and
map
the
comments
and
the
authors
that
created
them
and
create
recreate
those
comments
map
to
the
correct
authors
with
and
get
lab
issues
on
the
import.
This
also,
let
us
do
things
like
handling
ad
mentions
and
descriptions
and
other
cool
stuff
like
that.
The
next
thing
we're
going
to
be
doing
in
the
JIRA
importer
is
working
on
the
markdown
parser.
A
So
what
this
all
enables
to
do
is
take
the
jura,
syntax
for
their
descriptions
and
comments
and
convert
that
into
cloud
flavored
markdown
in
a
corrected,
sensible
way.
This
base
classes
for
the
partial
will
be
also
applicable
to
other
importers.
We
build
the
future,
so
that's
gonna
be
some
important
work.
There's
a
lot
of
other
little
cleanup
things
here.
A
We
won't
get
into
those,
but
the
two
main
things
you
want
to
get
to
in
terms
of
data
parity
is
bringing
in
the
authors
mapping
those
to
get
live
users
in
the
markdown
parser
for
our
second
main
theme,
we're
going
to
be
working
on
sprints
and
tracking
scope
change.
So
we've
had
this
multiple
milestones
issue
open
for
a
while.
What
we're
gonna
do
is
a
smallest
iteration.
Here,
just
add
another
time,
box
type
called
sprint.
A
A
This
will
enable
organizations
that
do
safe,
another
kind
of
multi-level
playing
breakdowns
to
attach
an
issue
to
a
priority,
increment
playing,
which
is
usually
a
quarter
along,
and
that
would
be
the
milestone
and
then
a
two-week
sprint,
which
would
be
what
the
actual
team
tracks
to
work
against
and
how
they
organize
the
issues
into
the
time
box.
So
we
have
the
UX
done
here,
everything's
good
to
go
and
I
think
we're
fairly
far
along
with
this
already
so
wrap
that
up
and
in
terms
of
tracking
scope
change.
A
A
Another
major
thing
we're
gonna
be
working
on
is
real
time.
This
is
an
ongoing
thing.
Our
first
goal
here
is
to
get
the
WebSocket
invitation
working
and
get
lab
and
then
have
assignees
update
in
real
time
on
the
sidebar.
So
if
you
update
be
a
quick
action,
if
somebody
else
in
a
different
client
updates,
it
would
push
that
update
through
the
server
back
to
the
client
without
needing
a
full
page
refresh.
So
this
is
a
huge
undertaking,
we're
making
some
good
progress
here
and
I
hope
to
see
it
live
in
13.
A
We
also
have
a
4
theme,
which
is
chores
bugs
long-running
investments.
This
may
be
things
like
cleaning
up
some
uux
debt
issues,
Moving's
and
promise
features
down
to
core
working
on
a
security
issue
and
then
any
additional
things
that
we
have
capacity
for
we're
gonna,
try
to
slip
in
and
get
those
done
in
terms
of
bugs
performance
or
availability
improvements,
and
that
is
what
we
had
planned
for
3904
the
project
management
group.
You
can
always
find
these
details
in
plan
issued.
Number
85
and
I'll
also
put
a
link
to
that
issue.