►
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).
B
B
A
So
and
I'll
add
the
color
context.
The
reason
why
we
created
plan
as
a
project
and
not
a
group
is
because
it
had
we
needed
to
have
issues
for
that.
We
could
collaborate
on
for
internal
things,
but-
and
you
can't
have
issues
at
the
group
level
so,
like
you
know
it's
a
conundrum
of
how
you
solve
this
problem
of
like
hey.
A
A
B
B
A
A
B
A
You'd
see
issues
from
the
project
below
it
that
would
roll
up
to
that
group,
but
but
the
purpose
of-
and
I
think
you
were
exploring
iterations
because
that's
the
thing
that
we
chose
to
dog
food
for
the
okr
for
dog
fooding
plan.
But
herein
lies
the
interesting
thing.
Let's
just
assume
we
did
create
a
plain
group
and
we
created
an
iteration
there.
Would
that
give
us
the
information
of
whether
or
not
like?
B
I
guess
it
depends
on
what
you're
trying
to
see
in
terms
of
iterations,
for
what
we
were
trying
to
see.
We
just
wanted
to
see
what
the
iteration
page
contained
for
plan.
So
what
initially
triggered
the
conversation
was
in
the
ux
showcase.
This
morning
it
wasn't
dimitri,
I
forget
who
actually
presented,
but
someone
presented
something
that
outlined
kind
of
a
road
map
for
next
steps
for
a
project
they
had
worked
on
recently
and
we
were
talking
about
you
know.
B
We
ideally
want
to
have
that
outline
for
these
larger
projects
like
iterations
of
boards,
we've
got
nbc
and
then
what
does
the
next
iteration
look
like
and
the
next
iteration
and
go
ahead
and
get
this
defined?
So
we
wanted
to
take
the
look
at
that
for
a
plan
and
that
was
kind
of
where
the
whole
conversation
came
about.
So
in
terms
of
seeing
that,
specifically,
it's
a
good
question
because
I
would
want
to
specifically
see
iterations
related
to
iterations
and
boards.
B
B
A
You
can
look
at
that
two
ways
like
the
way
that
we're
building
iterations
in
the
product
is
a
time
box
is
literally
like
a
fixed
period
of
weeks,
one
or
two
weeks.
You
could
also
look
at
the
way
that
that's
been
broken.
I
was
like.
What's
the
next
chunk
of
business
value
is
a
sub-epic
right
that
has
here's
the
feature
to
build
that
may
or
may
not
all
get
completed
within
a
given
like
time
period.
A
A
The
actual
gitlab
project
within
gitlab.org
right
so
and
a
project
can
only
have
one
parent
so
like
it.
It
can
only
ever
have
gitlab.org
as
a
group,
parent
or
some
other
subgroup
is
its
parent.
So
if
you
wanted
to
see
just
the
things
that
plan
was
working
on
across,
you
know
like
the
gitlab.org
group,
all
all
of
it
or
just
like
the
stuff
that
we
would
schedule
for
iterations,
which
would
be
in
like
the
getlab.org
project
or
the
gitlab
project.
B
So,
are
you
saying
that
if,
if
I
have
issues
within
a
project
and
that
project
is
in
a
subgroup
of
gitlab
org
called
plan,
for
example,
when
I
go
to
iterations
for
a
plan
group,
what
would
I
see?
Are
you
saying
that
I
would
not
see
anything
in
the
plan
project
because
it's
in
a
subgroup
and
it's
there's
like
a
middle
layer,
there.
A
Yeah,
no,
you
would
see
things
in
the
planned
project
if
it
was
directly
underneath
the
plant
group,
but
the
plan
team
itself
does
not
manage
its
issues
in
the
planned
project
because
we're
part
of
an
open
core
community
where
all
of
our
issue
management
for
our
product
happens
in
a
separate
project,
so
that
it's
easy
for
the
community
to
participate
without
having
to
like
hunt
through
all
of
our
different
org
level
groups.
To
find
the
right
thing
that
they
need
to
look
at
to
leave
a
comment
or
whatever.
B
A
A
So
so,
like,
let's
go
with
this,
the
problem
to
solve
is
if
we
create
a
if
we
can't
create
a
plan
group
and
given
our
current
structure
without
like
moving
everything
away,
and
we
want
to
create
plan
iterations
to
track
plan
work
there.
How
do
we
see
and
get
issues
that
are
in
a
sibling
project
or
group?
For
example,
the
gitlab
project
is
not
part
of
the
same
hierarchy.
B
B
A
Yeah
so
so
like,
in
this
view,
you're
at
the
top
level
group.
So
you
can
see
everything
right,
a
lot
of
organizations.
They
don't
give
access
to
everyone
at
the
top
level
group
or
they
don't
want
to.
They
want
to
give
just
you
access
to
plan.
So
you
can
see
just
the
plan
things
right,
but
in
this
case
the
plan
things
are
defined
by
a
label
in
another
project.
B
So
I
think
that
actually
one
of
the
one
of
the
things
that
michael
and
I
looked
at
that
may
tie
into
this-
was
he
pulled
up
the
plan.
Ux
group.
I
think
it
was
a
group
yeah
and
I
think
he
was
saying
we
could
create
an
iteration
here,
but
then
that
would
exclude
the
developers
I
would
think,
or
anyone
else
who
wanted
to
see
that
information
is
that
correct.
Is
that
kind
of
the
the
problem
that
you're
referring
to?
A
Among
other
things,
but
let's
look
at
also
what
what
happened
there,
as
you
switched
over
to
gitlab.com
top
level,
yeah
right,
so
you're
no
longer
in
the
dot
org
group
right.
So
let's
say
that-
and
this
is
another
good
example.
If
you
wanted
to
have
your
iterations
here,
how
are
you
ever
going
to
see
issues
that
are
in
the
gitlab.org
gitlab
project
here?
A
A
Oh,
I
don't
know
yet
I'm
still
working
through
it,
but
I'll
share.
If
you
want
to.
Let
me
share
my
screen.
I'll
run
you
through
some
of
the
things
that
we
were
working
on
and
it's
timely,
because
I
was
just
responding
to
a
comment
about
some
of
the
stuff
but
like
in
this
example
like
how
do
you
see
an
iteration
report
within
your
project,
you're
like
if
I'm
in
the
plan
project
in
iterations
of
the
group
level?
A
How
do
I
see
that
right,
and
so
one
way-
and
this
is
kong
and
mario
working
on
this
now?
But
you
have
your
group,
you
create
your
iteration
report
that
group
level.
So
in
our
case,
we
we
created
our
iterations
at
the
gitlab.org
level
and
we
would
want
to
eventually
be
able
to
expose
those
within
each
subgroup
and
within
each
project
so
that,
if
I
only
have
access
to
this
project,
I
only
see
the
issues
associated
with
this
iteration.
That
was
created
up
here
within
my
project
view
in
the
iteration
list.
A
And
this
solution
validation
issue-
this
is
kind
of
the
same.
The
whole
core
of
the
problem
is
that
considering
we
have
three
top-level
groups,
there
are
issues
I'm
assigned
to
in
subgroups
sub-projects
in
each
of
those
top-level
groups.
My
manager
wants
to
see
my
workload
in
a
board
of,
and
of
those
colleagues,
of
course.
So,
if
you
solve
this
problem,
you
also
consult
it
with
all
the
same
problems
like.
A
You
know
calling
it
whatever
but
then
making
it
so
that
they
can
be
shared
into
one
another,
and
if
you
share
into
one
another,
then
the
issues
can
will
show
up
in
both
places
so
like
if
space
4
gets
shared
into
space
d,
all
the
issues
from
space
4
will
be
visible
within
spaces
list
issue
list
and
could
be
assigned
to
you
know
space
these
iterations
or
whatever.
This
gets
kind
of
complicated
for
a
lot
of
reasons,
but
like
without
blowing
up
gitlab
like
there's,
not
a
ton
of
options.
A
Right,
one
of
the
other
things
that
we
were
looking
at
with
the
whole:
that's
why
the
whole
group
by
thing
was
there.
So
if
we
wanted
to
group
issues
by
label,
for
example
in
the
iteration
report,
you
would
go
to
the
the
getlab.org
iteration
list,
you
would
pick
the
current
iteration
and
then
we
could
group
them
by
label
like
let's
say
we
want
to
say
group,
project
management
or
group,
all
the
group
colon
colon
labels.
I
want
to
see
a
breakdown
of
that
and
you
could
see
a.
A
Of
progress
view
across
those
labels
within
the
given
iteration,
which
would
also
change
the
burn
down
chart
so
that
way
like
you
could
still
get
the
answers
you
want
of,
like
where's
plans,
iteration
report
within
the
context
of
the
broader
groups,
iteration
report.
So
that's
why
I
was
pushing
towards
this
type
of
solution
of
the.
B
A
B
A
B
B
B
A
A
A
A
B
A
A
There's
all
sorts
of
stuff
about
time
zones
and
then
the
configuration
for
like
this
is
where
we're
gonna
get
in
some
of
those
automation,
things
that
we
talked
about
so
moving
stories
from
one
iteration
to
the
next.
That
sort
of
thing,
there's
all
sorts
of
other
settings
too
so
iteration
length,
setting
that
how
long
your
things
are
project
setting
stuff.
B
I
appreciate
it.
This
does
remind
me
again
of
the
conversation
that
we
had
at
my
previous
job
about
giving
people
the
ability
to
like
officially
hit
a
stop
button
on
the
iteration
versus
the
company.
Defining
when
that
stop
time
is,
and
I
think
that
we
landed
on
giving
both
as
options
they
could
do
one
or
the
other,
depending
on
how
they
had
their
iterations
configured.
A
Yeah,
so
I
would
always
advocate
for
it
being
automated,
but
that's
fine
if
we
want
to
give
folks
the
option
to
manually.
Do
it
the
reason.
Why
is
the
whole
point
of
using
a
time
box
and
iteration
is
so
that
you
can
get
the
velocity
so
that
you
can
help
set
estimations
of
what
you
and
commitments
can
get
done
in
the
future?
And
if
you
have
time
boxes
of
varying
durations
and.
A
Yeah,
you
increase
your
volatility
because
you
could
get
more
stuff
done
than
the
extra
day
or
whatever,
which
breaks
the
whole
point
of
it,
which
is
what
I
appreciate
about
pivotal
trackers
like
screw,
that,
like
just
we're,
gonna,
have
the
same
cadence
so
that
you
have
same
measurements
and
anyways.
So
I'll
stop,
recording.