►
From YouTube: Plan group weekly meeting
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
C
B
Week,
two,
the
same
later,
we
have
a
lot
for
next
release
as
well,
but
some
of
these
turned
out
to
be
either
easier
than
expected
in
that
we
basically
basically
already
do
the
thing
it
just
takes
a
little
while
or
not
already
fixed
by
something
else,
which
is
also
great,
so
that
helped
a
lot.
We
have
a
new
back-end
engineer,
starting
mid-january.
If
we
see
Heinrich
join
then
Chantal
left
so
once
this
new
person
starts
will
actually
be
up
a
person
and
just
a
reminder
to
contribute
to
the
retrospective.
A
Great
I
do
have
something
this
and
I
brought
up
a
point.
Maybe
we
can
discuss
it.
I
think
you
know
we
have
better
ideas,
you
can
discuss
it
later,
which
is
the
the
feature
flag,
thingy
and
just
knowing
when
those
are
out
so
maybe
shot
if
you're
right.
If
you
already
have
like
a
quick
answer
to
that,
I
love
it.
So
my.
B
So
the
issue
suggestions
thing
might
be
one
of
those,
for
instance,
because
we
know
that,
like,
oh,
hey,
we're
doing
a
bunch
more
API
requests,
we
might
want
to
check
that
before
we-
and
you
know
before
we
actually,
you
know
you
might
want
to
turn
it
on
turn.
It
off
turn
it
on
turn
it
off
type
thing.
So,
but
my
understanding
is
that
the
idea
behind
outing
feature
Flags,
isn't
that
we
have
to
go
and
turn
everything
on
each
time,
because
that's
somewhat
rare
customers.
A
Okay,
and
so
so
my
only
question
there
is:
do
we
have
the
process
right
because
I
don't
want
to
interests
engineers
to
do
additional
steps,
but
if
they're
already
doing
something
that
I
can
poke
in,
which
is
say
like
a
suggested
issues
thing:
where
is
the
discussion
happening,
that
that
should
not
be
on
right
away?
And
then,
where
is
the
discussion
happening
like?
Oh,
let's,
you
know
wait
for
RC
and
then
somebody
will
remember
to
to
turn
our
like.
Where
was
that
discussion
happening
that
I
can
poke
in
on?
This
is
my
question.
B
So
I
would
say
that
the
way
we
should
change
this
if
we
change
anything,
is
probably
to
say
that
if,
if
you
are
adding
a
feature
flag
that
is
default
off
or
you
are
turning
a
feature
flag
off
you
should
you
should
have
an
issue
to
enable
that
feature
flag
like
Phil's
created
now.
So
if
the
feature
flag
is
in,
it
is
default
on.
Okay,
then
issue
because
like
unless
an
incident
happens,
and
we
need
to
disable
it
then
with.
A
A
B
If
we're
shipping
it
behind
the
flag,
the
intent
is
that
by
the
zero
second
yeah
by
the
twenty
seconds
it's
on,
so
the
idea
I
think
maybe
I'm
confusing
things
too
much,
except
for
sort
of
backstage
things
where
I
would
say
pretty
much.
Every
feature
flag
should
be
on
by
default,
every
new
one
that
we
add,
certainly
any
one
for
a
feature,
but
you
have
the
Trinity
to
disable
it
on
get
lab
comm
for
its.
B
Can
add
a
feature
behind
a
feature
flag
after
the
freeze,
you
can
change
a
feature
fight
from
default
off
to
be
fall
on
if
you
want
to
after
the
freeze
its
just
grated
default
on
and
then
disable
it
you
can
do
that
after
the
free.
So
that's
that's
the
other
aspect
of
this,
but
I
think
fundamentally
the
easy
easy
way
to
think
about.
It
is
always
add
them
as
default
arm
right.
If
you
don't,
you
will
have
a
good
reason.
B
We
assume
exact
if
you
need
to
turn
it
off
on
get
lab
calm
before
deploying
it
is
Oh
punky
lab
calm,
it
won't
turn
on
automatically.
In
that
case,
you
should
create
a
follow-up
issue,
and
that
should
be
on
the
same
milestone,
so
we
can
track
it
right
right.
A
A
Release
or
the
dog,
whatever
release,
and
so
for
that
version
that
will
always
have
an
issue.
There
will
have
a
mouse
don't
on
it
and
that
milestone
will
be
that's
the
plan,
the
milestone,
so
so
that
that's
it
and
we
can
expect
that,
of
course,
that
can
always
change,
and
so
yes,
what
can
happen
is,
for
example,
we
we
find
out
on
Gilad
calm,
something
terrible.
Then
we
just
go
back
and
you
know
change
the
mouse
and
I
think
that's
totally
fair.
A
C
A
A
C
Document
in
handbook
suggests
ideally
to
scope,
feature
flex
to
a
project
or
group
and
I
wonder
if
it
makes
sense,
then
to
have
them
on
by
default,
because
I
think
that
it
either
makes
sense
to
create
a
global
feature
flag
which
is
by
default
on.
But
if
I
scope
something
to
specific
project,
it
makes
sense
to
have
it
by
default
off.
Because
then
typical
scenario
is
that
if
something
goes
wrong,
I
can
easily
disable
the
feature.
C
B
Sorry,
and
so
currently,
as
far
as
I
was
away
the
feature
check
and
it's
been
a
while
since
I
went
to
this,
the
feature
check
only
worked
at
the
centage
of
the
time
or
on
or
off,
and
it
can
take
a
project,
but
when
it
is
a
project,
that's
just
for
a
license
check.
I,
think
I
thought
the
project
wasn't
actually
used
for
anything.
C
Yes,
so
I
was
following
the
command
I
placed
it
in
a
chat
and
I
can
set
feature
flag
scope
to
a
specific
project
or
group
picture.
It's
suggested
by
and
once
I
do.
This
I
think
that
it
makes
sense
to
have
the
feature
flag
by
default
of
if
I
do
if
I
use
a
scoped
feature
flag,
because
you
know
it's
it's
a
little
bit
weird
to
use
feature
flag,
which
is
by
default,
all
which
is
scoped
to
specific
projects
right.
B
B
C
C
B
B
A
A
So
number
three
roadmap
given
current
capacity.
So
if
you
click
on
that,
that's
our
standard
grow
map,
it's
so
what
I
did
is
sort
of
cheated,
which
is
I
pushed
a
lot
of
epics
out
further
into
the
future
and
because
our
road
map
view
doesn't
really
let
us
go
out
too
far
in
the
future,
and
that's
actually
something
that
animal
is
working
on
right
now.
What
I
did
is
I
cheated
a
little
bit
and
just
if
you
look
at
q4
2019,
all
the
epics
are
searches.
A
They're
toured
at
the
end,
and
the
reason
I
did,
that
is
just
so
that
we
can
have
a
view
of
all
the
ethics
because,
for
example,
if
you
look
at
the
list
view
of
epochs,
it
doesn't
show
start
date.
So
it's
really
hard
to
see.
Epochs
and
I
just
want
a
view
of
all
this
stuff
that
is
awesome
and
plan
and
that
we
want
to
do
with
some
degree
of
confidence.
A
But
this
is
my
somewhat
more
conservative
estimate
of
when
we
can
actually
get
to
these
things,
and
so,
given
the
amount
of
security
features
that
we
are
security,
bugs
that
we've
had
to
address
and
the
ones
that
are
upcoming.
This
is
my
my
estimate,
so
nothing
actionable
just
just
wanted
to
share
that
with
people
and
so
relatedly.
What
I've
done
is
I
created
a
couple
boards,
or
these
are
boards
I've
been
around
for
a
while,
so
security
issues
per
milestone.
A
So
if
you
don't
already
know
of
the
people
in
this
call,
don't
already
know
we
have
a
process.
So
if
you,
google,
get
lab
security,
team
handbook
or
something
you'll
see
their
page
in
our
handbook
and
what
it
says
is
essentially,
the
security
team
is
responsible
for
assigning
due
dates
to
security
issues
and
then
essentially,
I
and
Shawn
and
Andre
are
responsible
for
scheduling
the
issues
to
meet
the
due
date,
and
so
we've
been
doing
that
for
the
past.
A
Two-And-A-Half
milestones
that
I
think
with
pretty
good
success,
I'm
pretty
happy
what
6's
in
the
sense
of
it's,
it's
pretty
obvious
how
to
do
that.
It's
like
it's
just
an
algorithm,
just
the
the
the
furthest
milestone
that
meets
a
due
date
right.
That's
the
algorithm,
I
Brendan,
my
brain
and
then
in
the
eleven
point,
six
we've
been
able
to
finish
all
security
issues
and
still
do
other
work
so
which
is
amazing
so,
but
this
board
planned
security
issues
by
milestone.
You
can
see
for
eleven
point
seven.
A
We
have
six
issues
right
now
for
eleven
point:
eight
we
have
sixteen,
which
is
a
lot
for
twelve
point:
zero.
We
have
eight
and
there
for
twelve
point,
one
two
and
three
and
four:
we
have
zero,
because
the
security
team
puts
severity
up
to
s
3
and
then
s
three.
The
due
date
is
such
that
it
has
to
be
done
by
twelve
zero.
A
Any
ways
if
you
do
the
math
so
at
the
current
rate,
I
expect
these
security
issues
to
continue
at
a
similar
pace,
if
not
increased
and
I
read
somewhere
and
slack
or
somewhere
that
hacker
won
the
organization
we
used
or
the
integration
we
use
to
input.
These
security
issues
will
be
that
company
is
going
public
or
something
like
that,
and
so
therefore
we
expect
more
incoming
security
issues
from
the
community,
so
this
might
even
get
worse
before
it
gets
better.
So
it's
hard
to
predict,
but
that
is
a.
D
Only
thing
the
only
thing
I
have
heard
was
that
there's
a
bounty
on
program
happening
around
this
time,
all
right,
I
heard
about
the
public
saying
maybe
it's
the
same
thing
just
ok,
but
we're
expecting
a
little
bit
increase
in
P
ones.
For
example,
some
rent
parents
and
back-up
plan
to
have
someone
doing
the
holidays
for
the
front
that
at
least
I
think
the
back
and
s
as
well.
If.
B
A
That
makes
sense
so
yeah,
so
so
basically
I
don't
know
if
this
will
get
worse
or
better.
But
these
are
the
steps
we're
doing
to
manage
the
problem
managed
in
the
sense
you
know
give
visibility
be
able
to
show
people.
What
is
the
impact
of
these
things
so,
whether
it's
the
road
map
or
just
having
a
list
of
security
issues?
A
But
again
this
is
a
way
to
to
bring
a
little
bit
more
sanity
to
the
process
and
then
so.
Another
thing
to
note
is
that
our
boards
are
not
super
awesome.
Yet
so
there's
overlap
so
there's
security
things
in
this
particular
board
as
well,
so
sort
of
just
ignore
those,
because
those
are
already
covered
and
then
there's
a
head
count
planning
sheet.
So
so
I'm
purposely
not
sharing
my
screen.
Are
they
because
some
of
these
things
we
can?
A
We
can't
share
publicly,
but
the
head
count
planning
sheet,
go
ahead
and
click
on
that,
and
so
that's
our
very
ambitious
goal
to
do
to
hire
more
folks
to
do
more
awesome
work.
That's
inner
vision
is
essentially
so
we
went
through
this
exercise,
I
think
in
the
past
couple
weeks.
Some
of
the
executives
did
so
and
then
sort
of
just
trickled
down
to
myself
and
Andrzej
and
Shawn
I
think
Shawn
you're
away
so
I
pinged
in
and
bred,
and
they
were
very
helpful.
A
So
thank
you,
I
think
I
think
Mario,
sorry,
so
I
think
I
should
have
been
bad
for
that
one.
So,
in
any
case,
they
do
review
this,
and
so
why
I
wanted
to
bring
this
up
is
that
it
seems
sort
of
like
ridiculous
that
our
roadmap
goes
like
if
you
were
to
look
at
all
the
epics
and
all
the
things
that
we're
doing
given
the
current
capacity.
A
It
would
like
take
us
two
and
a
half
years
to
do
it's
like
by
my
estimate,
so
it
that
sort
of
seems
silly
right
so,
but
the
idea
is
that
good
lab
we
want
to
grow
as
quickly
as
we
can,
and
so,
if
you
look
at
this
spreadsheet,
this
is
a
way
for
the
team
at
good
lab
to
communicate
to
our
investors.
You
know
their
board
of
directors
is
actually
to
convince
them
like.
This
is
an
amazing
vision.
We
want
to
do
all
these
things.
Thus
we
need
to
hire
more
people.
A
Does
it
make
sense
on
and
so
forth,
and
we
can't
just
say
that
right,
because
you
know
what
we
could
I
mean,
but
we're
we're
a
big
organization
we're
doing
a
lot
of
things,
so
we
have,
to
you
know,
put
some
numbers
together.
Yes,
a
lot
of
these
are
really
rough
estimates,
but
nonetheless
we
need
to
do
an
exercise
so
that
it's
not
just
pulling
crazy
numbers
out.
A
Okay
yeah,
so
so
one
group,
yeah
yep,
so
I
have
to
change
our
language
because
it's
incorrect,
so
yeah.
So
the
plan
group
will
become
multiple
groups
at
some
point.
I
don't
know
when
and
how
and
stuff
like
that,
especially
since
I'm
not
very
much
involved
in
the
hiring
anyways,
but
you
know
that
that's
that's
coming
down!
A
A
D
A
Right,
yep,
yep
you're,
totally
right
thanks
Andre,
so
it's
it's
pretty
much
twice
for
us
and
then
you
can
see
like
I
think
forty
seven
is
like
so
yeah
security
is
is
huge
because
that's
like
a
ginormous
market
and
the
custom
customers
are
really
resonating
with
security
and
sort
of
it's
sort
of
obvious,
given
this
day
and
age,
why
security
is
a
big
deal,
so
we
we
were
my
understanding
and
talking
with
my
peers.
We
underestimated
that
market
and
so
we're
trying
to
catch
up.
But
plan
is
no
slouch
from
the
perspective.
A
There's
a
lot
of
stuff
we
we
can
do
and
that
we
want
to
do
and
it's
already
in
our
vision.
So
so
that's
that
and
then,
if
no
questions
comments,
they're,
okay,
Andre
I
did
something
so
I'll
go
faster.
Metrics,
so
is
something
that
you
know
as
a
prime
manager
should
be
doing
a
better
job
of
at
least
just
you
know,
showing
what
we
have.
So,
if
you
everybody
can
at
Gillick
and
you
should
be
able
to
get
a
looker
account
and
access
these
dashboards.
A
So
if
you
click
on
that
link,
you
can
see
those
desk
dashboards
and,
if
you're,
really
really
too
lazy
to
get
a
account.
A
looker
I'm
gonna
try
to
update
that
doc.
So
for
a
I,
and
so
you
can
see
I'll
just
take
screenshots
over
dashboards
and
the
reason
I'll
do
that
is
probably
because
I
want
to
advertise
these
things
more
broadly.
A
Within
gitlab
and
the
more
broad
you
can
go,
it's
it's
it's
even
less
expecting
people
will
be
able
to
get
account
no
problem,
and
if
you
need
to
leave,
you
have
to
leave
so
anyways.
So
those
are
usage,
ping
things
and
the
other
thing
is
with
snowplow
front-end.
So
the
machine
I've
been
putting
together
the
snow
cloud
framework,
so
I've
been
pretty
sure
that
that's
ready
to
go.
A
So
that's
why
I've
created
at
least
two
issues
and
I
think
there's
three
plan
issues,
but
two
I've
scheduled
already
to
measure
how
many
times
people
are
clicking
the
export,
CSV
and
import
a
CSV
functionality
forget
lab
so
I
think
now.
That's
like
a
great
first
place,
I
couldn't
think
of
anything,
that's
easier
or
sort
of
somewhat
useful
and
there's
also
some
some
metrics
in
general.
There's
a
bazillion
ways
to
use
it,
and
so
one
approach
is
that
we
just
log
everything
and
sort
of
look
at
it.
A
Afterward
we
can
do
that,
but
if
we
log
everything
it's
also
work
to
log
everything.
So
I
have
no
idea
how
easy
or
hard
it
is
to
log
everything.
So
I'm
letter
beasts,
importing,
CSV
and
exporting
CSV
is
sort
of
my
way
to
say:
okay,
let's
just
work
on
that.
First,
let's
get
the
team
comfortable
with
this
and
maybe
afterward
we
as
a
plan
team
can
say:
oh,
this
was
actually
pretty
easy.
Let's
do
more
long,
and
so
we
can
do
that.
A
D
D
Now
that
there's
an
issue
for
eleven
seven
that
we
have
been
discussed
about,
fixing
the
task
lists
and
I
know
there
was
some
proposals
over
there
that
how
to
fix
that,
but
since
we're
now
using
this
system
that
you
pick
whatever's
next
in
the
pipe
in
the
pile,
there
is
a
chance
of
us
having
this
situation
where
the
front
end
or
the
back
end
picks
it
up.
And
then
the
other
part
doesn't
have
availability.
B
B
Ideally,
we
would
have
some
way
of
giving
a
particular
checkbox
item
and
address,
or
something
like
that,
so
we
could
just
say,
check
this
box,
because
if
we
can
say
check
this
box,
it
doesn't
matter
what
order
these
two
things
happen
in,
because,
if
I
check
box
a
and
then
check
box
B,
the
result
should
be
the
same.
Obviously,
if
I
check
box
a
twice,
then
that's
slightly
different,
but
you
know
we
can
worry
about
that
separately.
B
So
when
I
say
retry
I
mean
from
a
back-end
perspective,
like
the
user
wouldn't
see
anything,
it
would
just
take
a
tiny
amount
longer
and
it
should
also
be
much
faster.
So
one
of
the
reasons
this
could
be
really
slow
right
now
is
because,
like
I
said,
we
update
the
entire
body,
which
means
that
we
have
to
render
the
entire
markdown
pent
HTML
and
particularly
on
our
QA
e
issues
that
we
automatically
generate
for
releases.
B
And
yeah-
and
you
end
up
with
a
lot
of
HTML
at
the
end
of
it
as
well,
which,
like
the
front-end,
doesn't
need
the
backend
doesn't
really
need
to
generate.
It
could
just
say
like
in
the
HTML.
This
box
is
now
checked,
so
I
think
that
that
part
can
mostly
be
decoupled
from
the
front-end
part,
but
obviously
don't
need
to
coordinate,
but
like
Louis
proposition
or
like
no
matter
how
we
resolve
it.
B
Having
said
that,
now
that
the
backend
item
has
been
added
to
this,
this
is
the
second
top
item
on
the
open
list
for
back-end
engineers.
The
only
item
above
it
is
a
security
issue
that
may
or
may
not
actually
need
a
fix
because
it
may
already
be
fixed,
so
someone
should
be
able
to
tech
gets
that
soon.
D
That's
because
we
had
security
shoes
where
I
wasn't
sure
how
the
situation
was,
but
what
I
told
my
people
was
that
hey
whenever
you
pick
this
up,
I
raised
this
on
the
channel
to
make
sure
that
we
have
back
and
soon
picking
it
up
that.
So
it
is
visibility
he'd
be
great
if
the
other
thing
happened
as
well.
So
if
the
backend
picks
it
up,
first
just
raise
that
on
the
channel
so
that
we
can
then
assign
the
front.
Then
it
was
more
available
then,
but
yeah
apart
from
the
specific
solution.
B
D
D
I
have
is
you
click
that
actually
I
don't
have
any
information,
I
think
or
maybe
it
does
anyway.
We
can
check
that
later,
but
yeah.
Of
course
we
try
to
use
a
possibility,
but
the
other
part
is
what
what
problem
is
actually
I
thought.
So
anyway,
we
can
sync
that
up
later
or
when
someone
picks
it
up,
I-I've
waited
I,
wait
that
issue
in
terms
of
front
end
the
weight
that
is
there
is
five
four
so
front
end.
B
A
I
know
yeah
no,
no
to
build
on
that
sure
I,
don't
care
like
I,
think
I,
think
in
this
new
world
I
care
about
order,
a
thing
that
we're
doing
and
then
the
the
fact
that
this
isn't
super
scalable
and
it's
manual
on
J
that
you
know
you
have
to
you
have
to
talk
with
Shawn
or
somebody
has
to
get
on
slack
like
I
I,
don't
mind
it.
Obviously
I'm
not
doing
anything.
You
you
folks
are
doing
all
the
work.
A
So
if
you
folks
don't
mind
it
and
like
there's
only
like
a
handful
of
these
happening
per
month,
I'm
still
super
happy
I
to
me.
It's
not
it's
like
we're
working
remote.
This
is
a
cost
of
things.
How
we
do
things
and
before
we
in
the
future,
we
have
got
Q
and
it's
super
awesome
right,
but
before
we
get
to
that,
there's
always
going
to
be
issues
of
the
quad
cross
collaboration.
A
If
it
takes
a
little
bit
longer,
I
think
that's
fine
and
if
it
delays
a
homo
stone,
I
think
that
that's
fine
but
but
I.
What
I
would
ask
for
you
and
Sean
is
to
be.
If
you
see
an
opportunity
to
say
like
let's
actually
not
do
this
now
and
knock
out
something
later
down
the
list,
that
is
a
lot
smaller
and
we
could
do
it
really
quickly.
A
I
would
ask
you
to
to
just
do
it
and
then
don't
even
ask
for
a
permission,
just
say
it,
and
then
just
tell
the
team
on
slack
that
you,
you
think
you've
just
did
the
priorities,
because
it
makes
sense
something
like
that.
I
think
that
makes
sense.
But
in
this
particular
case,
when
you
just
like,
we
had
this
conversation
in
this
video
call
for
10
minutes,
and
it
seems
like
both
you
and
Shawna
resolved
it
and
so
to
me
that
works
beautifully.
So
yeah.
A
D
Yeah,
okay,
thanks
figure,
we'll
do
that!
So,
if
I
go
to
the
next
point,
so
I'll
give
you
an
intro
and
then
I'll
explain
what
this
is
about.
So
this
is
more
for
for
your
wax,
so
Pedro
and
Annabel
I,
just
me
and
Tim,
and
in
the
front-end
team
we
were
moved
away
from
the
spreadsheets
and
jumped
on
board
full-on
with
the
issue
boards,
although
we
are
a
little
frustrated
with
some
features
that
are
lacking
and
their
plans.
D
So
there's
nothing
completely
mind-blowing
here
more
about
like
the
swim
lanes,
that
sort
of
thing
having
that
sort
of
visibility,
and
since
it's
not
there,
so
Tim
hacked
their
little
scripts
using
tampermonkey
to
improved
a
little
bit
of
the
issue
board
and
I
just
wanted
to
demo
it
for
you
just
so
that
you
could
visualize
how
it's
looking
for
us
right
now
again,
it's
not
perfect.
It's
not
amazing
it's!
D
So
it's
very
specific
to
our
case,
because
it's
overloading
the
meaning
of
the
in
dev
and
in
review
labels
having
that
exposed
visually
but
I
think
it's
useful.
First
I
have
a
look,
however.
I'm
doing
it
with
my
account
and
it
does
have
confidential
issues
on
it
and
we're
recording
the
call.
So
is
it
a
possibility
to
end
the
recording
here
and
me
doing
the
demo
without
recording.
A
D
Okay,
so
let
me
just
set
my
screen,
then
there
we
go
so
basically
the
changes
that
a
that.
So
this
is
basically
a
script
that
we
added
via
tampermonkey
an
extension,
so
it
runs
some
JavaScript
after
the
page
is
loaded
after
things
have
been
loaded
and
all
it's
doing
is
basically
giving
some
borders
on
the
left
of
each
card
to
highlight
the
state.
Now
he
told
me
what
the
meaning
of
these
labels
were.
I
think
let
me
just
have
a
look.
Oh,
why
is
it's
not
like
trying
to
find
one
green?
D
Maybe
there's
a
green
one
anyway,
all
right
there
we
go,
so
these
ones
are
the
ones
that
are
done
right
and
that's
for
us
to
understand
which
one?
Of
course
this
list
closed.
Basically,
if
it's
that
goal,
but
the
other
colors
basically
talk
about
assignees
about
states
of
in
development
or
in
review,
and
that
sort
of
thing,
so
it
does
this
for
for
every
board,
although
it
does
have
very
specific
meaning
for
us
on
top
of
that,
it
kind
of
summarizes
account.
D
So
after
it's
done
its
thing,
it's
able
to
tell
that
we
have
52
issues
open
13
in
the
5
and
review
and
they'd
have
been
done.
So
this
is
more
of
a
just
a
thing
for
us
cuz.
We
missed
this
from
the
spreadsheet
to
have
a
good,
clear,
look
as
an
individual,
as
we
have
assignees
lists,
it's
good
for
us
to
have
a
look
and
see
okay,
how
many
does
really
have
open,
which
ones
has
had
in
review,
and-
and
so
it's
very
useful
to
have
this
in
a
way
of
managing
the
team.
A
D
You
just
created
this
this
week
because
we
have
it
yeah.
We
have
a
kickoff
on
Friday
and
we're
going
to
use
this
board
to
do
like
a
sharing
of
the
whole
team
right
and
we're
going
to
basically
improve
this
just
so
that
we
have
sort
of
the
same
thing
we
had
on
the
spreadsheet
and
right
now
again,
this
is
using
correction.
So
it's
just
as
things
are
loaded,
the
script
runs.
So
it's
not
just
CSS.
D
E
E
D
Could
definitely
a
little
put
an
issue
or
something
and
dump
the
script
there
so
that
you
can
have
a
point
to
a
link
to
point
to
and
discuss
even
and
then
even
we
can
come
in
and
explain
a
little
bit
more
about
these
colors
I
know
that
one
is
Sinese.
The
other
is
colors.
The
other
is
in
that
round.
Okay,.
B
B
A
B
A
Would
make
a
lot
of
sense
yeah?
Nobody,
they
know
exactly.
I
could
totally
echo
Shawn's
point.
This
is
swim
lanes
and
I.
Don't
know
the
answer
to
this,
so
I'm
just
gonna,
throw
it
to
pager
I,
don't
know
if
you
have
an
answer
to
this
already
picture,
whether
you
like
this
version
of
swim
lanes
where
it's
not
swim,
lanes,
I,
guess
but
like
it's,
it's
scrunch
swim
lanes,
which
is
essentially
exerting
a
lot
of
space
or
yeah.
E
It's
different:
it's
a
different
approach
to
stimulants
I,
think
I
think
it
has
it's.
It's
like
both
approaches
have
they're
frozen
and
right,
but
I
really
like
like
is
what
you
were
saying
enjoy
once
you
know
what
the
colors
mean.
It's
it's.
It
works
right,
so
it's
really
good
that
it's
working
for
you
and
and
you've
made
this.
The
only
question
I
have
is
so
that,
for
example,
the
blue
ones,
the
one
that
have
blue
on
the
on
the
left,
those
mean
like
in
development
or
something
like
that.
E
D
I
forgot
I
forgot
to
mention
that,
but
he
is
filtering
a
bunch
of
labels.
So
the
point
is
this:
is
for
front-end
specific,
so
what
he
did
is
he
only
shows
the
certain
labels
that
might
make
sense
for
us
and
he
discards
all
the
rest.
Yes,
it
is
very
specific
for
us
in
this
case
you
wouldn't
happen,
but
to
your
point,
Pedro
even
me,
I
still
have
a
bit
of
confusing
confusion
between
what
the
colors
mean,
but
that
could
it
be
easily
solved
if
we
have
the
name
of
the
state.
Like
turn
wrote.
B
D
D
That
we
have
something
that
it
if
it
doesn't
have
a
deliverable
label,
you
will
be
highlighted
in
some
way.
I
think
that's.
It
I
think
it's
missing
the
deliverable
label
only,
even
though
we
can't
see
it
here
because
it's
probably
filtered
but
I,
think
that's
that's
what
it
means.
Yeah
I
think
that
I
didn't
put
it
here.
Yeah.
D
Katie's
here
and
just
put
the
link
there
for
you
guys
to
play
around
and
use
them
yourself
if
you
want
to
play
to
play
a
little
bit
for
now
again,
it's
very
specific
to
fronting
case
I,
really
like
this
specific
count,
which
could
be
at
the
bottom
of
the
screen
or
something
like
summary
of
the
whole
board
of
certain
special
labels.
Though
the
question
is:
how
can
we
make
this
so
generic
that
it
makes
sense
for
all
four
other
cases,
because
right
now,
this
is
just
a
label
right.
This
is
just
a
label.
D
B
A
E
We
can
also
do
the
other
way
around,
which
is
to
have
the
workflows
stages
or
whatever
you
want
to
call
them
as
the
columns
and
then
the
assignees
as
swim
lines
or
whatever
you
want,
and
then
you
can
have
these
counts
at
the
top
of
each
column.
So
you
see
right,
X,
number
of
open
with
X
number
of
wait
in
that
review
and
done,
while
still
being
able
to
just
see
groups
of
issues
for
assignee.
But
that's
again,
that's
another
approach
and.
D
It
depends
on
the
perspective
of
the
board
like
in
this
case.
This
board
is
to
manage
the
whole
team.
If,
if
you
were
managing
the
group,
you'd
probably
be
different,
but
one
of
the
things
that
I
liked
in
this
was
that
every
little
tweak
that
he
did,
except
from
the
filtering
of
the
labels,
he's
on
our
own
roadmap
and
we
have
ideas
and
have
been
discussing
them.
So
it's
not
that
we're
not
aware
of
them.
It's
just
that
we
haven't
gotten
to
them
yet
and
that
that
is
good.
D
A
good
sign,
I
think
we're
doing
our
job.
Okay.
For
for
the
feature
of
this,
so
good
job
team
group
right
group,
okay,
I'll,
stop
sharing
now
I'll
create
the
issue
and
I'll
update
this
agenda
to
have
the
issue
linked.
They
are
not
shared
on
this
like
channel
as
well
there.
That's
it
I,
don't
everything
else.