►
From YouTube: 12.4 Kickoff : Plan
Description
Plan Vision : https://about.gitlab.com/direction/plan/
Plan 12.4 Issues: https://bit.ly/2kzub5G
Questions? Comments? Send thoughts to kokeefe@gitlab.com or mention me on GitLab.com using @kokeefe
A
A
So
we
started
with
a
simpler
approach
of
adding
work-in-progress
limits
to
issue
lists
on
issue
boards.
Eventually,
when
will
we
want
to
get
to
having
min
and
Max
of
work-in-progress
limits,
but
right
now
we're
just
doing
max.
So
if
you
want
to
scroll
down
a
little
bit
and
you
can
kind
of
open
up
one
of
those
designs
Alexis,
do
you
want
to
talk
through
that
since
you're
here
and
you
designed
it.
B
Yeah
and
I'm
gonna
update
these
a
tiny
bit
just
with
like
minor
UI
changes
after
I
talked
with
one
of
our
product
designers
Jeremy.
But
the
interactions
shouldn't
be
the
same:
basically
a
user.
They
see
this
new
option
in
their
column,
their
list
that
there's
a
settings
option
when
they
click
on
that
it
opens
up
a
sidebar.
B
Because
it
if
it
opens
up
a
sidebar
and
there's
not
gonna,
be
a
whole
lot
in
there
at
the
moment,
but
the
basic
idea
is
that
they
can
then
edit
this
work
in
progress
limit
item.
They
enter
a
number
that
will
be
their
max
they'll,
see
that
it's
applied,
and
then
they
could
edit
that
again,
if
they
need
to
and
then
once
it's
applied,
they
see
it
on
their
column
that
there
is
a
another
number
next
issue
count
indicating
that
there's
a
max
on
their
issue
on
their
column.
B
If
they
have
let's
say
here,
they
have
three
issue
cards
within
that
column
and
they've
set
a
max
of
two
they'll
see
an
error
there,
I
don't
know
if
that's
an
error,
but
they'll
see
an
indicator
there
and
then
once
they
move
in
the
issue
card
out
of
that
column,
they'll
see.
There's
another
screen.
Therapist
they'll
see
that
they
have.
B
This
look
so
crazy
on
my
screen.
So
they'll
see
that
they
have
two
of
two.
So
it's
under
the
limit.
They
no
longer
see
an
indicator
on
that
list.
They've
gone
above
the
agreed
upon
with
limit
and
yeah
and
all
is
good
and
then
I
could
go
into
that
sidebar
again
and
then
in
the
future.
I
think
that's
flexible
enough
that
we
can
allow
them
to
set
min
max
by
weight
by
issue
count
if
that's
what
they
want
and
I
like
the
sidebar
to
I.
Think
in
other
products.
B
I
saw
a
lot
of
modal's
pop
up
when
you
want
to
change
that
limit,
which
I,
don't
think
is
the
greatest
experience,
because
you
really
don't
have
the
context
of
everything
else
going
on
in
the
page.
So
those
are
the
interactions,
the
design
you
know,
color
wise,
may
change
a
little
bit.
I
was
thinking
about
like
the
focus
state
of
that
column.
So
but
that's
all
it
might
change
well,
yeah!
That's
the
general
idea.
Does
anyone
have
questions?
I
know
that
was
kind
of
a
rough
ride
with
the
zooming
on
the
design
are.
C
A
Your
eye,
you
basically
have
a
station,
that's
idling,
which
means
that
they're
not
being
utilized,
which
is
if
it's
Caniff
it's
running
like
within
a
given
system,
that's
just
being
wasted
wasted,
output
or
unutilized
output,
so
I
think
that's
kind
of
where,
like
you
might
always
want
to
have
to
two
or
three
things
in
progress.
If
not,
then
it's
like
a
good
indicator
that
you're
upstream,
like
should
push,
can
can
pull
downstream.
D
A
B
E
A
A
That
watching
that
kind
of
they
look
kind
of
the
video,
maybe
also
think
that
some
point,
it
might
make
sense,
have
like
a
board
config
button
that
would
just
convert
everything
that
is
configurable
like
into
that
state,
so
that
you
could
quickly
run
through
and
change
like
the
work-in-progress
limits
on
all
of
the
lists
instead
of
one
at
a
time.
But
that
was
just
the
weird
random
thought.
A
B
Interesting
because
you
know
I
see
a
lot
of
people
do
the
configuration
setting
like
on
a
different
page.
So,
like
you
said
it's,
we
could
get
it
within.
The
context
of
this
page
have
like
a
board
setting.
Maybe
it's
another
side,
but
instead
of
having
to
go
one
by
a
line
that
might
be
cool
like
it
just
opens
up
an
input.
B
I
know
JIRA
used
to
do
that
when
on
another
page,
but
g-r
I
just
moved
to
something
more
like
this,
which
is
kind
of
interesting
they're
like
how
Trello
is
where
you
have
the
little
overflow
option.
You
click
that
and
then
it
you
can
select
the
with
limit,
so
they
actually
moved
more
in
this
direction.
So
that's
something
cool.
Maybe
we
can
research
like
how
are
people
setting
these
limits
and
like
are
what
is
the
workflow?
Do
they
go
one
by
one?
B
Do
they
want
to
like
configure
a
whole
board
all
at
once
and
then
maybe
like
we
think
about
where
else
we
want
to
go
with,
like
maybe
that's
where
we're
beside?
If
you
wanna
do
scrum,
if
you
wanted,
you
know
like
what
kind
of
board
you
want
right,
like
a
step
before
this
before
you
set
up
your
boy,
yeah.
F
If
that
a
lot
of
it
comes
down
to
how
they're
how
they're
wanting
to
use
it
like,
it
often
gets
controlled
in
my
experience
by
team
structure,
so
you
know
if
they
have
a
column
for
code
review
or
QB,
or
something
like
that.
That's
usually
really
I've
seen
people
put
work
in
progress
limits
because
there's
a
resource
constraint
there,
but
at
the
same
time
like
in
my
to-do
column,
you
know
at
the
beginning
of
my
sprint.
F
It
might
not
make
sense
to
have
a
limit
there,
because
there's
gonna
be
a
variable
number
of
tickets
in
that
every
time
so
yeah
I,
think
I.
Think
keeping
it
as
flexible
as
possible
is
great.
I
think
this
sidebar
is
great
kind
of
echoing
the
comments
from
before
so
I.
Think
a
lot
of
its
gonna
come
now
to
watch
and
how
people
use
it
and
get
some
feedback
and
then
a
board
configuration
option
might
make
sense.
Then.
A
A
So
the
only
thing
is
something
different
than
the
design
it's
up
there
right
now
is
there's
a
comment,
updated
description,
but
there's
a
comment:
a
discussion
around
changing
topical
description
to
I
think
compared
with
previous
version
and
I
put
that
correct
label
down
I
think
two
bullet
points
below
where
the
screens
cut
off
yeah.
So
compared
with
previous
version
to
expand
the
diff
there's
a
the
UX
work
is
done,
I
think
the
back
end
work
is
underway,
but
it's
not
done
so.
That
should
be
wrapped
up
in
12,
4
and
launching
with
that
milestone.
A
But
yeah.
This
will
be
nice
for
a
lot
of
people.
There's
been
a
lot
of
conversation
back
reports
about
pricing
period
should
fall
in
and
you
know
is
an
artificial
constraint
and
lots
of
different
things.
So
it's
kind
of
made
us
think
about
our
handbook
quite
a
bit
and
our
pricing
strategy
and
policies,
but
I
think
it's
it's
gonna
turn
out
pretty
well
and
lots
of
people
are
gonna,
be
happy
any
questions
about
this.
F
Right
so
this
will
be
Alexis's
and
a
nice
favorite
topic
of
conversation
over
the
last
week.
So
look
at
a
surfacing
weight
in
progress.
Information
inside
of
the
roadmap,
epic
bars
I
think
you
know
again.
I'm
coming
in
this
is
my
first
kickoff
meeting
so
really
coming
in
and
trying
to
pick
up
or
a
lot
of
portfolio
management.
Stuff
was
at
the
right
time
and
trying
to
move
things
forward.
That
I
think
we
can
get
through
an
iterative
process
without
too
many
large
scale
changes.
But
you
know
this
wasn't
fairly
simple
right.
B
F
So
sorry,
let
me
get
that
if
you
open
up
again
yeah,
so
we're
looking
at
really
just
how
do
we
display
that
information
in
the
roadmap
bars
in
a
way
that
isn't
too
overbearing
doesn't
clear
things
up,
but
lets
people
just
have
a
quick
visual
reference
of
okay
cool
I'm
32%
done
with
a
refactor
in
the
front-end
discussion
components,
and
it
looks
like
do
you
want
to
walk
through
these
this
new
picture
since
I?
This
is
a.
This
is
brand
new
yeah.
B
So
this
seemed
easy,
but
when
I
was
digging
into
it,
you
know
there
was
a
few
different
ways
to
do.
It
either
add
almost
like
a
new
column
into
the
left
sort
of,
like
we
have
a
column
on
the
left
of
our
roadmaps.
That
has
the
title
and
the
date
so
I
was
thinking.
Okay,
MVC,
like
easiest
thing,
might
be
adding
another
column
there
and
just
showing
the
progress
within
that.
B
But
many
products
also
do
more
more
of
a
visual
option
where
it
just
displays
on
the
epic
bars
themselves,
and
that
was
something
common
I'd
seen
in
Keenan
also
like
that
direction.
But
the
problem
with
ours
was
that
when
we
display
epic
with
no
start
or
end
date,
we
just
have
this
really
long
gradient.
So
it
was
hard
to
demonstrate
certain
end
date,
which
is
displayed
through
color
and
then
also
displaying
like
a
progress
on
the
epoch
bars
themselves
through
color.
B
There's
like
a
little
bar
under
epic
with
no
end
date,
so
just
having
like
a
small
line
there,
the
indication
there
that
there's
no
end
date
and
then
showing
a
progress
bar
instead
of
using
the
whole
width
of
the
epic
bar
and
like
having
kind
of
liking
the
issue
where
it
shows
it's
like
filled
in
on
the
epic
bar
itself.
Just
having
like
a
progress
bar
on
that
bar,
which
kind
of
decouples
the
two
things
as
well,
because
one
is
time-based
and
one
is
progress
based.
B
F
F
C
C
Was
exactly
thinking
about
percentage
in?
You
should
count
instead
of
wait,
because
yeah
I
see
that
many
people
count.
The
issues
that
have
been
delivered
is
enough.
Just
the
weight
and
the
weight
actually
can
it's
many
times
just
a
guess,
and
it
doesn't
reflect
exactly
the
work.
So
it
would
be
good
to
have
as
a
second
iteration
yeah.
F
G
G
G
B
That
somewhere,
but
it
was
actually
I,
was
using
newer
icons.
That's
what
I
meant
when
I
was
like
pairing
up
with
Jeremy
a
bit
he's
been
working
on
icons
lately,
so
in
that
mock
I
used
the
new
one,
which
maybe
that's
good
feedback
for
him,
that
it
looks
even
more
like
a
lock
no,
but
we
could
use
our.
F
Cool
any
other
questions
or
thoughts
all
right
all
right
to
the
next
one,
so
the
drag-and-drop
issues
and
epics
in
the
epic
tree
support
ordering
between
all
objects,
which
of
course
is
a
continuation
of
93
67,
which
is
dragging
and
dropping
issues
and
epics
in
the
epic
treat
separately.
So
by
understanding
again,
this
one
has
been
around
longer
than
me,
because
I
haven't
been
here
that
long
yet,
but
is
looks
like
we
had
to
split
the
work
out.
F
F
A
That's
it
does
anybody
have
any
things
I
think
the
other
thing
to
kind
of
discuss
that
we
didn't
really
highlight
is
an
issue.
Is
that
I
know
in
12.4
we're
starting
the
process
of
refactoring.
The
sidebar
and
epics
issues
emerge
requests
to
be
consistent
and
use
the
same
tech
stack
using
view
and
then
graph
QL
and
making
it
ready
to
support
real-time
functionality
and,
in
conjunction
the
memory
group,
is
working
on
a
WebSocket
support
and
there's
gonna
be
a
bunch
of
work
that
we
do
around
that.
G
That's
pretty
good
one
thing
we
do
want
to
keep
in
mind,
though,
as
we
get
to
the
real-time
is
how
we're
going
to
handle
some
of
the
some
of
the
real-time
interactions
like
if
somebody
is
like,
if
somebody
has
the
labels
drop-down
open
and
someone
in
another
browser
adds
a
label.
What
kind
of
notification
do
we
do?
A
Maybe
we
kind
of
break
those
out
in
their
own
like
have
with
their
own
editors
or
I.
Guess
if
there
is
a
start
date,
participants
due
date,
we
can
talk
about
on
each
one,
but
like
case
in
point
with
the
labels
thing
right
now.
If
a
label
is
selected,
it
has
a
checkmark
next
to
it
in
a
drop-down
somebody
has
the
drop-down
open
and
it
gets
updated
in
the
background.
Like
a
new
label,
then
it
should
directly
just
seamlessly
rerender
and
show
the
label
with
the
checkbox
or
the
checkmark.
E
I
worked
through
something
a
few
weeks
ago
with
the
details
task
list
item
in
the
issue,
description,
which
a
similar
kind
of
issue
where
the
back
end
was
returning
the
HTML
or
the
markdown
that
would
be
rendered,
but
it
wasn't
like
you
said:
it's
not
being
accounted
for
what
I
have
open
or
what
another
user
has
open.
So
then
you
kind
of
have
to
do
this
like
what
did
they
have
open
and
then
match
that
and
kind
of
work
through
it,
but
it
was
just
pasting,
the
HTML
or
inserting
HTML
into
the
Dom.
A
Good,
you
know
I
think
there's
also
just
regarding
the
issue
description,
slight
tangent,
there's
a
open
issue
to
refactor
that
to
something
else
that
will
allow
us
to
do
things
in
a
little
bit
more
collaborative
fashion
without
having
to
rerender
all
the
markdown
in
HTML
every
time.
There's
any
change,
which
would
be
great,
so
I'm
excited
to
work
on
that
in
the
near
future,
too.
D
G
They
are
just
because
on
the
front
end,
it's
it's
using
the
most
modern
it.
The
the
refactor
of
the
sidebar
on
everything,
but
epochs
is
a
pretty
large
task.
So
this
is
focused
on
the
epic
refactor
epic
sidebar
refactor,
but
it's
really
just
for
the
container.
Once
we
get
that
container
done,
then
we'll
be
able
to
start
working
on
the
next
page
sidebar,
which
is
going
to
be
issues
so
I
think
I.
Think
the
portfolio
management
should
work
on
the
graph
QL
stuff
for
epic
sidebar.
A
Just
yeah
along
those
same
lines,
we
should
theoretically
be
like,
for
example,
where
it
says
for
participants
that
should
just
be
one
component
that
just
gets
different
props
or
different
query
to
get
the
data
right.
So
if
we
recreate
that,
we
should
be
able
to
use
that
everywhere.
There's
a
side
bar
that
has
the
participants
in
it.
G
D
But
it's
it's
gonna
be
a
different
graph.
Ql
Cori.
In
other
words,
the
participants
hanging
off
of
the
epoch,
is
a
different
query
than
the
participants
hanging
off
of
an
issue
correct.
Yes,
it
is
so
it's
nice
I'm,
just
saying
I'm,
not
sure
it's
yeah,
we
need
to
reuse
it
I'm.
Just
there
may
be
a
point
where
it's
not
reusable
or
needs
to
be.
Some
switch.
D
D
A
Would
it
be
useful
Brett
if
you
me,
you
and
Donald
like
had
a
quick
sink
the
beginning
next
week,
just
like,
because
this
is
a
lot
of
moving
parts
just
to
get
on
the
same
page
and
make
sure
we're
not
duplicating
things
or
we
can
understand
how
everything's
work.
Sir,
do
you
have
a
pretty
good
idea
of
at
this
point.
D
G
Sounds
good
awesome
yeah
because
even
not
related
to
the
sidebar
we're
going
to
have
to
graph
QL
if
I,
both
the
queries
and
mutations
for
built
issues
and
epics,
so
the
stuff
we're
doing
on
the
back
end
to
get
the
issue
api's
over
to
graph
QL
I,
don't
really
have
to
be
related
to
the
sidebar,
it's
stuff.
We
need
to
get
done
anyway.
E
I
had
a
question
Donald
I
when
I
started
working
on
the
whip
limits
in
the
board
list,
I
puts
it
in
the
gate,
LabVIEW
I
chain
on
to
see
if
there
is
before
I
had
the
context.
There
was
something
like
that
in
Gail
Mui,
and
someone
had
mentioned
that
they're
building
a
drawer
component
and
someone
asked
if
that
would
suffice.
I
don't
really
know
what
that
drawer
looks
like,
but
just
so
kind
of
we're.
On
the
same
page,
Gail
I've,
you
I,
we're
not
gonna,
be
using
that
we're
gonna
build
our
own
sidebar
correct
at.