►
From YouTube: Testing UX / PM Sync 2021-10-07
Description
Gina and James talk priorities, the new iteration plan for the Project Quality Summary, progress on the MR Widget WG, how we delete job logs and how that compares to job artifacts, and why the dogs in James' neighborhood always bark during this call.
A
This
is
the
ux
pm
and
all
the
dogs
in
my
neighborhood
parking
meeting
for
october
7th
2021
follow
us
from
last
week.
I
just
wanted
to
follow
up
on
next
steps
for
the
job
to
be
done
stuff
that
we
talked
about.
I
updated
the
deck,
but
I
didn't
create
to
do's
in
the
ux
research
project.
Yet
I
can
do
that.
A
I
think
I
actually
have
a
job
to
be
done,
like
validation
issues
already
created
for
all
of
the
categories,
so
I
can
assign
those
to
you
put
them
in
the
proper
quarter
for
when
they'll
need
to
be
completed,
based
on
the
schedule
that
we
had
laid
out
and
then
as
part
of
transition
walk
through
those
with
new
pm
coming
on
board.
So
that
sound
like
a
reasonable
step
forward.
A
B
B
A
B
Yeah
sure
I'll
share
my
beautiful
readme
file,
so
my
highest
priority
is
reviewing
the
mr
widgets,
which
the
performance
load
widget
actually
got
merged,
and
that
was
that
was
a
pretty
tough
reviewing
process.
I
would
say
so
what
we
ended
up
doing
was.
I
met
with
scott
and
peyton
around
that,
and
there
was
a
lot
of
like
initial
review
that
was
going
on
that
didn't
really
require
getting
it
up
on
my
environment.
So
I
did
that
and
then
what
we
decided
was.
B
So
there
was
a
lot
of
styling
changes
that
I
commented
on
here
that
are
going
to
be
done
in
follow-up,
but
we
do
have
this
merge
so
now
you
can
see
it
in
it's
behind
a
feature
flag,
but
you
can
see
it
in
this
prod.
Where
is
it
this
one?
Sorry?
I
was
already
looking
at
it,
but
you
can
see
it
actually
compared
to
the
old
one
here
in
this
specific
project,
which
is
pretty
cool
so
now.
B
My
next
steps
here
is
to
do
a
more
in-depth
review
and
just
make
sure
that
anything
that
hasn't
been
vetted
out.
Yet
I'm
I'm
capturing
it
in
this
single
issue
and
then
I'll
reopen
this.
But
I'm
doing
this
mostly
for
myself
to
make
sure
that
we
get
these
changed
somewhere
and
then
I
can
update
the
status
saying
which
issue
this
is
going
to
be
made
in
and
blah
blah
blah.
It's
it's
nothing
functionality
that
needs
to
be
changed.
It's
just
stuff
yep,
exactly.
A
B
Yes,
it
should
yeah
that
should
happen,
because
browser
performance-
and
this
one
are
so
similar
that
should
work.
There
are
specific
things
for
some
of
the
like.
Some
of
these
might
be
able
to
just
be
made
in
the
core
component
and
then
universally
be
applied
as
well
to
not
just
our
testing
widgets
but
other
widgets
as
well
yeah.
So
we're
just
that's
what
I
was
working
on
this
morning,
just
making
sure
that
it's
okay
responsibly.
So
that's
my
highest
priority,
long
story.
A
Short,
I
would
encourage
you
if
you,
if
there's
already
an
issue
open
around
feedback
for
the
working
group,
dump
your
thoughts
into
that
about
the
review
process
here
with
between
development
and
ux,
and
just
overall,
like
as
we
have
working
groups
that
make
changes
your
feedback.
There
would
be
appreciated,
I'm
sure,
by
the
working
group
and
if
there
isn't
one
create
one
and
just
apply
the
working
group
label
to
it.
B
A
B
A
A
A
So
we
have
a
process
and
product
where
we
create
feedback
issues.
When
you
launch
an
mvc
in
the
release
post,
you
put
it
or
you.
You
list
the
issue
that
that's
where
we're
expecting
feedback,
but
that
doesn't
generate
a
lot,
so
eric
shooter
actually
posted
yesterday
about
all
the
feedback
he's
been
getting
from
his
feedback
issue
around
the
wiki
editor,
and
I
commented
I
was
like
this
is
awesome.
A
I've
never
gotten
feedback
on
these
feedback
issues
or
it's
been
very
minimal,
like
it's
been
internal
feedback
only
because
we
have
gone
out
and
requested
it,
and
he
had
like
20
comments
from
customers
and
said:
how
did
you
get
this?
He
said?
Oh,
we
put
it
on
the
page
itself
like
when
you
use
that
feature.
You
get
a
banner
that
shows
you
that
you
can
leave
feedback
about
that
feature.
A
So
I
want
to
do
that
on
that
specific
page
of
if
you're
using
this,
tell
us
about
how
it's
going,
which
will
give
you
with
a
banner
notification
like
a
site
notification
for
a
couple
of
weeks
after
launch
or
a
couple
of
months
after
launch,
even
potentially,
and
then
that
will
just
link
directly
to
the
issue.
And
you
can
leave
your
comments.
There.
A
B
A
B
B
B
Yeah
yeah
there
we
go
okay,
so
I
was
wondering
if
this
would
be
like.
I
was
wondering
your
perspective.
If
this
would
be
something
that
would
be
good
to
take
on
for
14.5
as
a
stretch
I
read
through
it
and
it
seems
like
I
mean
it
definitely
needs
ux
and
it
seems
like
it
would
be
somewhat
quick
to
do.
B
Of
this
issue,
so
I
think
it
seems
like
it's
more
of
like
a
settings
option
that
you
would
be
able
to
add
optionally,
like
I
don't
know,
click
to
automatically
expire,
build
logs
and
maybe
even
add
an
option
to
set
it
to
expire
after
a
certain
amount
of
time,
and
I
think
that
those
types
of
settings
are
already
used
throughout
gitlab.
So
I
feel
like
it
could
be
a
reusable
pattern.
A
B
A
Seems
similar
to
the
keep
artifact
from
the
latest
successful
pipeline
feature
that
we
have,
and
we
might
just
extend
that
feature
to
the
job
logs
as
well.
If
it
isn't
already
that's,
I
think
the
pattern
that
I
would
that's
the
pattern
I
would
replicate
because
it's
the
pattern
we
already
have
and
I
would
treat
the
job
logs
the
same
way
we
treat
the
job
artifacts.
A
This
is
we're
still.
This
is
an
interesting
feature
that
has
caused
some
consternation
because
of
our
abilities
or
inabilities
to
get
those
things
deleted
quickly
after
they
are
not
the
latest,
and
if
you
have
a
failed
pipeline,
it
keeps
those
we
are
cleaning
that
up.
I'm
surprised
that
job,
artifacts
or
job
logs
aren't
just
treated
the
same
as
job
artifacts.
To
be
honest
in
the
code
where
you
don't
have
the
logs
anymore
after
expiration,
yeah,
so
they're
not.
B
A
B
A
A
B
B
A
A
A
If
we
can
follow
an
existing
pattern
and
treat
these
things
the
same
way,
we
do
artifacts.
I
think
that's
probably
the
best
way
to
go,
but
understanding
if
users
are
having
issues
with
job
logs
and
persisting
job
logs
and
not
being
able
to
it
looks
like
they're
a
lot
easier
to
delete
than
artifacts
are
because
the
artifacts
api
is
woefully
inadequate.
You
have
to
do
it
a
job
at
a
time
you
can't
bulk
delete,
which
is
what
we're
working
on
next
and
that's
going
to
solve
that
giant.
Hammer
of
just
dump.
B
A
B
B
A
A
A
I
need
to
get
the
insights
created
from
last
week's
interviews.
I'm
going
to
do
that
this
afternoon,
and
I
don't
have.
I
didn't,
have
any
interviews
this
week.
I
have
some
next
week.
I
need
to
try
to
pull
those
other
ones
forward
still
just
so
I
can
get
it
wrapped
up
and
then
I'm
still
working
on
content
and
refining
the
content
for
that
sales
enablement
session
coming
up
later
this
month,.
B
A
A
The
only
other
thing
for
me
or
the
other
thing
in
there
is
scott,
is
starting
on
his
stuff
and
we
had
some
interesting
feedback
in
an
issue
yesterday
from
engineering
productivity.
Looking
at
how
do
we
measure
job,
durations
and
tracking
those
over
time
which
fits
into
scott's
research
issue
very
nicely.
So
I
tagged
him
on
that
and
I'm
hoping
he
gets
to
get
some
interviews
going
next
week
crossing
my
fingers
for
him
to
get
going
on
those
soon
and
otherwise.
I
wanted
to
just
follow
up
on
the
ux
labeled
issues.
A
I'm
just
reviewing
old
nbc's,
making
sure
that
there's
not
ux
debt
that
we
haven't
cleaned
up
and
if
there
is
to
create
the
issues
for
it
and
label
it
appropriately
and
then
just
look
at
the
existing
backlog
of
ux
issues
that
are
for
testing
and
see
what
is
what,
in
there
is
ux
debt,
because
we've
not
had
good
label
hygiene
when
it
comes
to
that,
and
I
think
that
that'll
wrap
up
that.
Mr
around
saying
30
of
our
time
is
a
split
between
tech,
debt
and
ux
debt.
A
A
Okay,
anything
else.
I
can
help
with
anything
else
you
want
to
chat
through.
I
believe
I
have
a
schedule
to
record
our
14-5
kickoff
next
week.
Yep
next
week
is
going
to
be
a
short
one
between
holiday
on
monday
and
friends
and
family
on
friday,
and
I'm
I'm
moving
my
friends
and
family
forward.
I'm
going
to
take
it
tomorrow
and
then
work
next
friday,
just
to
make
sure
I'm
all
caught
up
on
all
the
things
before
the
end
of
october.
B
A
I
have
14
6
and
14
7
planning
issues
already
created
and
I
have
scripts
already
written
and
I
have
gina
content
here
that
just
has
a
tag.
So
if
you
want
to
start
looking
at
those
milestones,
I
asked
scott
to
review
for
the
big
themes
and
the
the
big
issues
there,
but
I'll
tag
you
in
those
as
well.
If
you're
not
already
or
link
those
over
to
you,
so
you
can
take
a
look.