►
From YouTube: Plan | Weekly Sync (APAC) 2022-11-17
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
Yay
welcome
to
plan
weekly
APAC
Edition.
This
is
15th
November.
We
have
first
item
in
the
agenda.
It
was
posted
by
John,
but
it's
async,
so
I'll
read
it
anyway.
Plan
team
will
be
onboarding
a
couple
of
contractors
for
the
months
December
and
January,
and
we'll
basically
have
them
work
on
okr,
as
well
as
any
any
backlog
for
the
plan
stage
goal
of
having
the
contractors
is
mostly
for
okr
related
stuff,
so
that
main
team
members
can
focus
on
the
okrs.
A
While
contractors
can
focus
on
any
backlog
items
as
well
as
any
simpler
tasks
around
okrs.
If
we
need
it
to
be,
there
will
be
eight
team
members
in
total
who
will
join
in
and
out
of
those
three
will
be
joining
in
in
product
planning.
Those
will
be
reporting
to
me.
Remaining
team
members
will
be
working
on
service
desk
related
stuff,
but
we
are
yet
to
figure
out
whom
they
will
report
to.
A
It
may
either
be
yarka,
because
service
desk
is
certify
and
or
or
it
may
it
may
be
that
they
directly
report
so
and
yeah
we'll
we'll
definitely
have
behavioral
interviews
for
them
starting
next
week.
So
we'll
have
more
information,
as
we
know
concrete
details
about
who
are
the
team
members
when
they
join
in,
but
yeah
I
expect
them
to
be
also
participating
in
these
team
calls
for
the
months
December
and
January.
A
Yep
second
item
is
okrs
demos.
Over
to
you.
B
Yeah,
just
let
me
know
when
you
can
see
my
screen:
yep
yeah,
so
it's
pretty
minor
demo,
it's
already
available
in
my
weekly
update
video
as
well,
which
is
out
there
on
the
marketing
website.
So
last
couple
of
weeks,
what
we
were
doing
is
we
were.
We
have
added
a
way
to
add
objectives
to
the
issue
list
thing
and
the
entire
process
is
behind
the
feature
flag.
So
you
need
to
enable
okrs
MVC
feature
flag
and
you
need
to
have
ultimate
license
as
well
to
see
the
changes.
B
So
if
you
go
to
any
project
and
issue
list
of
that
project,
you're
going
to
see
a
button
which
says
new
objective,
this
button
is
going
to
be
inside
a
drop
down
with
the
new
issue
in
the
follow-up
member.
Now
on
click
of
new
objective,
a
form
will
be
shown
here,
wherein
we
just
take
the
input
of
title
right
once
user
enters
title,
they
can
just
click,
create
objective
which
will
create
the
objective
and
the
form
goes
away,
and
now
we
don't
have
icon
Set.
B
There
is
currently
an
issue
which
is
ongoing
where
we'll
get
a
brand
new
icons
for
objective
and
key
results
once
they
are
there,
we
are
going
to
update
them
as
well
now,
on
click
of
the
created
objective
link
user
will
be
navigated
to
the
work
item.
Show
page,
which
is
pretty
much
most
of
you
guys
might
have,
are
aware
of
this
particular
screen
so
yeah.
B
This
is
what
has
happened
so
far,
so
the
coming
coming
weeks,
I'll
be
working
on
a
progress
widget
for
okrs
we're
planning
to
make
it
more
generic
as
possible.
We're
having
discussions
around
it
so
assume
there
is
going
to
be
a
progress
field
somewhere
here
and
then
once
hierarchy
widget
is
done.
We
are
going
to
integrate
that
here,
where
we'll
have
opportunity
of
career
where
we'll
leverage
the
child,
widgets
and
hierarchy
widgets
to
create
key
results
as
well
as
sub-objectives
yeah.
B
So
that's
the
plan,
any
questions
all
right.
A
No
I
think
I'm
glad
that
we
no
longer
have
the
persistent
form
within
the
issues
list.
I
think
that
was
the
biggest
concern
that
most
of
us
had
yeah
I
mean
even
if
we
don't
do
the
drop
down
for
the
MVC,
we
just
go
with
the
clean
button
or
a
new
objective.
A
It
is
still
better
than
what
we
had
earlier
and
I
I
spoke
to
Amanda
earlier
this
week,
asking
like
how
this
form
will
show
up
in
different
projects,
and
she
mentioned
that
we
are
going
to
enable
this
feature
flag
only
on
a
particular
project
where
okrs
will
be
used
by
relevant
team
members,
which
means
that
users
are
not
going
to
see
this
button
or
the
form
in
the
gitlab
project
itself.
A
So
yeah
and
I
don't
know
how
we
are
going
to
allow
linking
issues
from
gitlab
Project
over
to
the
objectives
and
key
results
within
a
different
project,
which
is
the
okrs
project,
so
to
speak,
but
yeah
that
that
is
a
question
to
be
answered
in
future.
But
for
now
I
think
good.
B
Yeah
I
mean
this
also
brings
up
your
question
around
flipping
the
feature
flag,
right
question
which
is
put
by
John
I
guess.
So
we
do
have
a
rollout
issue
kushal,
but
that
that
we
are
only
going
to
flip
the
feature
flag
in
prediction.
Only
for
one
project
for
MVC
only
when
featured
becomes
viable,
which
is
mostly
end
of
q1
or
maybe
mid
Q,
two
or
q3s.
C
A
Yeah,
so
we
can
follow
the
steps,
as
mentioned
in
the
rollout
issue,
like
first
enemy
Legend
on
staging
and
then
testing
it
out.
What
we
can
do,
though,
is
even
if
the
feature
is
not
in
a
viable
State.
We
don't
enable
it
on
the
actual
project
where
PMs
need
it,
but
we
can
still
enable
it
on
the
test
project,
which
is
which
belongs
to
plan
stage,
so
that
team
members
can
at
least
try
it
out
and
provide
any
feedback
if
they
have
yeah
makes
sense
flurry.
The
next
feature
in
this
okrs.
D
A
D
That
might
also
help
us
use
it
pretty
quickly
so
yeah.
Basically,
my
I'm
gonna
share
my
screen
as
well.
What
I've
been
working
on
is
the
hierarchy
widget.
So
it's
basically
like
the
next
step.
After
what
ebola
has
just
demoed?
It's
not
currently
it's
not
merged
yet
so
on
and
like.
If
a
work
item
is
of
the
type
objective,
we
will
display
this
widget.
D
Currently
it's
just
empty
and
we
have
these
options
to
add
existing
or
create
new
objectives
or
key
results
and
I'm
also
I've
also
started
implementing
like
the
different
forms.
So
originally
the
plan
was
to
reuse
epic
tree
for
this
and,
as
I
started
sort
of
like
rendering
it
on
this
page
and
tried
to
wire
it
all
up.
I
realized
that
it
was
very
cumbersome.
D
It
would
require
a
lot
of
conditions,
so
I've
created
like
a
a
shell,
that's
specifically
for
this
and
I'm
reusing
the
form
components
from
task
hierarchy
and
because
the
forms
are
similar,
it's
just
the
labels
are
different
and
we
use
different
types,
but
it's
all
the
same
queries
we
just
like
use
objectives
and
key
results
instead
of
tasks.
D
The
rest
is
the
same,
and
when
we
display
children
we'll
have
the
ability
to
Nest,
which
we
currently
do
not
have
on
tasks,
so
that
will
be
a
like
a
an
improved
version
of
that
to
add
the
nested
ability
following
the
pattern
of
epic
tree,
but
not
reusing
those
components
directly.
Only
the
patterns
because,
like
it's,
it
has
a
vieweg
state
like
the
just.
The
component
itself,
is
of
ux
app,
which
is
very
heavy
and
Bloated.
D
So
we
don't
want
to
use
it
here
and
the
the
huge
advantage
of
doing
this
is
that
I'm
making
this
component
adaptive
for
all
the
work
item
types.
So
it
will
work
for
all
work
item
hierarchy
in
the
future.
So
it's
like
we're
even
working
ahead
for
all
workout
and
hierarchy.
D
Beyond
okrs,
which
I
think
is
pretty
cool.
D
Well,
it's
just
getting
started
like
we
can't
display
children,
yet
that
will
be
the
next
the
next
step,
but
yeah
I
actually
found
it
so
much
easier
to
reuse.
The
work
item
forms
to
tasks
instead
of
the
epic
tree,
like
I
wasted
so
much
time
on
epic
tree
and
like
like
I
spent
hours
on
it,
and
it
was
so
difficult
and
this
I
just
put
it
together
really
quickly.
So.
A
Yeah
I
think
when
we
started
working
on
a
big
street,
like
obviously
we
had
to
use
bux
because
we
were
using
rest
apis.
There.
D
A
No
graphql
back
then,
but
then
it
further
complicated
the
implementation
when
we
decided
to
add
support
for,
drag
and
drop
to
reorder
and
not
just
reorder.
We
also
allowed
user
to
drag
an
epic
onto
another
epic
to
create
the
nesting
and
all
that
API
is
still
rest.
I,
don't
know
how
it
is
going
to
work
out
with
graphql
and
view
draggable.
The
library
itself
that
we
are
using
to
support
that
drag
and
drop
is
a
mess.
So
I
don't
know
how
we're
going
to
handle
that
channel.
D
Implementation,
especially
since
we
won't
have
reorder
abilities
at
the
beginning,
I'd,
rather
just
like
detach
ourselves
from
that
and
see
how
like
is
the
graphical
and
when
it's
going
to
be
completely
different.
So
that's
also.
Another
issue
is
like
the
Epic.
Api
is
quite
different
from
the
work
item
API,
whereas
here
of
like
we
already
have
tasks
using
the
work
item
API,
so
it
fits
way
better,
but
yeah
we
learn.
We
didn't
have
time
for
a
spike
for
this,
so
I'm
kind
of
just
winging.
It.
B
Yeah
I
agree
with
you:
kushal,
not
just
views,
draggable
I,
think
any
draggable
Library
out
there
drag
and
drop
library
is
a
mess.
In
my
personal
opinion,
flurry.
This
is
looking
really
great
I,
really
like
what
exactly
I'm
seeing
now
right.
So
thanks
for
working
on
this,
if
you
don't
mind,
can
you
shape
the
draft
URL,
because
I'm
still
in
the
learning
curve,
I
would
be
happy
to
see
you.
B
You
share
the
Mr,
which
is.
D
Course,
I'll
put
it
in
the
agenda.
D
You
go
it's
on
my
demo
item
in
the
agenda,
so
you
can
so
you
can
check
it
that
way.
D
Yeah,
so
this
was
just
merged
yesterday
and
like
this
is
for
tasks,
but
we're
going
to
use
the
exact
same
component
and
workflow
for
okrs.
So
keep
that
in
mind,
so
we
edited
like
we
only
had
when
we
were
clicking
it.
D
This
used
to
be
a
button,
and
it
would
just
create
a
new
task
like
this,
but
now
we
have
the
existing
task
option,
which
uses
a
token
selector
input
which
allows
us
to
add
multiple
tasks,
work
items,
I
would
say
to
an
issue
in
this
case,
but
it
means
we
can
add
multiple
key
results
and
objectives
at
once
on
an
objective
once
this
is
all
connected
like
once.
D
We
have
an
API
to
do
that,
so
we
just
add
it
and
it
adds
multiple
tasks
at
once
like
this
on
your
shoes,
so
yeah.
This
is
like
this
is
super
useful
people
have
been
asking
for
this
for
tasks
and
it's
definitely
also
a
requirement
for
okrs
and
key
results.
It's
also
we're
iterating
on
this.
D
So
currently
we
can
only
search
by
title
and
add
by
title,
but
there
will
be
future
iterations
after
MVC,
probably
to
add
using
the
ID
or
the
URL,
because
that's
also
been
required
by
customers,
but
at
least
it
gives
the
ability
to
not
have
orphan
tasks
anymore,
like
we
can
always
re-add
them
or
move
them
across
issues
very
easily.
Now
any
questions
or
comments
on
this.
C
A
Yeah
so
I,
yes,
sir,
go
ahead.
B
Super
awesome
flurry
for
doing
this
and
picking
the
same
thing
for
okrs
I
can
instantly
feel
the
relief
that
we
are
going
to
get
in
okrs
post
MVC,
because,
generally,
what
happens
is
we
create?
Ceo
cares
Standalone,
we
create
all
the
ctOS
and
other
level.
Okay
are
Standalone,
then
the
linking
happens,
not
a
single
tool
out.
There
allows
group
linking
group
aligning
out
there.
B
D
Yeah,
it's
a
pretty
nifty
I'm,
also,
really
glad
we
got
this
merged
before
the
15
6
cut
off
it.
This
feature
for
tasks
is
making
15
6,
which
honestly
I
didn't
think
it
was
going
to
make
it
because
the
decision
to
ship
this
with
just
the
search
and
AD
by
title
was
made
last
week.
I
think
we.
D
So
I
kind
of
like
rushed
it
and
did
my
best
and
she's
not
on
the
meeting
today,
but
Natalia.
Thank
you
for
the
maintainer
review
and
making
sure
we
made
it
too
15-6.
So
it's
super
exciting.
A
Yep
so
I
had
just
one
question
again,
not
something
to
to
be
concerned
about,
but
does
it
support,
fuzzy
searching
I
mean
does
searching
happen
locally.
D
D
Must
have
been
gone
on
the
back
end
because
I
didn't
do
any
changes
on
the
front
end
unless
okay,
so
I'm,
using
a
gitlab
UI
component.
That.
A
D
Which
might
do
if
there's
each
search,
because
so
as
far
as
I
know,
the
backend
only
does
matches
on
four
words:
okay,
but
we
might
have.
But
if
it
works
on
fuzzy,
then
it
just.
D
C
D
Will
share
this?
The
excitement
of
this
thing
working
so
I
have
I
guess
just.
A
Type
in
blh
and
see
if
it
if
it
brings
just
type
blh.
D
A
D
D
A
So,
if,
if
the
requests
are
not
happening
in
real
time,
and
if
these
results
are
pulled
in
locally
within
the
app
itself,
then
I
think
adding
first
order
in
plus
to
to
the
mixed
and
support
fuzzy.
Surging
might
be
useful.
I
mean
I'll,
take
a
dig
at
it
now
that
it
is
merged.
I
I
have
some
time
free
to
see
if
I
can
integrate
it
before
PST
cut
off
happens
for
the
15
yeah.
D
Because
there's
also
questions
about,
like
so
I
think
it
only
returns,
100
records
at
a
time.
So
there's
also
the
question
of
what,
if
there's
more
than
a
hundred
when
you
search,
because
you
don't
get
everything
when
you
you
search,
it
needs
to
like
talk
to
the
API
again
to
like
search
beyond
that
hundred
still
matching
that
string,
Etc,
so
there's
obviously
more
tested.
C
A
And
I
recall
Heinrich,
discussing
support
for
fuzzy
searching
on
the
backend
side
for
the
apis,
because.
A
Yeah
because
it
was
asked
for
especially
in
the
navigation
drop
down
where
we
can
search
for
a
project
within
the
drop
down
itself
on
the
Top
Nail
Bar
of
gitlab
and
there
it
it
never
pulled
in
the
right
result.
I
mean
you
would
type
gitlab
and
expect
that
it
would
bring
in
the
correct
project,
but
it
would
always
bring
up
some
other
project
from
gitlab
or
group
and
not
the
actual
project.
A
Yep
I
just
made
it
in
time.
What
did
I
make
it
in
time
for
to
not
see
demos,
no.
A
Yeah
so
I
think
that
was
all
for
the
demos
and
the
last
item
is
more
of
an
fii.
It
is
basically
around
plan
engineering
Q
for
okrs,
so
we
have
four
okrs
as
of
now
like
complete
annual
training
assessment
in
workday
Implement
objectives
and
key
results
within
gitlab,
which
we
are
already
doing
it
and
show
the
demos
for
established
plan
as
leaders
in
enhancing
gitlabs
product
development
flow,
which
I
think
we
will
eventually
once
we
have
okrs
and
other
stuff
in
Implement
significant
performance
enhancements,
which
has
been
the
ongoing
initiative
within
plan
stage.
A
Now
that
Natalia
is
principal
and
she
can
focus
on
some
higher
level
items
on
different
and
performance
improvements.
So
yeah
encourage
you
to
take
a
look
at
the
details
behind
all
those
okrs
social
time.
A
Let
me
stop
the
recording
and
then
we
can
use
this.