►
From YouTube: Plan | Weekly Sync (APAC) 2023-04-06
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
Welcome
to
plan
weekly
APAC
Edition
for
April
6
2023
first
item
is
demo
from
Rajan.
B
Yeah,
so
I
will
start
on
that.
It
is
basically
a
small
demo
regarding
one
notification:
widget
we
have
added,
it
is
similar
to
what
is
in
Mr.
Actually
I
noticed
that,
so
what
we
have
done
is
added
a
small
toggle,
which
is
basically
a
form
and
when
you
change
that
we
have
shown
one
post
similar
to
right
now,
what
has
been
shown
in
Mr
and
similar
this
thing
similar
works
for
our
models.
B
Also,
so,
if
you
open
any
key,
then
this
notification
will
work
there
also,
and
lastly,
we
have
tasks
and
lists
issues.
Sorry,
and
let
me
open
some
issue,
so
you
can
also
turn
on
off
notifications
for
your
task.
B
I
mean
I've
been,
and
that's
that's
what
it's
right
now.
C
B
B
Right
yeah,
if
it
had
been
some
complex,
widget
I,
will
definitely
move
to
Common.
B
Yeah
yeah,
that's
that's
more
of
it
right
now,.
A
Yeah
I
think
that's
all
we
have.
One
item
is
left
by
Jackie,
which
is
read
on
D,
but
I'll
still
verbalize
so
I
mean
she
mentioned,
often
not
being
able
to
attend
a
pack
session,
but
wanted
to
invite
anyone
with
any
questions
or
feedback
that
they
might
have
for
ux
team
to
to
add
to
the
agenda
document
so
that
she
can
respond
at
a
later
time.
D
C
A
A
I,
don't
think
we
do,
can
you
can
you
post
a
screenshot,
maybe
in
in
s
plan,
Fe,
Channel
or
even
product
planning,
Channel
and
I
can
take
a
look
at
it
and
see
if
we
have
issue
already
I'm
sure
it
it
must
be
a
minor
one,
probably
because
obviously,
if
some
bad
changes
that
we
might
have
done
recently,
yeah.
C
Okay,
I
just
wanted
to
ask,
is
the
subscription
on
for
this
notifications
widget
in
book
items.
No
okay,.
A
Yeah,
it's
it's
a
simple
mutation,
I
think
for
widgets,
like
this
one,
and
also
there
is
another
back-end
change
that
got
merged
last
week
only
which
was
around
to
do
support
for
work
items
that
also
won't
be
a
subscription
it.
It
would
be
a
plain
mutation
and
we
can
use
basically
other
things,
like
maybe
optimistic
updates
to
account
for
slower
requests,
because
we
noticed
that
even
for
to-do's
requests
are
taking
a
bit
longer
so
yeah.
A
Least
for
first
iteration,
we
have
not
decided
to
go
with
subscriptions
because
obviously
it
requires.
C
B
It
is,
it
is
also
for
individual
right.
It
is
not
like
it
should
be
a
feature
for
common
I
mean
it
is
not
common
between
folks.
So
basically,
if
I
have
turned
on
notifications,
it
would
be
only
for
me
right.
C
A
C
B
A
So
yeah
that
that
is
not
the
use
case
where
we
would
want
subscriptions
anyway,.