►
From YouTube: GitLab 13.7 Kickoff - Plan:Project Management
Description
Planning issue: https://gitlab.com/gitlab-org/plan/-/issues/201#project-management-gabe-kickoff-video
A
Hey
everyone:
it's
gabe
weaver,
I'm
the
senior
pro
product
manager
for
the
project
management
group
in
the
plains,
age
of
gate
lab.
Today
we
are
going
to
be
talking
about
the
13.6
release
and
this
is
the
kickoff
video.
So
we
have
two
main
themes
for
this
upcoming
release
and
the
first
is
an
ongoing
one
that
we've
been
working
on
and
that's
planning
with
work
with
iterations.
A
So
the
main
focus
for
my
group
for
the
remainder
of
fy21
is
going
to
be
providing
best
in
class
capabilities
for
single
teams
that
you
utilize
common,
agile
methodologies,
like
scrum
stream
programming
combine
now
with
these
teams
over
75
percent
of
them
rely
on
iterations
or
sprints
and
scrum
to
plan
and
manage
their
work.
So
this
is
why
we're
focusing
mainly
on
making
this
a
first
class
experience
within
gitlab
and
for
13.6
we're
going
to
focus
on
four
key
improvements
here.
The
first
one
is
going
to
be
the
ability
to
add
iteration
lists
and
boards.
A
So
right
now
iterations
don't
exist
in
boards,
but
as
a
product
manager
like
myself,
I
need
to
be
able
to
see
and
manage
multiple
iterations
into
the
future
and
within
a
single
view,
so
that
I
can
plan
work
for
my
team,
and
so
this
is
going
to
follow
for
the
mvc
a
common
pattern
where
we're
just
going
to
be
able
to
add
iteration
lists,
and
then
the
goal
is
to
kind
of
enhance
this
and
iterate
on
it,
so
that
you
can
do
some
automated
list
management
for
your
iteration.
A
So
show
me
my
current
iteration
and
then
automatically
show
me
the
next
five
that
are
upcoming,
so
that's
adding
iteration
lists
and
boards.
We
also
want
to
properly
handle
state
for
closed
issues.
So
right
now,
if
I
go
looking
at
iteration
report
after
it's
been
done
or
closed,
the
stats
continue
to
change.
So
the
completed
amount,
the
incomplete
amount
that
that
varies
even
after
the
date,
the
iteration
is
closed,
but
it
really
should
be
a
snapshot
in
time.
A
So
what
we're
going
to
do
is
we're
going
to
make
sure
that
these
numbers,
once
the
iteration,
is
over
never
change
and
they're
immutable.
That
will
provide
a
better
historical
snapshot
when
you're
going
back
to
check
on
how
you
did
during
the
previous
iteration.
The
other
is
grouping
issues
by
label
within
the
iteration
report.
A
So
a
lot
of
teams
like
gitlab
ourselves.
We
use
this
group
project
management
label
to
know
what
is
is
my
issue
or
my
my
team's
issue
and
since
iterations
live
at
the
group
level
right
now,
and
that
was
intentional
and
issues
from
many
teams
and
projects
can
roll
up
into
a
single
group.
Iteration
report
there's
currently
no
way
to
group
or
see
specific
labels
that
maybe
my
team
is
responsible
for
group
issues.
A
According
to
that,
so
the
first
thing
we're
going
to
be
doing
is
adding
the
ability
to
group
issues
by
label,
so
there'll
be
a
kind
of
a
new
selector
down
here,
where
you
can
specify,
if
you
want
to
group
by
label,
is
the
first
one
we're
also
going
to
work
on
assigning
an
epic
after
that,
but
this
will
more
or
less
create
the
groupings
of
all
the
issues
according
to
different
labels.
A
Once
we
have
this
initial
mvc
in
place,
we'll
then
expose
the
ability
to
select
all
the
labels
that
you
want
to
view
your
groupings
by
the
fourth
final
thing:
we're
going
to
do
for
iterations
to
improve
it
is
we're
going
to
provide
the
ability
to
scope
a
board
to
a
current
iteration.
So
we
talked
about
adding
list
iteration
lists
and
board.
A
That's
if
I
want
to
plan
in
the
future
and
then
this
is
to
allow
a
board
to
be
scoped
the
existing
current
iteration
and
because
of
the
way
that
we've
designed
iterations,
you
don't
have
to
specify
what
the
current
is.
There
can
only
ever
be
one
current
iteration,
so
it's
just
going
to
be
a
simple
checkbox.
A
If
you
want
to
scope
the
board
of
the
current
iteration,
and
this
will
make
sure
that
only
issues
that
are
within
the
current
iteration
will
be
shown,
the
second
major
thing
we
want
to
work
on
is
kind
of
an
ongoing
will
always
be
a
thing
theme.
I
think
within
my
my
group
is
usability
and
quality
of
life
improvements,
so
within
these
some
of
the
ones
that
we
want
to
kind
of
highlight
is
the
first
is
removing
a
board
upsell
list.
A
So
when
you
create
an
issue
board
for
the
first
time,
we've
added
the
ability
to
automatically
create
a
couple
lists
for
you,
but
there's
a
sort
of
weird
thing
list
that
gets
added
to
encourage
you
to
upsell
and
upgrade
your
plan.
After
doing
some
data
analysis,
we
kind
of
found
that,
out
of
all
the
times
that
this
list
has
been
shown,
it
only
was
clicked
on
three
times
out
of
the
months
that
it's
been
there
and
it's
never
converted.
A
The
next
thing
we
want
to
do
is
we've
kind
of
been
working
on
this
in
the
back
end
for
a
while.
But
if
you
try
to
autocomplete
somebody
and
by
tagging
them
in
a
comment,
it
doesn't
work
well
to
search
by
name,
but
we're
going
to
make
it
so
that
you
can
search
by
both
username
and
first
name.
So
this
is
going
to
be
a
nice
thing.
If
you
don't
know
what
somebody's
gitlab
handle
is,
you
can
also
find
them
by
their
first
or
last
name.
A
This
is
one
of
our
stretch,
goals
that
we
have,
but
it's
cloning,
an
issue
with
a
quick
action
and
also
a
ui
element,
and
so
a
lot
of
common
use
cases
are
when
somebody
is
creating
an
issue
and
they
know
that
they
have
two
projects
that
they
need
to
create
the
issue,
and
maybe
it's
an
ios
app,
but
maybe
it's
the
api
instead
of
having
to
go
manually,
create
that
in
both
places.
What
we
want
to
be
able
to
do
is
you
can
create
one
issue
and
you
can
clone
it.
A
You
can
clone
it
into
your
current
project
or
you
can
clone
it
into
a
target
project,
so
this
will
make
it
easier
to
create
a
lot
of
issues,
especially
if
they're
similar
and
you
maybe
just
need
to
change
one
or
two
things
quickly
and
the
way
this
will
work
is
once
you
start
the
clone.
You
select
the
project
you
want
to
clone
it
to
or
take
you
to
the
new
issue
creation
form
with
all
the
data
pre-populated.
A
So
if
you
just
need
to
change
the
label
or
title
or
a
few
things,
you
can
do
that
quickly
and
then
you
can
go
ahead
and
create
the
issue.
Another
one
of
our
stretch.
Goals
is
going
to
be
forwarding
an
email
to
an
existing
issue
as
a
new
comment.
So
right
now,
if
I
leave
a
comment,
I
can
go
check.
My
notifications
in
my
email,
client
and
I
can
go
ahead
and
respond
to
that
we'll
post
back
to
the
issue,
but
there's
no
way
to
start
a
new
comment
directly
from
an
email.
A
So
what
this
will
do
is
each
issue
will
have
its
unique
email
address
that
is
kind
of
obfuscated
a
little
bit.
So
it's
not
easy
to
guess,
but
it
will
be
the
same
email
address
for
the
length
of
the
issue
and
you
can
copy
that
quickly
via
the
reference
area
down
here
in
the
bottom,
and
once
you
do
that
you
can
create
a
new
email
and
your
email
client,
with
the
two
address
being
the
one
that
you
copy
on
your
clipboard.
A
You
can
fire
that
off
and
it
will
create
a
comment
on
behalf
of
gitlab
bot
and
then
the
future
iteration
will
be
detecting
whether
or
not
that
emails
was
coming
from
an
existing
gitlab
user
or
project
member.
If
so,
we
go
ahead
and
post
it
on
their
behalf.
So
there's
a
preview
of
some
of
the
quality
of
life
improvements,
stretch,
goals
and
things
that
we're
focused
on
for
13.6
in
project
management,
thanks
for
checking
it
out.