►
From YouTube: Support Ops Sync - 2023-06-27
Description
Support Ops Sync - 2023-06-27
B
B
There's
a
handbook
link
there
in
our
talk
to
remind
you
of
what
that
looks
like
especially
the
standard
change
management,
which
is
the
one
that's
real
important
to
you.
But
the
shorthand
summary
is
our
Quest
issue
is
made
you're
going
to
analyze
it
determine
where
it
can
fit
if
it
could
fit
in
the
next
deployment
or
the
deployment
after
whatever,
and
you
will
apply
a
milestone
for
that.
B
If
it's
within
five
business
days
of
the
next
deployment,
that's
the
cutoff
date,
so
it
needs
to
go
into
the
following
deployment:
you'll
communicate
to
the
original
requester
when
the
deployment
is
going
to
be
given
the
specific
date.
Don't
you
say
it's
the
deployment
for
August
say
it's
August
1st
you'll
work
the
request
as
usual.
You
know.
Do
your
testing!
Do
your
review
make
your
Mr.
The
big
difference
comes
at
this
last
Point,
where,
when
the
Mr
is
ready,
everybody's
reviewed
it
go
ahead
and
just
merge
it
into
the
repo.
B
C
I
have
a
question:
what
happens
that
if,
for
example,
due
to
any
case,
the
the
Mr
doesn't
need
to
be
merged
and
it
got
merged
again,
is
there
any
way
to
revert
back
a
process
for
that,
for
example,
we
are
going
to
make
a
form,
but
certainly
in
the
next
deployment
we
decided.
That
form
should
not
be
there
it
should
it
wait
for
the
another
deployment
date
or
can
we
reverted
right
away.
B
B
Okay,
but
in
theory
with
us
communicating
and
all
that
there
should
not
be
those
kind
of
issues
if
there
is
I,
definitely
want
to
be
kept
aware,
because
I'm
going
to
want
to
do
a
postmortem
kind
of
like
hey.
Why
is
it
we
all
agreed
on
this
deployment,
but
when
it
actually
went
live?
Everybody
was
like.
A
B
It
off
seems
like
somewhere.
There
was
a
bad
communication,
so
definitely
something
I'd
want
to
review
sure.
If
you
look
at
the
handbook
link
It'll
point
out
the
exceptions
to
our
change
management,
things
like
macros
and
organotes,
where
it's
like
yeah.
No
we're
not
going
to
do
a
monthly
Cadence
on
Macros,
just
they
they
follow
the
same
process.
They've
always
followed
related
to
those
changes,
because
they're
they're
coming
I
am
making
a
ton
of
issue
and
Mr
default
files
and
doing
a
bunch
of
project
setting
updates.
B
No
actions
needed
on
y'all's
part
just
expect
that
when
you
start
making
issues
in
Mrs
they're
going
to
look
very
different
than
they
have
been
for
the
past.
However
long
they've
existed
in
the
current
format,
the
new
format
will
tell
remind
you
to
do
the
various
parts
of
the
process
remind
you
to
check
the
tags,
all
that
fun
stuff
they've
got
check
boxes
to
help
guide
you
through
the
process.
B
Agent
workspace
is
going
live
at
the
end
of
July
I.
Think
technically.
July
29th
is
what
I'm
going
to
turn
it
on,
but
that's
like
Friday,
so
I'm
gonna
wait
end
of
day
Friday
into
day
Friday,
but
in
no
day
Friday
man,
but
yeah.
So
just
make
sure
you
read
the
handbook
make
sure
you're
comfortable
play
around
the
sandbox,
because
I
expect
we're
going
to
see
questions
or
going
to
see
feedback.
We're
going
to
have
to
do
all
that
fun
stuff.
C
B
But
obviously
they're
both
on
PTO,
so
I
didn't
want
to
schedule
it
and
have
them
both
have
conflicts
and
then
I
come
back
going.
I
guess
I
now
have
to
do
an
AMA
at
three
in
the
morning,
so
I'm
waiting
for
them
to
come
back
to
finalize
that
before
we
actually
put
that
in
there
Lyle's
going
to
start
announcements
in
July
he'll
do
one
company-wide
mid-july
and
then
one
company-wide
a
week
of
well.
B
B
Cool
the
final
part
of
the
new
patriarchy
change
management
stuff.
The
final
step
for
us
is
coming
on
the
first
or
thereabouts.
The
first
is
kind
of
like
middle
of
the
week
or
start
of
the
week,
but
or
Saturday
I,
don't
remember
whichever
it
is.
I
don't
want
to
think
too
hard,
but
just
just
adds
up
there.
It's
coming
through
we've
got
some
questions
and
stuff,
but
mostly
it's
just
understanding
how
to
do
it.
So
it
looks
like
it's
working.
Okay.
B
If
everything
goes
off
without
a
hitch,
then
I'll
probably
update
docs
a
bit
to
illustrate
what
I
learned
and
then
we'll
start
slowly
getting
other
dris
to
handle
it,
and
all
that
fun
stuff
plan
is
every
single
person
in
Readiness
at
least
one
quarter
is
going
to
be
the
dri
for
what
it
means.
I
want
all
of
us
to
be
comfortable
with
the
process.
It's
a
lot
of
do
a
thing
and
then
wait
a
month
do
a
thing
and
then
wait
a
month.
So.
C
Yeah
I'm
actually
working
on
handbook
update
regarding
sandesk
Explorer.
This
is
for
a
really
long
time.
It
wasn't
a
backlog
and
this
needs
to
be
updated
as
soon
as
possible.
So
anything
that
you
want
to
add
please
consult
with
me.
I'll
keep
you
updated
with
the
current
updates
as
well
right
now,
it
has
been
done
with
a
you
know:
the
dashboards,
how
to
create
dashboards,
how
to
create
reports,
and
things
like
that
important
dashboards,
which
we
use
a
lot
in
support.
B
I'd
say
probably
it
is
a
priority,
but
don't
feel
like
take
your
time
on
that
one
because
there's
a
ton
of
metrics
and
ideally
we
want
like
a
step-by-step
guide
on
how
every
part
of
those
big
the
big
metrics,
like
especially
the
ones
we
use
in
the
key
review
and
the
group
conversation
are
made
because
you
know
the
affiliate
leaves
or
goes
on
extended
PTO.
We
should
have
a
better
answer
when
we
need
to
change
something,
then
we
need
to
wait
for
Ilia
to
come
back.
C
There
are
some
metrics
just
to
let
you
know
that
there
are
some
formulas
over
there,
which
normally
takes
three
to
four
days
to
write
as
well,
because
the
metrics
are
hella
detailed.
Not
everything
is
involved
in
zendes
Explorer
not
available
by
default,
and
we
have
to
write
a
lot
lots
of
custom
metrics,
keeping
in
mind
that
we
have
a
lot
of
just
different
teams
as
well,
and
every
report
in
every
formula
requires
their
own
version
and
taste
so
yeah.
It
will
take
some
time
yeah,
hopefully
yeah
yeah
yeah,
but
yeah.
A
B
B
C
B
B
B
C
C
B
C
C
B
Me
and
APAC
look
like
they're
staffed,
pretty
well
on
Fourth
of
July.
A
mayor
is
not
all
three
Reds
but
like
so
many
people
are
off
I.
Think
19
people
are
out
that
day
so
and
that's
just
as
of
right
now,
people
might
remember
that
they
need
to
put
on
the
PTO
and
yeah,
but
as
of
right
now
let
me
in
APAC
look
all
right
for
Fourth
of
July,
which
is
kind
of
what
you
want
with
federal
holidays.
You
know
you
want.
A
C
B
B
C
A
B
A
C
B
C
B
Yeah,
it
is
an
iteration
I,
don't
like
what
I
did
there
I'd
prefer
to
probably
use
rubudoc
or
something
like
that.
Sorry,
Ruby
doc,
oh,
combining
two
different
tools,
but
for
now
this
what
I
did
with
the
comments
will
work
until
I
figure
out
the
more
scalable
better
solution
for
our
scripts
and
like
stuff
like
that.
Ultimately,
it'll
probably
result
in
US
building
a
gym
for
us
to
use
and
then
it'll
dramatically
simplify
code
when
most
of
what
we
do
is
require
the
gym
and
run
commands.