►
Description
Christen Dybenko (Product Planning) and Jeremy Watson (Project Management) preview what's ahead for Plan in 13.9.
- Plan:Product Planning - 0:34
- Plan:Project Management - 6:04
Agenda and issue links available at https://docs.google.com/document/d/e/2PACX-1vT9tqVy-jBuPaUe_tHvhIiVlKQDRPY3c1eiQxzI_rmYdmTDL3RHhAOeu_ZaZWBiew1-rlFXTUoMZfDd/pub
A
A
B
B
If
I
open
these
up,
a
lot
of
the
effort
has
been
happening
in
13
8,
but
we
do
still
have
the
end
of
the
work
around
10
to
12
points
and
13
9
to
deliver
mvc1
and
basically,
what
this
one
would
get.
You
is
the
minimum
requirements
to
be
able
to
create
an
epic
board
and
like
see
it
on
the
board
and
interact
with
it,
but
you
can't
delete
it,
modify
it
or
do
any
of
those
actions
with
it.
So
that's
what
we've
tracked
to
in
13
9..
B
A
Awesome
thanks
a
lot
kristin.
I'm
really
excited
to
see
epic
boards
kind
of
come
to
fruition.
I
think
that
you
know
the
feedback
that
I
hear
from
customers
is
that
we
want
to
make
epics
a
lot
easier
to
use.
Allow
you
to
visualize
things
at
a
very
high
level
and
allow
customers
to
kind
of
shift
and
kind
of
drag
and
drop.
You
know
how
they
their
kind
of
planning
process
at
a
high
level.
So
I
think
it's
going
to
be
super
useful
for
our
customers
at
a
high
level.
A
So
I'm
really
excited
to
see
that
you
might
stop
sharing
your
screen.
Real,
quick,
oh
sure,
awesome
thanks
the,
and
I
also
appreciate
you
continuing
to
prioritize
instrumentation
the
epic
comments.
The
the
epic
interactions,
I
think,
is
the
right
way
to
kind
of
move
towards.
You
know
how
we
count
the
interactions
in
usage
ping,
so
we
can
understand
that
I
wonder:
is
there
like
a
specific
aspect
of
epic
interactions,
that
you're
kind
of
really
curious
to
see?
Because
right
now
I
think
we
just
measure
epic
creations.
A
A
Yeah,
that's
a
great
point.
It
really
is
frustrating
that
epic
comments
don't
show
up
on
your
activity
feed,
and
you
know
it's
hard
to
kind
of
understand
where
the
discussion
is
happening.
So
I
think
it's
a
great
great
idea,
great
change
and
thanks
for
prioritizing
epic
boards
and
again
it's
like
you,
there's
a
great
example
iteration,
because
you
held
off
things
like
removal,
as
I
recall
for
a
future
iteration,
so
good
work
scoping
that
down
to
like
just
the
basics,
so
we
can
start
getting
value
out
of
it.
It's
awesome
stuff.
B
A
Awesome
so
I'm
going
to
talk
a
little
about
what's
ahead
for
project
management,
gabe
weaver
would
normally
be
representing
he's
out
of
office
on
the
beach
super
excited
for
him
to
spend
some
time
out
of
office.
So
what's
ahead
for
project
management,
it
kind
of
falls
into
three
overall
themes.
I
think
the
first
one
I'm
going
to
talk
about
is
really
around
our
use
of
making
iterations
like
a
first
class
and
lovable
feature.
A
This
is
really
important
because
you
know
gitlab
is
a
very
powerful
project
management
tool,
but
for
teams
that
are
operating
in
an
agile
environment
and
frequently
using
sprints
to
be
able
to
organize
their
work
on
it.
On
a
you
know,
week
to
week
two
week
basis,
we
want
to
make
sure
that
this
is
a
tool
that
is
lovable
easy
to
use
and
something
that
teams
can
can
really
rely
on
on
a
day-to-day
basis.
A
A
Iterations
can
be
filtered
on
boards,
but
that's
only
one
at
a
time
and
what
we
would
like
to
be
able
to
iterate
towards
is
having
multiple
iteration
lists
on
a
board,
so
you
can
take
an
issue
and
then
drag
it
from
iteration
to
iteration
in
order
to
sort
through
exactly
how
which
iteration
an
issue
will
land
in.
So
this
will
make.
A
This
will
allow
a
user
that
is
using
a
board
with
us
with
a
scrum
team
or
to
see
multiple
iterations
at
a
single
board
and
be
able
to
drag
and
drop
an
issue
from
one
iteration
to
another,
depending
on
your
needs
from
on
a
sprint
to
sprint
basis.
This
becomes
a
real
superpower
when
you
also
enable
epic
swim
lanes
to
to
to
to
horizontally
split
the
number
of
of
your
work,
where
eventually
you'll
be
able
to
see
after
this
change
epics
on
a
horizontal
basis
and
then
iterations.
A
A
You
want
to
be
able
to
to
to
create
a
record
for
that
in
gitlab,
now
you'll
be
able
to
you'll
be
able
to
find
iteration
data
that
have
started
in
the
past.
I
think
the
last
issue
that
I'm
really
excited
about
is
being
able
to
group
issues
by
label
within
the
integration
report.
So
currently
we
have
an
iteration
report
in
the
group
view.
A
That
is
kind
of
analogous
to
what
you'll
see
for
milestones,
so
you'll
be
able
to
click
into
an
iteration
yellow
to
see
a
burn
down
chart
and
a
burn
up
chart
of
all
the
issues
that
fall
into
that
iteration.
But
the
challenge
here
is
is
that
you
also
want
to
be
able
to
break
this
down
a
little
bit
further.
A
Well,
you
might
want
to
be
able
to
see
this
split
out
by
team,
where
teams
are
typically
split
out
by
label,
so
you'll
be
able
to
group
issues
by
by
by
this
by
this
dimension,
and
you
can
see
in
this
figma
report
you'll
be
able
to
see
like
at
the
top.
You
know
a
particular
label
and
you'll
be
able
to
see
a
breakdown
of
all
the
issues
in
that
iteration
that
fall
underneath
that
label
we're
still
iterating
on
exactly
how
we're
going
to
handle
pagination
between
the
scroll
or
pagination.
A
But
this,
I
think,
makes
the
iteration
report
so
much
more
powerful
by
allowing
a
scrum
master
or
an
engineering
manager
to
kind
of
see
what's
going
on
at
a
high
level
and
have
a
clear
breakdown
of
which
teams
are
what
the
status
of
the
issue,
depending
on
the
label
and
and
team
status,
we're
also
getting
a
start
on
iteration
cadences.
So
we're
not
going
to
ship
this
in
13.9,
but
I'd
like
to
just
kind
of
preview.
A
This
to
where
we're
going,
which
is
you
know,
iterations
right
now,
are
have
to
be
manually
created
on
an
ongoing
basis
in
the
future.
We
want
to
be
able
to
define
a
specific
iteration
cadence
for
a
different
particular
team
and
allow
that
team
to
go
ahead
and,
on
an
automated
basis,
create
new
iterations
that
they
can
use
to
plan
future
work.
A
A
The
other
theme
that
I'm
that
I'm
going
to
talk
about
is
extensible
issues,
so
iterations
is
going
to
be
the
focus
extensible
issues,
I
think,
is
not
far
behind
the.
What
we
want
to
do
is
we
want
to
make
issues
really
really
powerful
by
eventually
introducing
customizable
issue
types
and
allowing
you
to
specify
kind
of
a
the
type
of
issue
which
comes
with
it:
predefined
content,
predefined
rules.
We
need
to
iterate
in
order
to
get
there,
and
you
can
see
that
we
did
this.
A
So
all
types
of
issues,
epics
and
issues
will
be
considered
in
the
future,
an
issue
type
and
once
we've
accomplished
that
we're
going
to
work
on
full
on
more
richer
customizability
by
allowing
you
to
define
specific
content
for
specific
issue
types.
So,
for
example,
if
an
issue
is
an
incident
default,
the
discussion
order
to
a
certain
type
default
like
a
issue,
template
type
of
content
to
the
issue
description
and
allow
you
to
have
a
lot
of
more
a
lot
more
richer
control
over
issue
types
in
the
future.
A
A
A
A
This
figma
prototype
kind
of
shows
a
little
bit
of
that
experience,
so
you
can
see
you
can
kind
of
go
in
and
you
can
see
this
person
is
actually
defining
an
or
some
or
logic
for
the
assignee.
So
you
can
actually
like
click
on
multiple
assignees,
and
when
you
do
that,
you
see
the
or
populate
where
you
can
actually
say
looking
for
issues
that
are
under
assigned
to
joe
smith
or
ali,
this
is
going
to
be
a
huge.
A
You
know,
step
forward
for
our
filtering
logic
really
excited
for
that
which
will
be
landing
in
13.9
and,
finally,
I
think
another
usability
improvement
that
I'm
super
excited
about
is
introducing
group
level
description
templates
for
issues
epics
and
merge
requests.
Currently,
you
know
we
have
the
ability
to
define
description
templates
at
the
project
level,
but
I
think
the
challenge
is
that
if
you
have
many
many
different
projects
across
a
large
organization,
it's
really
painful
to
manage
all
of
those
templates
in
every
single
individual
project.
A
So
now
you're
going
to
be
able
to
specify
a
specific
project
within
a
group
that
serves
as
the
source
for
the
templates
you
manage
and
then
maintain
them
in
a
single
project
and
you'll
see
them
populate
everywhere
across
all
the
projects
and
all
the
subgroups
within
that
group
so
really
excited
for
all
these.
For
all
these
improvements,
I
think
there's
a
lot
of
great
stuff
ahead
in
13.9
for
project
management,
but
yeah.
That's
all
that's!
That's
what
we've
got
in
store.
Kristin.
Do
you
have
a
do?
You
have
a
couple
questions
or
comments.
B
B
I
wonder
too,
like
just
seeing
that
view,
and
it
was
using
bullets
in
the
list,
and
I
know
in
that
we're
using
a
board
over
in
the
milestone
report
like
just
getting
a
little
more
clarity
around
when
we
use
those
different
rollups,
the
different
types
of
ways.
We
could
show
these
issues
and
why?
Because
I
think
we've
got
a
couple
different
ways
to
view
them
right
now.
A
A
It's
so
cool
yeah,
it's
really
nice.
I
think
I
could
definitely
like
you've
been
thinking
about
managing
okrs
and
how
to
kind
of
handle
like
a
larger
initiatives.
I
think
that
we
got
to
make
sure
that
that
pattern
and
that
approach
makes
sense
for
for
your
use
case
as
well.
So
you
know
the
issue
is
linked
here
so
feel
free
to
click
into
it
and
click
around
your
prototypes.
But
I
think
it's
great
that's
awesome.