►
From YouTube: Fulfillment Release Kick Off 13.0
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
A
I've
indicated
just
a
high-level
summary
of
what
we
have
for
backhand
in
front
end
by
workflow
labels,
so
I'm
wondering
if
anybody
has
any
issues
which
are
in
dev
or
in
review
any
of
these
here
that
you
think
are
not
going
to
require
much
dev
work
at
all
are
almost
done.
That
sort
of
thing
please,
let
me
know,
because
I'm
looking
to
pull
some
a
couple
of
issues
out
for
both
front
end
and
back
end
to
make
sure
that
we're
successful
and
I
want
to
know
how
much
I
need
to
pull
out.
A
B
A
Okay
and
then
the
other
thing
is
I,
find
myself
having
a
hard
time
distinguishing
which
of
the
issues
like
as
as
the
team
digs
into
bigger
issues,
and
they
make
kind
of
sub
issues
that
they
they.
They
need
for
these
big
initiatives
that
we
have
I'm
having
a
hard
time
figuring
out
if
those
sub
issues
are
urgent,
if
they
need
to
be
done
in
the
current
milestone
if
they
could
be
scheduled
on
the
next
or
in
a
future.
A
So
I
would
just
ask
that,
as
we
create
those
issues
either
put
a
note
that
basically
says
you
know
this
is
not
urgent
or
use
a
severity
label,
or
something
to
just
note
to
me
that
this
needs
to
be
placed
in
the
current
milestone
or
in
the
next
one,
or
it
can
be
placed
out
three
milestones
from
now.
That
sort
of
thing.
A
They're
not
assigned
a
milestone
so
like
I'll,
just
give
an
example
Tyler,
as
he's
digging
in
the
ceiling
or
to
the
automated
billing
he's
creating
all
these
smaller
issues
of
things
that
need
to
happen,
and
it's
mostly
behind
the
scenes.
Kind
of
stuff
and
I.
Don't
really
know
is
that
something
that
has
to
be
completed
in
the
current
milestone.
Or
is
that
just
a
reminder
for
him
for
later?
You
know
and
he's
not
feeling
everybody
does
this,
which
I
think
is
completely
valid
and
I
just
don't
know
from
a
planning
perspective.
C
B
All
the
times
they
just
create
it
because
they
found
like
something
that
may
need
to
be
done
later,
but
they
can
put
a
milestone
because
they
don't
know
other
priorities.
Of
course,
oh
I
think
I
think
what
we
were
me.
We
may
want
to
mention
it
to
the
engineers
to
make
sure
that
the
EMS
and
the
PM
deserve
among
the
dead
being
on
those
issues.
So
we
can
surprise
it
yeah.
A
B
A
B
Thing
to
mention
here
is
there.
Sometimes
engineers
may
may
work
on
something
really
small,
maybe
Mac
know
been
worth
an
issue,
but
they
may
create
a
shoe
anyway
and
I
think
those
ones
they
may
want
to
work
on
the
same
milestone.
There
should
be
fine,
like
those
that
have
like
a
weight
of
one
may
yeah
may
take
like
a
couple
of
hours
for
them.
I
think
we
encourage,
in
general,
in
development
in
dnas
to
to
the
leave
of
those
anyway,
and
we
can
add
into
the
same
milestone.
Yeah.
A
And
I'm
fine
with
that
yeah,
you
know
if
it's,
it
is
not
necessarily
a
blocker,
but
it's
such
a
quick
piece
of
work
and
it's
related
to
what
you're
doing
anyway
totally
fine
and
go
ahead
and
put
the
current
milestone
on
that.
But
first
stuff,
that's
like
a
reminder.
We
need
to
do
this
next
milestone
or
in
the
next
two
to
three
milestones:
let's
have
the
engineers
ping
me
and
just
let
me
know
the
priority
and
then
I'll
put
it
in
the
upcoming
milestone.
Well,
thank
you
highlight
here
that
we
have.
A
The
deliverable
label
is
back,
so
what
we're
trying
to
do
is
is
kind
of
disregard
the
priority
labels,
because
those
are
used
for
planning
to
which
milestone.
It
should
be
in
not
priority
of
work
within
the
milestone.
So
when
we
look
at
the
the
planning
board,
I'm
sorry
the
issue
board,
we
will
see
that
the
the
issues
are
in
priority
order.
I
still
have
them
in
priority
order,
but
we're
the
deliverable
label
is
mentioned.
That's
something
that
we
really
want
to
get
out
in
the
milestone.
A
So,
if
anything
has
to
slip,
it
should
be
something
that
doesn't
have
the
deliverable
label
essentially
I'm,
trying
to
make
the
deliverable
label
a
smaller
percent
of
what
we've
been
seeing
this
milestone.
Unfortunately,
it's
a
little
bit
larger
because
we
brought
a
big
one
over
as
well
and
so
moving
forward
were
aiming
for
a
smaller
percent
there,
but
looking
for
a
good
mix
of
deliverable
feature
bug
as
well
as
work
that
the
engineers
can
pick
themselves.
A
A
How
we
delivered
deliverable
is
specific
to
within
the
milestone,
thinks
that
we
want
to
deliver
good
question
all
right
and
then
I
also
created
a
label
call
to
affect
Salesforce
anytime,
that
that
label
is
on
which
right
now
I
will
manually
apply,
but
in
the
future,
James
will
automate,
which
J
would
be
awesome.
If
that's
on
during
mr
review,
you
want
to
ping
Jack
Brennan
for
review
so
that
he
can
sign
off
that
our
work
hasn't
unintentionally
broken
Salesforce
or
done
anything
that
he
didn't
expect
alright.
So
those
were
the
only
agenda
points.
B
What
well
I
think
related.
Today's
is
that
we
have
to
see
how
this
works
out
the
pinging
jack
on
the
meta
quests.
Normally
with
unexpect,
we
used
to
take
too
long,
get
back
to
the
most
requester
and
review
of
them.
So
I
know
jack
is
quite
busy
and
having
just
a
single
person
to
do
this.
It
may
happen
that
we
may
want
to
reconsider
this
and
maybe
change.
B
This
is
likely
to
perhaps
create
a
follow-up
issue
for
Jack
to
review
later
on
or
something
that
but
I'm
happy
to
you
know
just
keep
it
as
it
is
now
I
added
to
the
oddities
to
the
mess
across
template
for
engineers
to
be
aware
of,
and
then
we'll
see
what
happens.
But
if
the
real
times
are
affected,
then
we
should
definitely
do
in
a
different
way.
Yeah.
A
And
I
I
had
that
concerned
myself
because
just
from
a
requirements
perspective
when
I
ping
Jack,
sometimes
he
it
takes
a
few
days
to
get
an
answer
because
he
is
so
busy
and
I
actually
basically
said
that
to
him
and
he
said
4mr
reviews
that
he
will
guarantee
a
same
or
next
day
response.
So
that
he's
not
slowing
us
down.
So
it's
definitely
something
to
keep
our
eye
on
and
I
think.
A
Maybe
if
we
go
through,
you
know
milestone
or
two
and
it's
going
well
great
if
it's
not
yeah,
let's,
let's
try
a
different
process
and
I
just
want
to
point
out
that
I'll
I
will
be
applying
the
label
to
the
issue.
So
if
mrs
are
made
related
to
the
issue,
make
sure
that
you
know
you're
looking
at
the
label
at
the
issue
level,
all
right
so
we'll
take
a
quick
look
here
at
the
board.
I
just
moved
work
over
from
1210.
A
So
if
there's
stuff
here
that
shouldn't
be
here
that
you
think
should
be
closed
out,
let
me
know
in
the
open
we
have
I'm
working
with
legal
to
update
terms
as
a
result
of
the
quarterly
billing.
So
that's
what
this
is:
it's
not
coming
into
any
of
your
limbs
and
then
some
sales
collateral.
So
don't
worry
about
that.
Okay,
so
the
the
quarterly
billing
is
still
in
process
and
we
had
a
late
change.
So
I
expect
that
that
would
cause
more
work
there.
A
Although
I
think
this
is
still
showing
us
blocked,
but
I
don't
know
why.
So
maybe
we
can
just
look
into
why
that's
yeah?
Is
there
actually
a
blocker
and
then
this
is
all
related
work,
so
this
is
letting
the
users
know
about
the
charge
coming
up
giving
them.
This
is
an
email.
This
is
a
banner
okay.
So
here's
the
new
work.
So
the
new
work
for
this
milestone
is
the
customers
portal
customization
for
resellers.
This
is
a
whole
rework
of
basically
how
the
customers
portal
reacts
to
the
data
it
receives
from
Zoara.
A
So
the
TLDR
here
is,
if
zara
passes
a
flag
which
jack
has
a
related
issue
for,
and
he-
and
I
told
him
if
you
don't
get
the
work
done.
That's
fine
just
tell
us
what
what
the
flag
will
be,
so
we
can
code
for
it.
So
if
zora
passes
a
flag
instead
of
provisioning,
the
customers
portal
in
the
customers-
name,
which
is
what
we
do
today-
provision
it
in
the
invoice
customer
or
the
invoice
account
name
and
contact
details.
A
A
Okay,
future
data
licenses.
So
this
is
the
early
renewal.
Basically,
if
today
for
self
managed,
if
somebody
renews
30
days
early,
they
get
the
license
30
days
early
and
they
load
it
30
days
early,
it
will
become
available
immediately.
It
will
give
those
entitlements
on
the
day
you
load
it,
regardless
of
the
start
date
this.
This
prevents
that
so
Tyler
already
spec
to
this
and
found
a
much
easier
way
of
handling
this
than
when
I
was
suggesting,
which
I'm
super
happy
about,
and
basically
it's
just
going
to
the
job.
A
That's
saying
which
license
should
I
use
right
now
and
instead
of
just
using
whatever
is
the
most
recent
loaded
use,
the
one
that
has
the
proper
start
date.
I
need
you
to
deal
with
that
and
then
the
next
one
is
seat,
link
data
being
made
available
to
sales,
so
we're
waiting
for
some
information
back
from
jack
on
this
one.
But
what
he
has
suggested
is
that
we
just
passed
the
seat,
link
data
to
Zora
and
then
he's
going
to
take
it
and
make
it
available
in
an
object
in
Salesforce
or
something
so.
A
Whoever
takes
this
one,
please
don't
be
afraid
to
reach
out
to
jack
he's,
put
several
comments.
He
actually
had
a
related
issue.
Where
is
it
here?
So
he
had
a
related
issue
which
I
closed
as
a
duplicate,
but
he
essentially
stated
how
it
should
work
in
this
issue.
So
if
you're
not
sure
reach
out
to
him
and
copy
me,
so
I
can
stay
on
top
of
him.
A
Alright,
it's
okay!
I'll
fix
it!
Thank
you
web
Drex.
This
is
a
new
bug
that
was
just
found
and
it's
a
pretty
big
priority.
I'm
gonna
have
a
hard
time
figure
out
what
to
take
out
of
this
milestone.
You
have
a
lot
of
really
important
work,
so
this
is
a
new
bug.
It's
not
sending.
Oh!
This
is
not
about.
This
is
a
this
is
actually
a
teacher.
A
A
This
one
is
for
Ben
Tzion
team.
This
is
a
blocker
for
her
team
to
be
able
to
do
end
and
testing.
So
I.
Don't
really
understand
the
issue
too
much
I'm
going
to
be
completely
transparent,
but
I
understand
that
it's
not
a
big
issue,
it's
weighted
as
two,
and
so
this
would
be
a
great
quick
win
for
somebody
looking
for
a
small
piece
of
work
to
pick
up.
A
Okay
excuse
for
open
virtual
classrooms,
so
this
is
essentially
a
new
service
that
we're
gonna
start
selling.
So
Ragnar
heads
up
on
another
new
SKU
that
we're
going
to
have
to
make
sure
we
build
into
power
how
we're
displaying
so
that
it
doesn't
go
into
the
unknown
pile.
But
basically
the
work
for
this
is
to
take
the
SKU
that's
being
created
in
surah
and
make
it
available
in
in
customers
portal
the
way
that
it
should
be
available.
A
Data
this
one
is,
is
a
big
one
coming
up
in
the
next
milestone,
so
this
is
just
research
to
figure
out
how
to
do
it.
This
it
would
be
ideal
if
we
could
actually
get
it
in
this
milestone,
though,
so
this
is
for
the
quarterly
billing
in
self-managed.
Basically,
we're
gonna
start
billing
them
for
for
overages,
but
we
want
to
be
able
to
tell
them.
Oh
you
can
go
here.
Oh
I
know
I'm
sorry.
This
is
not
the
proof.
This
is
for
the
folks
who
are
air
gaps
that
we
cannot
bill.
A
Basically,
it's
going
to
take
all
the
data
that
we're
sending
to
us
and
see
Tinley,
and
it
should
serve
it
up
in
such
a
way
that
the
user
can
export
it
and
give
it
to
the
sales
person
to
be
able
to
fill
them,
but
it
shouldn't
be
editable.
The
should
not
be
able
to
change
any
of
the
data,
so
I
don't
know
if
it
needs
to
be
encrypted.
I
think
some
salespeople
gave
us
gave
us
some
feedback
in
the
original
in
the
engineering
issue.
That
I
don't
know
something
about
security.
A
It's
not
here,
oh
here
yeah.
So
take
a
look
at
his
concerns
there.
So,
basically,
this
is
a
research
issue
to
investigate,
what's
the
best
solution
for
this
and
then
create
small
issues
as
small
of
issues
as
possible
for
the
work
and
again,
the
work
is
currently
in
13:1,
okay,
so
I'm
not
going
to
go
through
the
rest
of
these.
You
guys,
sorry,
you
all
can
take
a
look
at
that.
Those
are
the
high
priority
ones
and
back
end
on
the
front
end.
We
have
some
companion
stuff
here,
the
the
banner
message.
A
This
is
work
so
that
the
automated
billing
doesn't
break
the
renewal
process
so
at
renewal.
We
should
not
allow
people
to
use
the
auto
renew
feature
if
they're
not
sending
us
seat,
link
data
we're
no
longer
doing
through
ups
for
anybody
sending
a
seat
link,
so
we
basically
have
to
trick
the
system
and
build
the
true
up
at
zero
with
the
proper
count,
so
that
the
the
license
doesn't
break.
The
reason
why
we're
not
changing
the
license.
A
A
That
way
this
is
someone
or
quarterly
stuff,
and
then
the
rest
of
this
is
pajamas
and
other
kind
of
random
I
think
we're
trying
to
do
some
cleanup
here
but
being
over
if
anybody
especially
Chris,
if
you
have
anything
in
this
in
this
list
that
you
would
say
hey,
this
is
a
little
priority
that
we
can
move
out
to
make
it
more
comfortable
for
the
team.
Let
me
know
you
axe,
I,
don't
think
I
have
anybody
on
the
call
that
I'll
do
a
quick
highlight
so
Emily's
tackling
the
UX
for
these
three
issues?
A
Each
of
these
issues
are
in
the
dev
work,
for
these
issues
are
in
the
future,
milestone
from
now
on,
I'm
gonna
try
and
do
that.
I'm
gonna
give
you
X
they're
design,
specs
a
milestone
before
so
that
when
engineering
gets
the
issue,
they've
got
the
design
and
they
don't
have
to
wait
for
it.
You
don't
have
to
wonder
you
know
when
is
it
going
to
deliver,
and
then
we
have
some
other
stuff
here.
That
I
think
we
have
to
see
if
it's
gonna
stay
in
or
not,
and
then
quality
yay
is
helping
out.
A
So
quality
is
going
to
help
with
mapping
of
the
kind
of
end-to-end
process
as
well
as
I
think
we
have
another
one
in
the
backend
that
they're
going
to
help
out
with,
depending
upon
when
it
comes
up,
I
think
it
is
oh,
it's
the
hooking,
the
staging
environment,
I
believe
cool.
So
depending
upon
when
that
one
comes
up
to
Engineering's
plate.
We
want
the
engineer
who
picks
the
hook
up
Salesforce
instance,
two
peeing
Vincey,
to
see
if
Chloe's
up
and
running
and
ready
to
start
looking
and
shadowing
on
some
work.
A
C
This
mapping-
one
probably
would
be
me
at
this
point
Jamie
for
Chloe
she
joined
last
week,
so
I
would
not
really
assuming
before
at
full
capacity
at
this
month
with
this
particular
milestone.
That
being
said,
yes,
please
paint
Chloe
when
developer
picks
up
the
initial
ticket,
so
then
they
can
play
program
and
she
won't
have
a
better
understanding
of
what
all
this
is.
That
would
be
easier
for
her
to
wrap
up
on
this
photo
and
so.
A
A
All
right,
so
that's
a
quick
summary
of
the
work.
That's
in
there
again,
I'm
gonna
have
I'm
gonna
go
in
and
look
for
work
to
take
out.
So
if
there's
anything
Chris
or
James
that
you
see
that's
like
technical
debt
or
stuff
that
I
pulled
in
to
try
and
clean
up
some
stuff
that
isn't
urgent.
Let
me
know
that
those
are
candidates
to
pull
out
I'm,
going
to
look
for
bigger
things
too.
But
okay,
thank
you,
but
sorry
am
I.
So
quick
sidenote
for
some
reason.
A
My
four
year
old
school
has
decided
it's
a
good
idea
to
do
daily
online
classes
that
he
has
to
attend
four
year
old
yeah,
so
I
put
the
eight-year-old
in
charge
of
it
he's
having
a
panic
attack
that
he
has
to
do
this.
Okay,
sorry,
so
yeah!
So
let
me
know
if
there's
anything
you
want
to
take
out.
I'm
gonna
keep
looking
at
this
today
to
see
what
I
can
take
out
and
if
I
don't
know.
If
there's
any
questions,
I
can
answer
while
we're
still
alive.
A
A
A
I
would
just
say
again,
I
think
that
we're
saying
this
a
lot
and
can't
be
said
enough,
take
time
for
yourself
if
you
feel
like
you
need
to
take
some
time
off
just
playing
with
your
manager
so
that
we
can
cover,
but
don't
feel,
like
I
saw
a
comment
that
somebody
couldn't
attend
the
social
call
last
week
because
they
felt
some
pressure.
Don't
let
that
happen?
If
you
feel
the
pressure
walk
away,
do
something
fun
I,
don't
know,
but
it
nobody
wants
that
for
anybody
so
put
some
time
off
in
the
calendar.
A
If
you
don't
have
any
schedule,
please
do
don't
forget
the
23rd
is
the
contribute
for
the
company.
So
if
you
can
contribute
to
that,
that's
awesome
and
May.
1St
is
a
company-wide
day
off
so
make
sure
you're
taking
that
time
for
yourselves
and
your
families
as
well.
All
right.
Thank
you.
Everybody,
sorry,
for
the
rush
to
call
have
a
great
rest
of
your
day.
Thanks.