►
From YouTube: Plan stage weekly - 2022-12-15
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).
A
Cool
welcome
plan
stage,
weekly
December
15th
I
have
the
first
comment
all
right:
it's
not
really
a
design
team
preview,
but
it
just
saw
that
we
relaxed
the
requirement
a.
A
A
You
just
have
to
add
a
comment
saying
that
this
is
the
reason
why
you
didn't
why
you
didn't
use
the
roulette,
but
yeah
just
wanted
to
bring
that
to
everyone's
attention
in
case
you're
like
me,
and
didn't
see
that
until
today,
okay,
any
questions
on
any
of
that
cool
demos.
Let's
start
with
the
okr
management
demos
control,
you
wanna,
yep,.
B
Yeah,
so
let
me
share
my
screen
and
I'll
demo,
okay.
So
what
I'm
demoing
today
is
basically
the
tree
view
with
all
the
additional
attributes
that
weren't
visible
before
so
as
you
can
see,
I
have
the
preview
with
key
results
and
objectives
with
all
the
other
metadata
options
like
the
Milestone
assignees
and
labels
visible.
So
let's
go
ahead
and
try
to
create
a
new
objective
from
scratch
and
then
add
a
bunch
of
attributes
and
then
we'll
see
whether
review
shows
it
correctly
or
not.
B
If
I
click
on
new
key
new
objective
and
say
object
to
two
and
I
click
on
create,
so
it
gets
added.
The
form
remains
open
because
in
case
user
wants
to
create
multiple
objectives
in
one
go.
They
can
do
that
now,
since
this
objective
doesn't
have
any
attributes,
so
it
doesn't
show
anything
and
everything
is
aligned
in
the
middle.
But
if
I
open
this
objective
separately
and
assign
a
couple
of
attributes
like
say,
I
want
to
assign
multiple
assignees
and
then
one
to
also
set
a
bunch
of
labels.
B
We
can
also
do
scope,
labels,
so
I,
add
the
label
and
then
I
also
add
a
milestone.
So
once
I
do
that,
since
the
tree
view
is
not
real
time,
which
means
that
we
need
to
reload
the
tree
to
reflect
these
changes,
but
now,
as
you
can
see,
that
all
the
attributes
that
I
added
are
now
visible
here,
the
behavior
of
all
these
different
attributes
is
similar
to
how
we
are
doing
it
in
other
places.
B
So
if
you
look
at
child
epics
and
issues
within
epic
page
then
hovering
over
Milestone
will
show
all
the
details
like
what
the
Milestone
title
is
and
what
is
the
time
frame
of
it,
whether
it
is
past
due
or
not
so,
for
example,
this
Milestone
is
past
due
so
it
so
it
shows
that
it,
it
was
expired
a
month
ago.
So
all
those
information
is
visible
as
it
is.
We
are
using
the
same
component
to
do
that
for
assignees.
In
case
there
are
more
than
two
assignees.
B
Then
we
use
a
GL
Avatar
inline
component,
which
supports
collapsing
additional
assignees
and
combines
the
names
within
this
badge
and
yeah
attributes
are
visible
even
on
all
the
children
items,
so
you
can
go
ahead
and
add
attributes
to
these
values
so
yeah,
that
is
about
it
and
yeah.
One
more
thing
like
in
in
the
test
project
that
we
have
on
gitlab.com,
it
doesn't
show
ability
to
create
or
add
key
results,
but
we
already
have
an
MR
open,
I've
linked
it
to
our
agenda.
B
It
is
this
one,
so
this
merge
request
once
merged
user
will
be
able
to
see
these
two
options
in
the
ad
drop
down
in
in
gitlab.com
and
as
far
as
the
attributes
Mr
is
concerned,
so
this
Mr
is
also
ready.
It
is
this
one,
so
I've
added
all
the
tests
and
everything
it
is
now
just
a
matter
of
adding
the
ux
review
getting
that
approval
and
then
we'll
send
it
for
final
reviews.
So
this
basically
covers
around
70
percent
of
what
we
wanted
to
do
with
the
tree.
B
What
remains
now
are
two
things.
Basically,
progress
information,
so
we
are
waiting
for
scg
groups
Mr,
which
is
basically
adding
the
progress
widget
within
the
objectives,
so
once
those
two
Mrs
get
merged,
we'll
be
able
to
consume
that
information
within
the
tree
view.
Similarly,
although
for
the
MVC,
we
didn't
plan
to
include
health
status,
but
the
health
status
widget
is
very
close
to
completion,
which
means
that
we
may
be
able
to
accommodate
health
status
within
the
within
the
tree.
B
D
B
Yeah,
so
this
is
the
smallest
size
that
GL
Avatar
in
line
component
supports,
which
is
24
pixels,
so
we
need
to
add
support
for
even
smaller
size,
maybe
16
pixels
in
case
it
supports
it.
But
this
is
also
first
time
where
we
are
using
a
tree
like
widget,
along
with
assignees
yeah.
So
this
is
the
first
instance
where
we
are
using
this,
so
maybe
we
can.
B
We
can
Target
it,
maybe
as
a
part
of
refinements,
once
the
core
functionality
is
complete,
so
yeah
I
agree
and
even
the
this
component
itself
is
not
White
accurately
laid
out
like,
for
instance,
if
you,
if
you
inspect
this
particular
container
notice.
What
is
happening
here
like
if
I,
expand
and
highlight
this
one?
So
since
we
are
using
absolute
positioning
with
custom
left
and
right
attributes,
the
container
element
for
all
the
three
items
is
basically
smaller
than.
C
B
So
what
the
this
problem
leads
to
is
we
need
to
offset
this
additional
clipping
by
providing
more
margin
to
the
labels
container.
So
if
you
look
at
the
labels
container,
which
is
adjacent,
I,
had
to
basically
offset
additional
margin
due
to
that,
otherwise
it
would
basically
go
underneath
the
assignees
and
I've
also
raised
it
in
gitlab,
UI
channel
and
apparently
it's
a
known
issue.
So
hopefully
this
will
get
fixed
so
yeah.
B
There
are
a
couple
of
issues
with
this
component,
but
since
this
was
the
fastest
way
to
have
this
sort
of
layout,
I
think
we
can
live
with
it
as
far
as
MBC
is
concerned.
So.
D
C
B
Yeah,
so
we
we
don't
don't
so
we
do
support
Auto
completion
like
if
you
go
to
existing
and
the
moment
you
click
it.
It
will
show
all
the
objectives.
Similarly,
if
you
go
to
existing
key
results,
it
will
show
all
the
existing
key
results
which
are
available
to
set.
The
thing
is
that,
as
far
as
combined
options
within
the
drop
down
is
concerned,
that's
a
different
conversation,
because
this
has
been
a
case
with
child
issues
and
epics
as
well,
and
there
too
also
we
have
the
similar
drop
down.
B
So
maybe
we
can
tackle
both
of
them
as
a
part
of
ux
discussion
and
see
what
we
can
do
there
I
think
the
motivation
behind
having
a
single
button
was
to
not
pollute
the
header
a
lot,
especially
in
smaller
screens.
Like
the
moment,
you
shrink
it
past
a
certain
size
you
can
imagine
like
if
this
is.
If
this
title
is
shown
in
a
different
Locale,
then
chances
are
that
it
will
overlap
and
maybe
wrap
around.
C
B
Okay,
yeah:
we
we
had
to
implement
this
drop
down
from
scratch.
Although
the
component
is
smaller
one
but
yeah,
we
can
certainly
use
the
issues.
Button
I
think
the
problem
with
having
not
having
a
shared
drop
down
component
is
because,
if
you
look
at
child
issues
and
epic
widget,
which
is
also
a
preview,
it
is
all
dependent
on
rest
API
and
it
doesn't
account
for
work
item
types.
So
right
now,
if
you
open
this
drop
down
and
select
one
of
these
items,
we
are
passing
the
exact
work
item
type
depending
on
what
backend
provided
with.
B
On
the
other
hand,
the
drop
down
button
in
the
tree
widget
uses
string
enums
to
pass
the
relevant
type
and
shows
the
form
accordingly
but
yeah
once
both
of
them
are
work
item
we
might
as
well
reuse
the
whole
tree
and
I
think
that's
the
motivation
why
we
created
that
review
from
scratch.
We
we
want
to
reuse
this
whole
tree
as
it
is
for
epics
as
well.
Once
all
the
epics
are
also
work
items.
B
A
Yep
yeah,
so
then,
can
you
show
me
what
the
query
for
getting
the
children
here
in
the
tree
view
looks
like.
B
Sure
so
I
have
just
a
second.
Let
me
fix
something
quickly,
yeah.
So
if,
if
you
go
to
this
work,
item,
work
Items
app
within
the
core
part
of
our
application.
All
the
queries
that
we
use
here
is
is
available
within
this
app.
So
if
you
go
to
graphql,
folder
I'll
I'll
also
share
the
link
to
this
file.
So
when
the
page
is
loaded,
we
are
basically
loading.
B
This
work
item
fragment,
which
is
part
of
the
base
page,
but
for
the
children
we
have
work
item
widgets
fragment,
which
is
responsible
for
fetching
all
the
widgets
for
the
for
the
all
the
children.
So
right
now,
since
children's
also
Show
additional
metadata,
we
are
adding
those
widgets
within
the
children
connection,
so
we
have
hierarchy
Milestone,
assignees
and
labels,
because
the
hierarchy
widget
represents
whether
this
particular
child
is
expandable
or
not,
and
once
it
is
expanded.
We
use
a
different
query,
which
is
work
item
tree
query,
which
is
similar.
B
So
there's
a
lot
of
duplication
going
on
in
terms
of
these
fragments,
like
I,
would
rather
have
a
single
place
where
I
can
just
Define
what
metadata
I
want
to
show
for
this
entire
page,
especially
for
the
tree
part,
and
it
should
be
available
in
all
the
children
items
as
well,
but,
as
you
can
see,
I
had
to
Define
Milestone
assignees
and
labels
four
times,
which
was
on
the
children
items
on
the
base
item
itself,
as
well
as
on
the
actual
widgets
fragment
which
is
here.
B
So
we
would
want
to
reduce
this
duplication
a
bit.
We
can
create
a
widgets
fragment
and
then
reuse.
It
everywhere
else,
because
right
now,
the
entire
query
splitting
that
is
happening
for
the
work
items
is
very
complicated
to
wrap
our
hands
around
so
yeah,
okay,.
A
Yeah
yeah
I
was
just
wondering
if
we
were
using
widgets
and
yeah.
It
definitely
looks
like
we
are,
which
I
think
is
good.
A
That's
that
has
hierarchy
I'd.
Imagine
we
are
not
going
to
want
to
show,
or
at
least
give
we'll
want
to
give
users
the
option
to
not
show
everything
that
we're
showing
here,
because,
like
once,
we
have
what
yeah.
B
So
yeah
exactly
I
I
understand,
because
if
you
look
at
our
epics
to
review
there,
we
do
have
a
toggle
to
hide
labels
when
we
don't
want
to
see
them,
and
we
would
want
to
replicate
that
behavior
here
as
well,
like
just
ability
to
turn
on
and
off.
The
thing
is
that
this
config
is
preserved
on
a
user
preference,
which
is
not
the
case
in
this.
B
One
like
I,
was
planning
to
maybe
use
a
local
storage
to
at
least
give
some
option
to
hide
the
metadata,
or
maybe
at
least
hide
the
labels,
because
the
motivation
of
adding
labels
as
a
part
of
okrs
MVC
was
to
replicate
health
status
in
some
way,
and
it
was
literally
mentioned
in
the
original
requirements
that
we
want
to
use
labels
as
a
replacement
for
health
status.
B
For
now,
while
we
wait
for
health
status
availability,
but
since
we
are
closer
to
having
health
status,
widget
like
the
backend
Mr
already
got
merged
and
Nicholas
has
back
front-end
Mr
already
open.
We
are
now
aiming
for
health
status
to
be
part
of
MVC,
which
means
that
labels
will
mostly
be
used
to
identify
which
category
and
okr
belongs
to
or
an
objective
or
a
key
result
belongs
to
so
yeah.
It
would
certainly
be
useful
to
hide
labels
when
they
are
not
needed.
So
I
can
basically
add
a
toggle
which
is
purely
front
end.
B
B
It
would
hide
them
but
optional,
since
it
is
part
of
local
storage,
I,
think
technically,
we
can
prevent
fetching
as
well.
It
would
require
looking
at
how
we
can
selectively
load
fragments,
because,
right
now
it
is
all
defined
in
the
query,
so
we'll
have
to
figure
out
a
way
to
not
Define
this
fragment
when
the
local
storage
flag
is
not
enabled
so
yeah.
A
Do
we,
the
toggling
of
the
entire
Widget,
the
tree
view.
A
B
B
Yeah
so
yeah,
so
this
is
also
something
that
we
want
to
tackle
before
GA
and
I.
Think
in
epics
we
don't
even
have
that.
We
have
an
open
issue
for
front
end,
which
is
easier
for
someone
new
in
the
team
to
implement
that
toggle.
But
what
we
can
do
is
we
can
basically
make
use
of
this
toggle
by
not
fetching
the
children
when
the
widget
is
collapsed,
to
save
some
bandwidth
there.
So.
A
Yeah
definitely
and
then
so,
I
wonder
I'm
working
on
on
click
opening
it
up
in
the
modal
instead
of
the
full
detail,
view
okay,
but
when
we
do
that,
because
the
children
I
think
are
kind
of
deep
in
the
deep
in
Apollo
cache,
because
ideally
we'd
be
able
to
render
the
modal
with
all
of
the
all
the
data
we've
already
queried
within
this
tree,
View.
B
And
I
I
looked
at
the
implementation
of
how
model
worked
and
I
discussed
it
with
Natalia
as
well
and
yeah
I
mean
it
is
not
as
straightforward
as
we
would
like.
So
that's
the
reason
why
I
fixed
the
breadcrumbs
part
first,
because
we
don't
want
to
prevent
user
from
navigating
and
drilling
down
individual
items,
so
you
can
basically
click
on
any
child
from
the
Tree
View,
and
it
will
take
you
to
that
page.
So
user
is
not
blocked
like
there
is
still
a
workaround.
B
It
is
just
that
user
would
have
to
wait
for
the
page
reload
to
happen
and,
for
instance,
if
user
is
on
multiple
levels,
deep
child,
then
there
is
no
way
to
go
to
the
top
level
objective.
From
this
view.
So
I
don't
know
whether
breadcrumbs
supports
having
multiple
parents
all
the
way
up
to
the
root
parent
within
the
breadth
terms,
so
yeah,
but
right
now,
navigation
is
still
possible.
It
is
just
that
we
would
have
to
click
multiple
times
to
reach
the
parent
objective.
B
We
only
support
immediate
parent,
but
then
we
basically
end
up
in
a
house
recursive
situation
where
how
deep
do
we
go
to
fetch
the
Banning
information?
Technically,
it
is
possible,
like
when
I
open
any
work
item
and
look
at
what
information
is
available.
There
is
a
value
present
which
mentions
like
which
particular
parent.
This
work
item
belongs
to
in
this
case,
since
it
doesn't
have
any
hierarchy.
B
Oh
sorry,
yes
yeah!
So
if
I
look
at
this
one
in
the
widgets
within
the
a
hierarchy,
I
think
there
is
an
option
to
have
information
about
the
parent
like
which
parent
this
particular
widget
belongs
to.
So
there
is
a
way
to
fetch
it,
but
yeah
like.
A
E
But
then,
just
something
in
mind
when
I
click
on
any
objective
I
like
I,
already
have
the
tree.
Yeah
I,
don't
know
where
to
save
that,
while
clicking
it
at
least
if
I
like,
for
example,
I
click
on
the
fourth
item
in
the
tree.
I
know
the
objective
one
two
three
I
just
had
to
calculate
here
and
when
I
click
on
the
link,
maybe
I
can
save
it
somewhere
in
the
URL
or
something,
and
that's
too
much
for
the
URL
I
know.
B
Yeah
I
mean
if,
if
we
were
using
the
view
router
to
navigate
between
the
children,
it
would
have
still
been
possible,
like
we
can
inject
the
information
as
a
powder
part
of
router
object
and
consume
it
there,
so
that
we
wouldn't
have
to
worry
about,
like
which
particular
objective
hierarchy.
This
objective
belongs
to
but
yeah.
Since
we
are
not
using
router,
we
are
making
the
navigation
here.
It
won't
be
possible
to
preserve
that
intention.
E
A
B
Yeah
that
was
already
proposed
for
epics
right
now.
If
you
switch
parent
to
any
work
item,
it
will
basically
switch
it
silently
without
informing
user.
So,
for
instance,
if
you
look
at
this
sub
child
key
result,
one
which
belongs
to
objective
one.
It
is
an
indirect
child
of
sample
objective.
It
is
not
a
direct
child,
but
I
can
technically
go
ahead
and
click
on
existing
select
this
one
and
add
it,
and
at
that
point
see
that
it,
it
basically
got
yeah.
B
So
at
this
point
you
can
see
that
both
of
them
are
visible,
because
tree
is
not
real
time.
So,
if
I
reload
the
page
and
then
expand
objective
one.
This
basically
is
part
of
direct
children
of
sample
objective
and
is
not
present
anywhere
in
the
middle
of
the
tree.
B
So
right
now
you
can
switch
parents
without
any
user
confirmation,
and
that
was
reported.
Like
I
mean
when
I
was
having
it
ux
reviewed.
When
we
had
the
first
mr4
review
opened
like
there
was
a
feedback
on
you,
basically,
where
a
user
was
able
to
set
an
item
to
a
different
parent
without
any
information
on
what
exactly
happened
like
whether
the
parent
was
switched
or
whether
the
item
got
assigned
to
multiple
parents.
B
Is
the
parent
by
visiting
that
parent
first
so,
for
example,
right
now
this
key
result?
It
is
part
of
simple
objective,
but
now
I
want
to
move
it
to
objective
one
then
I
would
need
to
visit
objective
once
work
item,
page
click
on
existing
key
result,
and
here
it
is
and
I
can
click
on
ADD
and
it
will
show
up
here,
but
obviously
this
tree
will
not
be
updated
right
away.
B
D
B
The
review
not
yet
okay,
yeah
in,
in
fact
we
are
fetching
all
the
children,
along
with
the
base
Page
information
when
the
page
is
loaded
for
the
first
time.
Ideally,
I
would
want
to
separate
both
the
queries,
so
the
page
load
gets
loaded
first
and
then
directly
runs
are
loaded.
But
if
you
see
when
I
reload
this
page
for
the
first
time,
everything
is
shown
up
at
once,
I
don't
think
we
are
batching
two
queries
at
once.
B
We
are
only
making
one
query,
which
is
this
query
work
item,
and
we
are
just
passing
the
information
of
this
particular
work
item.
But
since
it
is
part
of
the
same
query,
I
can
open
and
inspect
the
hierarchy
for
this
particular
sample,
objective,
query
and
within
children.
B
I
have
all
the
direct
children
which
are
part
of
the
tree,
so
ideally
I
would
want
to
separate
both
the
queries
so
that
Pages
gets
loaded
first
and
then
there
is
another
query
which
is
fetching
just
the
children,
but
that's
again
not
strictly
for
MVC,
but
I
would
do
it
most.
Probably
in
first
week
of
January,
once
we
have
the
core
functionality
available.
B
B
Maybe
it
will
be
easier
to
have
a
subscription
like
we
do,
support
subscriptions
on
other
attributes,
so
I
don't
know
whether
it
is
possible
to
have
subscription
on
hierarchy
widget
itself,
because
then
it
will
be
possible
to
get
this
tree
updated.
B
It
is
just
that
if
we
are
doing
the
subscription
route,
then
the
way
it
will
work
is
a
bit
tricky
to
understand,
because
at
this
point
suppose
I
have
all
the
children's
expanded
all
the
way,
and
if
I
am
updating
something
with
the
pastry,
it
will
refetch
the
base
tree,
but
it
will
not
know
whether
there
are
any
children
which
are
expanded
or
not.
B
Yeah
so
at
this
point,
I
think
it
is
easier
to
have
a
rather
dumb
implementation,
where
we
don't
refetch
and
maybe
show
a
warning
or
an
information
within
the
widget
saying
that
you
switched
parents
to
one
of
the
children.
So
do
you
want
to
refetch,
and
maybe
we
can
make
that
operation
async
like
providing
a
refresh
action
here
and
it
will
just
call
a
refetch
action
on
the
Apollo
ready
rather
than
reloading
the
whole
page.
Yeah.
A
I
almost
wonder
if
we
should
have
for
each
of
these
child
items
like
within
the
hierarchy.
Widget,
we
only
return
work
item
IDs
like
we
can
only
query
work
item
IDs
and
then
we
have
a
separate
like
root
level,
query
for
every
work
item
items
and
then
that,
because
they're
all
batch
together
anyway,.
D
B
If
you
look
at
like,
we
are
fetching
a
lot
of
information
at
once
at
this
point,
and
let
me
check
like
what
was
the
size
like.
We
are
basically
downloaded
18
KBS
of
information
and
that
too,
in
a
rather
simple
tree,
where
we
have
several
more
items
are
available
like
if
you
expand
and
look
at
the
response
preview
like
there's
a
lot
of
information
that
we
are,
including
within
this
payload,
that
we
don't
need
to
at
least
on
the
page
route,
so
I
think
first
way
to
fix.
B
B
Yeah
yeah,
except
that
we
are
not
fetching
the
indirect
children.
So
if
you
look
at
this
tree,
we
have
information
up
to
objective
one,
but
we
don't
have
information
of
these
three
values.
These
are
fetched
only
when
the
objective
is
expanded,
so
if
I
close
it
and
we
have
around
eight
items
industry.
So
if
I
reload
the
page
and
look
at
the
response,
then
the
children
within
the
hierarchy
will
only
have
eight
items
at
the
most.
B
Here
it
is
so
we
have
eight
items
in
total,
but
when
we
expand
a
child
it
makes
another
query
and
then
it
fetches
the
information
of
other
children,
and
we
are
caching
the
response.
Once
an
item
is
expanded,
so
that
is
already
sorted.
It
is
just
that
we
shouldn't
be
combining
the
base
objective
information
and
the
hierarchy
objective.
Information
in
in
one
query.
E
E
B
Yeah,
so
one
is
for
current
user
and
I
think
it
may
be
foreign.
B
So
this
is
for
pre-fetching,
so
we
have
prefetching
mechanism
in
place
like
if
you
hover
over
any
item
notice
how
just
on
Hover
it
got
expanded.
So
this
is
actually
a
side
effect
of
the
tasks
list
where
we
supported
prefetching
when
the
model
is
opened
like.
If
you
go
to
any
issue
where
there
are
tasks,
we
can
technically
pre-fetch
all
the
task
list
items
upon
hours,
so
model
dialogue,
opening
it
is
faster
wait.
Let
me
find
an
issue
which
has
a
task
present.
B
So
we
have
this
issue
where
the
task
is
present,
if
I
clear
this
list
and
if
I
just
hover
notice,
how
a
request
happened
right
on
Hover.
So
when
I
click
on
this
model
opens
instantly
instead
of
user
waiting
for
the
data
to
be
loaded
within
the
model,
so
that
there's
a
way
to
turn
it
off,
like
my
Mr,
is
still
in
draft,
but
I
will
not
combine
turning
off
prefetching
for
objectives,
at
least
but
yeah.
That
additional
query
is
just
so.
A
Okay,
on
the:
how
are
we
handling
the?
How
are
we
handling
Apollo
cash
when
you're
loading
more
when
you're
loading,
the
children?
Are
we
just
injecting
it
to
the
so.
B
So
we
are
using
a
component
recursively
here
like
the
component,
which
is
responsible
for
rendering
the
top
level.
Children
is
also
responsible
for
rendering
subtree
and
it
is,
it
is
basically
part
of
the
same
Apollo
cache.
So
when
I
load
the
subtree,
it
knows
that
objective,
one
which
belong
to
the
top
level
objective,
got
further
hierarchy.
Children
which
are
now
available
at
at
a
subpoid
level,
so
we
are
using
the
same
Apollo
object
across
all
the
sub
trees.
B
So
if
you
remove
it
basically
ensures
that
the
removal
happens
instantly
there
you
go
so
since
there
is
no
information
available.
There
is
another
interesting
caveat
where
no
children
is
available,
but
when
I
click
on
expand,
nothing
happens.
But
the
query
continues
to
happen
so
yeah
there
are
still
a
few
minor
glitches
that
we'll
need
to
fix
once
we
have
the
core
functionality
ready
and
write
query
for
some
reason:
wasn't
working
correctly,
so
I
have
an
issue
open,
which
was
basically
around
implementing
cash
eviction
in
in
some
way.
B
So,
if
I
go
to
the
issues,
we
have
an
issue
that
I
created
so
just
a
second.
B
B
So,
for
example,
if
I
remove
one
of
the
children
which
belongs
to
the
top
level
objective-
and
we
are
on
the
root
page,
so
removal
happens,
predictably,
where
we
show
our
tools
with
undo
action
and
when
I
click
on
undo
the
child
is
added
back,
but
this
behavior
is
not
available
when
I
do
it
for
a
child
for
a
child
which
is
indirect.
So
if
I
remove
this
object
from
here,
it
gets
removed.
But
there
is
no
toast
and
there
is
no
way
to
undo
that
action
and
as
a
side
effect
If.
B
The
child
was
the
only
child
for
the
supre.
Then
the
button
will
remain
here.
So
that
is
because
we
are
not
clearing
the
cache
correctly
when
this
happens,
and
it
is
not
as
straightforward.
So
we
have
created
a
follow-up
issue
which
will
be
not
part
of
MVC,
because
it
is
not
as
simple
to
do
right
away.
B
B
It
was
the
implementation,
was
quite
complicated
to
be
honest,
and
there
was
no
way
to
split
that
Mr,
so
Natalia
helped
multiple
times
throughout
the
past
couple
of
weeks.
While
we
were
getting
that
Mr
for
review
and
and
merge
and
then
Kong
reviewed
it
and
made
some
good
suggestions
so
shout
out
to
both
of
them.
D
A
B
Yeah
yeah
so
so
key
result,
related
backend
is
already
merged.
It
is
just
that
we
had
turned
off
ability
to
create
key
result
or
add
key
result,
because
back-end
was
not
ready
back
then
so
I've
opened
another
front-end
Mr
and
it
is
currently
waiting
for
ux
approval,
I'm
working
with
ux
designer
there
to
sort
it
out,
and
hopefully
it
will
get
merged
by
end
of
day
today,
I'm
aiming
for
this
Mr
to
get
reviewed
and
merged
by
end
of
this
week.
So
that's
starting
next
week
on
test
projects
within
gitlab.com.
B
We
will
have
most
of
the
information
available
to
try
it
out,
and
next
week's
goal,
like
I
mentioned,
is
having
a
progress.
Widget
and
health
status.
B
So
I
I
key
results
will
be
showing
up
within
issues
list,
but
I
don't
think
we
have
ability
to
filter
issues
list
with
key
result
as
one
of
the
supported
types
it.
It
only
has
objectives,
so
we
will
need
to
implement
a
new
token
value
for
type
within
the
issues
list
so
that
key
results
start
showing
up
there
but
yeah
it's
it's
a
minor
follow-up
and
will
be
purely
front
end.
Just
a
matter
of
adding
the
correct
levels:
cool.
B
C
A
D
C
So
I've
I've
not
added
the
Avatar.
This
is
just
where
I
want
to
I've
got
this
little
add
a
comment
button
and
then
you
get
the
little.
C
We've
got
both
of
different
text
field
formats
and
then
yeah,
we're
gonna,
add
some
text
here.
Let's
make
a
strong
text
and
we
save
this,
but
this
is
just
for
adding
comments
so
to
actually
view
them,
and
this
next
product
is
really
going
to
amaze.
You
got
a
query
here,
but
only
comments
and
we
we
hopefully
have
one
in
his
year
involved.
Here
we
go.
Look
at
that.
There's
a
coin
that
I
just
added.
D
C
D
C
It
Is
by
note
ID.
If
we
have
we
have
this,
but
it's
not
possible.
D
C
D
A
C
B
It
also
supports
sorting
chronologically
right.
Yes,.
D
A
E
E
D
D
E
Yeah
so
I
remember
seeing
the
last
video
in
the
demo
and
I
fixed
it
in
the
AMR
yeah
I.
Remember
seeing
the
notes
in
the
agenda
and
I
was
like,
let
me
just
fix
it.
So
that's.
D
E
E
B
So
I'll
just
pasted
the
link
to
that
issue.
So
in
case
your
Mr
gets
deployed
and
if,
if
you
can
try
it
out
on
github.com
I,
don't
think
but.
B
D
A
All
right
nicely
done
Simon
in,
like
the
you
got
that
up
quickly,
but
that's
exciting
to
see
that
to
see
the
ability
to
add
comments
to
it
already.
E
Okay,
so
my
demo,
so
the
first
Mr
included
just
fetching
and
showing
the
list
and
making
sure
the
work
item
notes.
Query
is
fed
separately
and
not
as
a
part
of
the
main
query.
So
right
now,
if
you
see
which
I
show
in
the
last
one.
So
there
are
two
three
use
cases
which
I'll
show
one
which
has
the
next
space,
one
which
does
not
have
the
next
page
and
with
sorting.
So
what
I'm
going
to
show
is
sorting
and
pagination
together.
E
So
here,
if
you
see
that
we
have
very
little
imagination,
the
notes
are
there,
it's
visible.
The
component
is
new,
which
is
copied
now,
and
the
last
demo
I
said
we're
using
the
same
alert
management
component,
but
we
are
not
because
we
are
facing
some
use
cases
which
are
not
handled
in
that
and
we
ended
up
creating
a
new
one,
just
copied
from
the
system
node
from
issues
without
WX
dependency
and
in
the
future.
E
We
plan
to
use
the
same
component
for
issues
as
well:
okay,
so
by
default,
if
you
see
the
Sorting
is
oldest
first
and-
and
this
is
the
first
page,
there's
no
like
no-brainer,
we
have
the
work
item
notes
query.
E
So
the
page
size
is
30..
I
have
used
the
same
page
size
which
is
used
for
issues
which
increment
which
increases
incrementally,
which
is
the
batch
discussion,
which
is
the
logic
the
same
as
it
is
in
issues
which
I'll
show
in
the
next
task
and
if
I
just
change
the
Sorting,
the
Sorting
is
in
front
end.
We
have
all
the
layers
we're
just
reversing
it,
and
another
thing
is
the
Sorting
direction
is
saved
in
local
storage.
E
So,
if
I
refresh
this
again,
the
Sorting
direction
will
be
saved
and
it
is
in
us
first.
So
this
is
one
thing
which
is
there
as
a
part
of
local
storage
thing
in
the
activity
filter.
What
we
are
going
to
do
in
this
in
the
same
mile
is
going
to
keep
the
filters
in
the
Sorting
separately
like
it's
not
in
the
issues
we
have
the
Sorting
in
the
filter.
In
the
same
thing,
now,
let's
come
to
a
task
with
like.
E
D
E
Okay,
so
if
you
see
here,
you
see,
the
button
was
disabled
till
the
time,
I'm
fetching
all
the
system
nodes
here
yeah,
so
it
is
so
it
is
fetched
in
batches
but
I'm
fetching
like
in
Parts.
If
you
see
the
first
one
is
with
page
size,
30
and
then
it
is
with
page
size.
E
E
So
that's
how
it
is
I
can
do
30,
300
hundred
hundred,
which
is
it's
a
small
change.
I
just
wanted
to
make
sure
that
I
have
I,
have
no
idea
why
this
logic
is
present
on
issues,
but
I've
tried
to
keep
it
the
same.
The
logic
which
is
on
issues,
but
we
can
change
it
anyhow,
it's
not
a
big
thing,
yeah
one.
What
I've
done
here
is
the
on
the
first
load.
Only
there's
in
it
it
is
I've.
E
It
is
an
intersection
Observer
which
is
placed
at
the
top,
and
it
keeps
on
calling
up
here
till
the
time
we
have
loaded,
all
the
them.
I
wanted
to
which
I
can
show
what
we
wanted
to
achieve
here
is
load
on
demand
like
at
the
end,
but
the
problem
is
that
is,
since
the
Sorting
is
on
the
fronted.
I
have
to
make
sure
that
I
have
like
I
anyways
have
to
fetch
all
of
them
at
the
same
time,
when
I'm,
sorting
and
on
loading.
E
So
that's
one
thing:
what
we
can
do
is
we
can,
you
know,
load
more
on
oldest,
first
load
on
demand
and
oldest
first
and
not
a
news
first,
which
is
I'm,
not
sure,
I'll
give
it
for
ux
review
and
maybe
what
Nick
suggests,
but
what
I
thought
the
best
is
make
sure
that
the
same
we
are
fetching
it
in
batches
for
all
and,
for
example,
if
it's
newest
first
I,
you
can
see
the
loader
till
the
time
I'm
like
fetched
all
and.
E
Yeah
and
then
it
just
fetches
all
and
at
one
time
fetch
All,
In,
Reverse,
so
yeah,
that's
pagination
and
sorting.
There
is
one
point
that
we're
not
sorting,
so
you
know
regularly
people
don't
sort
a
lot,
so
we
may
want
to
choose
to
load
a
scroll
on
demand.
What
I
can
do
to
show
it
to?
You
is,
let
me
just
how
it
works.
In
oldest.
D
E
E
So
that
is
one
thing,
but
it
works
well
with
like
when
you
don't
have
to
sort
and
it's
not
newest.
First,
yes,
so
that's
the
thing
I
was
facing.
Apollo
queries.
Where
the
work
item
notes
and
the
work
item
notes,
query
and
the
work
item
query
was
were
conflicting
and
every
time
the
update
was
called
it
was,
you
know,
fetching
the
workout
notes
every
time
and
that's
why
in
the
demo
last
time
it
is
not
real
time
and
still
we
were
able
to
see.
E
The
latest
updates
was
because
it
was
fetching
the
academy
notes
again,
which
should
not
have
happened.
That's
why
that
was
a
bug
and
subscription
will
come
later
on
in
the
separate
Mr
with
there
are
separate
several
use
cases
which
we
need
to
handle
here
is
toggle
committee
list,
see
this
description
lives
and
one
or
two
that
Simon
mentioned
is.
We
can
also
combine,
for
example,
if
I
change
the
description
together.
A
couple
of
events
that
things
that
are
you
know
have
the
same
activity.
We
can
combine
them.
E
So
this
Mr
I'll
give
for
ux
review
today
and
hopefully
it
will
be
merged
before
I
go
publication
yeah.
So
that's
that's
about
it.
A
B
Yeah
so,
like
lately,
I've
been
noticing
that
every
time
I
assign
any
okrs
related
MR2
a
ux
designer
who
isn't
part
of
plan
state,
then
chances
are
they.
They
don't
exactly
have
information
on
which
feature
Flags
they
need
to
have
enabled,
and
although
I
try
to
keep
as
much
information
within
the
merge
request.
Description
like
these
are
the
feature
Flags.
B
You
need
to
have
enabled
on
your
project
to
be
able
to
see
the
information,
but
still
it
is
hard
for
them
to
reproduce
and
and
again
I
I
wouldn't
blame
them,
because
I
think
the
the
entire
feature
flag
situation
we
have
around
work
items
and
okrs
in
general
is
fairly
complicated,
like
even
I
struggled
initially
when
I
was
working
on
smaller
issues
around
okrs,
where
I
wouldn't
know
like
okay
I
need
to
enable
this
particular
feature
flag
for
this
feature
and
this
flag
or
this
feature.
B
So
is
there
a
way
to
basically
streamline
it
in
in
some
way?
If,
if
we
can
get
rid
of
any
additional
feature,
flies
that
we
don't
want
like
even
like,
particularly
if
you
look
at
just
these
MVC
feature
flags
that
we
have
around
work
items.
These
are
fairly
hard
to
keep
track
of.
Even
for
the
okrs.
We
have
two
feature
Flags,
which
is
different
from
work.
Item
feature
Flags
like
right.
Now
you
need
to
enable
one
feature:
flag,
called
database
restrictions
and
another
one
called
okrs
MVC.
B
Only
after
these
two
feature
flags
are
enabled
you
will
be
able
to
see
anything
around
okrs,
but
then
chances
are
that.
If
someone
visits
the
worker
item
page
then
somethings
may
still
not
show
up
for
them,
because
they
don't
have
relevant
work
items
and
PC
feature
flag
enabled
so
I
I
feel
that
if,
if
there
is
a
way
from
blackened
well,
we
just
toggle
a
simple
switch
and
it
it
turns
on
everything
for
someone
who
wants
to
try
out
any
feature
around
okrs
or
work
items
in
general.
E
So
I
have
a
question:
I
don't
know
I.
So
what
I
was
trying
to
do
yesterday
to
check
that
the
hierarchy
and
notes
are
I
could
not
actually
see
Collective
and
I.
Myself
was
wondering
what
feature
flag
am
I
missing
and
then
I
figured
out
that.
Why
isn't
that?
Behind
the
mvc2
flag
I
mean
because,
like
is
okr
stuff,
we
decided
to
keep
the
okr
as
a
separate
thing.
B
Yeah,
so
if
you
look
at
okrs,
it
is
basically
for
internal
team
use
once
it
once
the
MPC
is
available
and
everything
that
we
are
building
for
okrs
is
like
some
of
the
implementations
that
we
are
doing
is
very
specific
to
okrs.
B
It
is
not
around
generic
work
items
in
in
in
terms
of
features,
so,
although
we
may
be
adding
new
widget
types
which
are
on
top
of
work
items,
but
they
are
not
strictly
for
okrs
and
every
time
we
are
working
on
any
feature
which
is
relevant
just
for
work
items,
but
although
it
is
getting
used
for
okrs,
we
are
not
using
okrs
feature
flag,
but
the
hierarchy
widget
that
you
see
within
the
work
items
page
that
depends
on
having
okrs
related
feature
flag
in
place,
which
means
that
if
you
want
to
create
objective
on
a
project
level,
you
need
to
ensure
that
a
certain
feature
flag
is
enabled
which
is
okrs
underscore
MVC.
B
Then
there
is
back-end
feature
flag,
called
database
restrictions,
which
is
very
specific
to
okrs,
like
we
want
to
make
sure
that
user
is
able
to
create
key
results.
Only
inside
objectives.
Key
results
will
not
be
allowed
to
be
created
within
a
project
at
a
root
level.
Similarly,
you
cannot
create
more
than
100
children
for
any
objective.
So
that
is
another
restriction
and
one
more
restriction
is
the
depth
like.
You
cannot
go
more
than
nine
levels
deep
when
you
are
creating
objectives
within
objectives
and
so
on.
B
So
that's
the
confusing
part
that
I
think
we
need
to
address
in
general
I
for
both
reviewers
and
users,
who
want
to
try
it
out
locally.
E
Yeah
for
me
as
well
I
couldn't
really
honestly
I
tried,
I
went
to
the
New
Path
and
I
was
like
okay.
This
is
an
objective
and
now
I
see
it's
an
issue.
I'm,
like
I,
created
an
objective
yesterday.
It's
an
issue
so
yeah
I
myself,
don't
know.
Is
this
documented
somewhere
I?
Don't
know,
I
missed
that?
Maybe
when.
B
It
was
yeah
so
so
before
so.
The
due
date
for
MVC
is
a
January
18th
and
we
plan
to
update
the
documentation
in
terms
of
which
features
are
because,
since
it
is
an
internal
use,
only
we
are
not
updating
our
documentation.
B
Otherwise
it
will
start
showing
up
for
customers
and
users
as
well,
which
we
don't
want,
but
what
we
can
do
is
we
can
make
it
a
part
of
similar
to
architectural
blueprint,
just
that
it
won't
strictly
be
a
blueprint,
because
it's
a
feature
and
not
a
framework
or
a
foundation,
so
yeah
I
think
having
a
centralized
documentation
just
around
okrs,
where
user
can
know
which
feature
Flags
to
turn
on
should
be
possible,
but
for
for
that
purpose,
only
if
you
go
to
gitlab
okrs
project,
which
is
on
on
top
of
our
agenda
I,
have
added
as
much
information
within
the
readme
of
that
project
and
we
can
do
similar
to
work
items
as
well.
B
Where
I
have
added
the
information
like
which
feature
Flags.
We
need
to
enable
to
be
able
to
see
it.
It
is.
It
is
selected
here,
so
we
can
do
that
similar
to
in
in
plant
test
project
as
well.
We
can
basically
add
a
readme
to
that
project
and
provide
the
information
like
which
feature
flag.
You
need
to
enable
to
see
what
so,
at
least
for
internal
testing
and
usage
purposes.
Someone
can
just
look
at
the
readme
and
know
okay.
They
need
to
enable
these
feature
flights.
A
Yeah,
so
that's
that's
listed
out
in
the
in
the
work
items
blueprint
linked
on
what
is
it
three
c
I
yeah
so
there's
two
sections
there
there's
one
that
that
talks
through
what
our
initial
plan
was
for
feature
Flags,
where
we
were
planning
on
just
using
more
of
a
promotion
style
process
there,
as
opposed
to
having
to
keep
track
of
like
a
different
feature
flag
for
every
widget
and
turning
off
and
on
each
of
those
and
then
worrying
about
dependencies
and
everything.
A
The
plan
was
to
just
have
three
feature
flags
for
each
different
phase:
that
the
widget
or
work
item
is
in
so
one
feature
flag
turns
it
on
for
or
one
feature
flag
is
turned
on
for
just
the
plan
stage
project.
The
next
feature
flag
is
turned
on
for
gitlabore,
Oregon,
kitlab
com
and
then
the
last
feature
flag
is
turned
on
for
all
of
gitlit.com
and
then
the
next
step
would
be
to
get
it
out
of
feature
Flags
completely
with
okrs.
A
Like
you
said
it's
a
little
bit
of
a
one-off,
so
yeah
the
feature
flags
are
a
little
bit
different
with
okrs,
but
maybe
we
should
list
it
in
the
blueprint
also
or
at
least
link
to
the
to
the
to
the
wiki
or
to
the
readme
in
the
okrs
test
project
that
you
created
yeah,
but
there's
also
a
section
in
the
blueprint
that
lists
off
all
the
widgets
that
have
been
created
and
where
those
are
in
the
feature
flag,
promotion
process.
A
So
what
feature
flag
they're
behind
I
think
we've
been
doing
a
decent
job
of
updating
that
as
widgets
go
through
the
process,
but
yeah.
We
want
to
make
sure
that
we
keep.
We
keep
updating
that
I'm
trying
to
think
I.
Think
Milestone
was
the
last
one
that
went
out
of
the
feature
flag
process
and
that
one's
definitely
updated
in
the
blueprint.
A
Actually
we
have
six
because
we
have
one
for
the
tasks
within
issue
page
that
was
an
old
like
Legacy
feature
flag.
That's
not
that's
not
following
that
process,
yet
either:
okay,
oh
it's
top
of
the
hour
I
think
everything
else
can
be
read.
Only
I
like
having
the
Apec
meeting
at
this
date
and
time
day
and
time,
but
if
you
all
want
to
change
it
to
a
different
day.
Just
add
a
comment
to
no.
D
D
B
A
Night,
but
not
not
Sunday,
night,
yeah,
okay
and
then
playing
Team
day.
If
you
all
want
to
post
or
attend,
go
to
that
issue
with
that
John
link
there.