►
From YouTube: CI/CD UX Team Meeting: November 16, 2022
Description
The CI/CD UX team shares work that is happening in each group and what is coming up that may include cross-group collaboration.
A
C
B
I
think
my
first
item:
it's
about
severity
labels,
if
I'm
not
mistaken,
so
just
a
heads
up
for
product
designers,
please
don't
forget
to
add
severity
labels
to
your
ux
issues,
especially
the
sus
impacting
ones
the
boat
will
annoy
you.
If
you
don't
so
it's
a
good
way
of
reminding
us
to
label
those
issues
accordingly,
so
we
can
have
help
with
prioritization
but
also
I've
seen
some
issues
you
might
see.
Valerie
also
doing
some
housekeeping
on
those
on
those
issues
and
leaving
comments.
B
But
there
are
some
issues:
there
are
not
labeled
ux,
but
they
do
have
ux
requirements.
So
I
review
one
for
verify.
Today
there
was
a
backend
issue,
but
it
changed
settings
and
it
changed
UI
copy,
but
it
didn't
have
ux
or
a
severity
added.
So
just
a
reminder
for
everyone
to
please
make
sure
that
the
issues
that
you
and
your
team
are
working
on
have
the
correct
labels
applied.
So
that's
one
and
then
my
other
updates
about
hiring.
You
have
a
new
product
designer
joining
the
pipeline
insights
team.
B
A
A
D
Well,
that's
a
great
tie-in,
because
working
backward
from
my
list,
one
of
the
things
was
that
we
have
I
wanted
to
like
celebrate
the
my
my
updates
today
are
framed
around
welcome
back,
hey
Anna,
yay
you're.
Welcome
I,
wanted
you
to
know
that
Gina
and
will
actually
got
sick
and
like
tested
such
that
I
couldn't
go
to
the
conference,
and
so
Gina
like
stepped
into
this
leadership.
Position
will
really
delivered
and
we
have
like
four
reports.
D
D
And
then
I
guess.
My
last
item
too,
is
just
asking
if,
if
you
all
would
like
to
open
up
the
H2
verifying
package
comment
screener
for
solution,
validation
studies
just
wanted
to
check
if
it's
worth
like
making
that
change
with
Caitlyn
and
I
linked
a
PDF
of
the
of
what
the
questions
are
and
as
long,
but
we
have
like
500
participants
in
there
and
some
of
them
have
been
used,
but
I
think
I'll.
Give
you
time.
D
But
before
then,
I'm
just
doing
work
to
like
kind
of
crosswalk
the
stages
that
have
done
this
before
to
kind
of
like
make
sure
what
we
do
is
on
par
and
then
we
also
kind
of
related
to
package
resources.
We
put
on
hold
this
life
cycle
of
an
image
study
until
the
new
PM
joins,
so
that
would
be
the
study
that
we
did
kind
of
with
secrets
and
CI
templates
where
it's
like.
How
does
it
start?
What
happens
next?
What
happens?
Next?
D
D
One
more
thing
to
mention
about
that
is:
Gina
has
a
really
cool
issue,
a
research
issue
around
looking
at
the
life
cycle
of
logs,
and
so
part
of
me
wants
to
try
to
fold
that
into
this
study.
That's
now
on
hold,
but
I
think
we're
getting
feedback
that
we
need
to
like
scope,
that
Gino
study
down
a
little
bit
so,
but
does
note
that
I
have
like
a
plan
because
I
think
it's
really
smart,
like
in
foundational
research
terms.
B
D
D
What's
our
screener
look
like
I
actually
have
our
screener
drafted,
and
so
whenever
Tim
has
time,
he
can
kind
of
come
in
I
think
the
idea
would
be.
We
would
treat
it
like
a
common
screener
and
then
be
in
a
position
to
run
the
next
Benchmark
like
we
would
have
500
participants
that
we
could
select
from
if
we
kind
of
start
rolling
it
out
as
soon
as
we're
ready
and
so
we're
just
waiting
on
Tim
to
have
time
yeah.
So
it's
like
what
were
the
screeners?
D
How
are
the
samples
comparing
and
that
will
help
us
know
like
I,
think
what
I'm
seeing
so
far
is
like
we're,
mainly
small
medium
business
samples,
which
is
fine
to
know
right,
but
it
means
we
don't
have
to
then
stretch
to
do
an
Enterprise,
recruit
kind
of
we
want
to
be
on
par
and
then
I'll
be
looking
at
all
of
the
mechanisms
that
different
researchers
use
to
like
get
feedback.
Like
will.
D
Has
this
lovely
mural
approach
that
he
used
for
jobs
to
be
done
like
deciding
on
the
tasks
and
then
working
with
Tim
to
figure
out
like
what
the
team
has
capacity
for
I
feel
like
we're,
we'll
go
more
Bare
Bones,
which
is
also
okay,
but
so
in
a
couple
weeks,
when
we
get
back
from
the
Thanksgiving
holiday
I'm
gonna
meet
with
Tim.
To
like
give
the
updates
and
then
see
what
his
thoughts
are
related
to
the
kind
of
the
next
steps
and
I.
B
Okay,
I'm
taking
some
notes
here.
Thank
you.
Take
care
for
the
overview.
That's
that
clarifies
my
next
couple
of
questions
and
then
I
just
want
to
say.
Please
keep
me
in
the
loop,
because
if
we
know
a
bit
ahead
of
what
the
the
ux
I'll
say,
like
Hands-On
design
work
for
package
is
going
to
look
like
I
need
to
know
to
prepare
the
ux
coverage
because
we
won't
have
ux
allocation
for
package
until
next
year,
Q3
Q4,
right
yeah.
B
We've
made
a
decision
too,
because
team
and
Victor
and
also
Michelle
they
talk
about
the
deliverable
plans
for
package
now
and
that's
for
everybody
to
kind
of
be
aware
that
well
they're
hiring
developers
right,
so
they
don't
have,
for
example,
front-end
allocation
to
build
UI
right
now.
So
we
are
not
going
to
be
hiring
a
designer
for
package
right
now
we
move
the
head
counter
to
a
different
team,
and
then
we
won't
have
a
designer
for
package
until
next
year
right
once
development
picks
up.
B
But
if
there
is
a
the
research
is
going
on
and
we
have
well,
the
Harry
for
development
also
picks
up,
and
we
know
that
we
have
a
need
for
package
ux
deliverables.
Then
yeah
I'll
need
to
know
ahead
of
time
so
that
we
don't
work
on
the
coverage
or
borrow
plan
or
a
hurry
plan
for
the
for
the
design
backfill
for
Katie's
backfield.
B
D
D
C
C
C
E
Well,
I'll
go
a
little
out
of
order
because
I'll
get
to
my
critique
one
at
the
end,
but
I
was
mostly
curious.
Now
that
I'm
kind
of
getting
to
the
stage
of
conducting
the
CMS
interviews
with
internal
users
just
kind
of
some
of
the
things
you
did
to
recruit
people
I
know
we're
using
some
people
from
the
delivery
team
who've
already
offered
to
volunteer,
but
just
any
other
options
to
get
people
into
the
study.
I'm.
Looking
for
so
looks
like
will
and
Gina
both
had
comments
around
that.
C
Sometimes
I've,
like
leaned,
on
the
PM,
to
try
to
help
direct
me
to
like
the
right
channels
to
go
to,
but
since
you're
working
a
lot
with
the
delivery
team,
they
might
you
know,
help
you
know
where
to
post
or
you
could
just
talk
to
the
participants
that
you
have
signed
up
and
say,
like
hey,
you
know
now
that
you've
gone
through
this
study.
You
know:
is
there
someone
else
on
your
team?
That
might
be
good
for
this.
A
A
B
Handbook
right
we
have
a
section
with
the
internal
customers
for
each
stage
group
and
then
on
which
page
is
that
on
the
handbook
product,
slash
categories
and
if
our
release
stage,
we
know
it's
a
delivery,
distribution,
team
security.
So
just
echoing
what
the
will
and
Gina
said
most
of
those
groups,
they
have
on
their
own
slack
channel.
So
you
can
drop
that
same
message
in
there
and
then
we
either
Reach
Out
directly
to
people
I.
Think
for
the
release.
The
delivery
team
they're
super
active.
B
E
Cool
the
second
update
I
wanted
to
give
is
we
adjusted
the
deployments
navigation
so
now,
when
you
click
on
the
high
level
deployments,
you
land
on
the
environments
page
not
feature
Flags,
because
there's
a
lot
of
data
showing
that
people
would
land
on
feature
flags
and
navigate
away
as
well.
There
was
comments
about
this
in
our
like
benchmarking
study,
so
that
is
now
in
production,
which
is
really
great
and
then
will
I
notice.
You
had
a
comment
on
that
as
well.
C
Yeah,
as
you
talked
about,
we
did
see
this
a
lot
in
the
benchmarking
study
and
I
would
just
constantly
see
participants
like
click
on
the
link
and
know
that
they
weren't
going
to
go
to
the
right
place,
and
then
they
would
just
like
get
frustrated
and
then
have
to.
You
know,
use
that
extra
click
to
go
to
the
right
page,
so
I
know
that's
going
to
be
a
big
time.
Change.
E
E
If
I
can
figure
out
what
screen
I
have
to
share
this
on
well,
so
how
I
started
this
is
I
really
took
a
step
back
and
went
through.
The
research
and
kind
of
this
page
is
interesting
because
it's
not
a
typical
flow
users,
wouldn't
be
going
here
to
complete
like
a
typical
flow,
but
I
did
want
to
get
onto
paper
kind
of
like
some
of
the
tasks
that
the
research
showed
that
they
were
looking
for.
E
E
Are
you
having
problems
with
any
of
them,
so
a
little
TBD
on
what
to
show
in
this
area,
but
really
having
that
high
level
summary
and
then
being
able
to
dig
down
if
you
need
and
then,
when
you
go
into
the
environment,
showing
an
environment
level
summary
of
that
production,
environment
with
like
environment,
Health,
Project,
the
deployment,
the
most
recent
deployment
health
and
then
some
actions
you
can
take
as
well
as
showing
that
most
recent
deployment.
So
you
have
like
context
of
what
is
going
into
that
environment.
E
Currently,
I've
cut
it
down
quite
a
bit
from
some
of
the
original
proposals,
because
this
page
we
really
want
to
show
them
what
is
going
on
and
not
bog
them
down
by
a
bunch
of
different
information
that
they
could
kind
of
dig
into
and
find
so
I've
kind
of
moved
it
into
this
again.
As
you
can
see,
this
is
like
a
really
big
TBD.
I
want
to
create
a
nice
summary
at
the
top,
but
kind
of
showing
this
into
like
group
name
environment
at
the
production.
E
Tier
kind
of
like
is
the
most
recent
deployment
successful.
Is
there
anything
action
you
have
to
take
and
then
kind
of
showing
details
about
the
most
recent
deployment
underneath
it
with
options
to
like
view
in
project
and
kind
of
debug
problems
going
that
way,
but
by
condensing
this
information
down
reducing
the
amount
of
like
pigeonation,
you
need
so
being
able
to
show
things
all
on
one
page
and
being
able
to
show
just
the
information.
E
You
need
to
kind
of
take
the
action
that
you
need
to
take
so
open
to
suggestions
on
this,
but
that's
kind
of
like
how
I've
started
this.
It's
still
fairly
rough,
so
there's
like
I
do
want
to
run
this
by
some
users
as
well,
but
thought
I
would
get
a
first
feedback
look,
even
though
this
is
kind
of
like
a
rough
low,
Fidelity
right
now,.
A
I
had
one
comment
just
saying
that
I
thought
it
looked
great
I
didn't
even
see
this,
the
one
that
you're
showing
right
now
I
only
saw
the
Ia
stuff,
so
I
think
it
I
think
it
looks
like
with
the
all
the
information
that
you
have
to
deal
with,
which
there
is
a
lot
like.
You
did
a
really
good
job
of
summarizing
that
and
making
it
clear,
I.
Also
the
thing
that
came
to
mind
for
the
summary
view
up
top
I
think
that
this
single
stat
component
is
always
good
for
that
type
of
stuff.
A
A
I'll
link
it
to
you
from
pajamas
awesome,
it's
pretty
flexible
too,
which
is
great
then
my.
My
only
other
comment
was
for
like
this
would
be
adding
a
new
navigation
item
for
for
groups,
and
we
had
to
do
a
similar
thing
for
a
runner,
so
I
would
consider
talking
to
the
foundations
team
just
to
make
sure
like
I,
think
you
have
to
get
approval
from
them
now.
I
can
link
the
handbook
page,
but
I
also
know
because
they
have
all
their
navigation
efforts
going
on.
E
A
D
So
I
think
you
could
add
Clarity
here.
If
there's
like
a
light
touch
way
to
even
like
allow
people
to
dig
into
the
different
variables
that
are
being
used
in
different
environments
and
what
they
do.
I
think
that
would
help
them,
and
it
feels
like,
if
we're
going
to
do
an
overview
like
that.
That
would
be
something
to
highlight
or
think.
C
E
C
Think
for
the
summary
view,
some
of
the
things
that
could
be
helpful
is
just
being
able
to
identify
not
just
like
how
many
environments
are
in
a
successful
status,
but
also,
if
there's
ones
that
are
like
pending
or
if
there
are
ones
that
are
like
failing
or
having
some
sort
of
like
difficulties.
Just
so
that
people
can
like
easily,
like
click
into
those
and
and
be
taken
to
those
somehow
and
then
also
I
like
how,
in
your
design,
you're
not
like
using
the
carrot,
slash
accordion
style
menu
that
that
we
currently
have.
C
E
Person,
yeah
yeah,
it's
kind
of
I
know
a
lot
of
our
research
has
shown
those
collapsible
sections
when
you're
trying
to
find
a
high
level
view
of
everything
was
just
not
working
out
right.
So
I
was
trying
my
best
not
to
even
collapse
any
information
and
just
if
there's
information
you
that
needs
to
be
hidden,
maybe
that's
not
the
right
place
to
put
it
on
this
page,
so
appreciate
that
you're
welcome
cool
and
hayana
I.
Think
you
have
the
last
comments.
B
Anyone
really
that
is
interested
in
how
the
application
is
doing
at
the
higher
level,
so
I
think
that's
that's
going
to
be
a
great
addition
and
I
have
a
couple
of
follow-up
questions.
Emily
I'm,
not
sure
if
you
have
the
time,
but
anyway,
I
think
those
are
just
the
things
I
was
thinking
of,
while
looking
at
the
prototypes.
B
Has
the
team
considered
if
this
would
be
something
that
will
be
just
pre-populated?
You
know
coming
from
all
the
projects
that
had
they
have
environments
that
meet
a
specific
criteria
or
will
users
be
able
to,
let's
say,
manage
and
customize
that
view
based
on
what's
important
for
them
to
see
you
know
for
each
project,
yeah.
E
E
B
Thanks
that
answers,
my
question
and
I
think
following
up
to
that
and
thinking
out
loud
too,
is
that
you
know
when
you
have
the
chance
look
at
how
the
MVC
plus
would
look
like
because,
for
example,
if
I'm
not
mistaken,
you
can
have
multiple
environments
under
the
same
tier
right.
So
if
you
set
it
up
in
the
CI
file,
you
can
have
I,
don't
know
different
production
environments,
label
production
but
put
a
different
name
right.
So
how
would
that
look
like
in
the
UI?
B
How
would
users
customize
so
I
think
would
be
a
good
next
step
for
you
there
to
see
how
this
page
would
grow,
because
one
of
the
challenges
that
we
had
with
the
current
environments
page
is
that
while
designing
and
also
coding
it,
we
were
not
thinking
of
how
that
paid
would
scale.
So
I
think
you
have
the
the
ability
here
to
predict
some
of
the
Educators,
but
also
to
avoid
you
know
the
unhappy
unhappy
bats
in
the
in
the
ey
in
the
overall
ux.
E
Yeah
for
sure
yeah,
that's
something
and
where
I'm
early
enough
into
the
designs
here
now
that
I
have
to
kind
of
build
out
what
does
like
unhealthy
environments?
Look
like
what
happens
when
you
have
like
a
lot
on
this
page,
so
I
think
we
still
have
quite
a
bit
of
time
to
kind
of
build
out
all
these
educations
and
then
once.
E
B
B
E
B
Awesome
yeah
I
think
that
that
would
be.
You
know
a
good
I'm
gonna
put
that
justification
right
for
Deborah
Katie
or
moving
away
from
that
environment.
Dashboard
View,
there's
no
traffic
there.
As
far
as
I
know,
and
to
your
point
there
are
so
many
restrictions
in
terms
of
the
also
for
that
performance
of
that
page,
that
you
know
I
would
say
if
you
can,
and
also
when
you
have
the
decisions
or
conversation
with
the
team
put
in
the
proposal
too.
D
E
B
E
B
Awesome
and
then
my
last
feedback
just
about
it's
just
about
DUI
and
then,
if
I
yeah.
Let
me
zoom
in
here
yeah
when
I
did
the
validation
for
the
environments.
Page
right,
I
learned
that
the
information
about
the
commit
message
it's
irrelevant
to
users,
or
it's
usually
relevant
when
that
commit,
is
merging
or
Branch
or
anything
into
Master,
because
it
often
shows
that
same.
You
know
default
message,
merge
branch
and
then
Branch
name
and
that's
not
really
readable
and
that's
not
a
very
informative
to
users.
E
Yeah
I
I,
agree,
I,
think,
there's
stuff.
We
can
especially
that
if
we
can
save
real
estate
on
anything
in
this
page
and
take
out
things
that
they
don't
need
at
this
Viewpoint
something
I'm
working
towards
right
now.
So
that's
great
to
know,
that's
something
we
can
potentially
take
out
of
this
awesome.
Well,
thanks.
Everyone
for
your
feedback,
I
want
to
give
Gina
enough
time
for
her
points
as
well,
but
I
appreciate
kind
of
taking
the
time
to.
Let
me
walk
through
that.
So.
A
Thanks
Emily
I
have
one
other
question
for
you:
I
noticed
that
the
the
way
that
you
were
like
for
each
row
there
was
kind
of
like
many
columns
of
metadata
in
there
like
the
job.
Like
all
that
stuff.
Have
you
heard
gotten
any
feedback
around
how
that
impacts
like
scannability,
I,
guess
across
different
deployments,.
E
Just
so,
we
can
reuse
some
components
so
yeah
I
agree.
Those
sections
I
think
need
a
bit
of
cleaning
up
and
figuring
out
what
exact
information
should
be
placed
there
like
the
merge,
Branch
message
taking
that
away,
but
yeah
I,
agree,
I,
think
there's
some
simplification.
We
can
still
do
in
that
area.
A
Yeah
I'd
be
like,
if
you
end
up
testing
this
I
would
be
interested
in
seeing
if
people
say
like
if
they,
if
they
want
to
scan
I
guess
by
column,
like
does
formatting
the
information
in
that
way
impacts
that,
because
I
mean
we're
doing
that
in
runner,
and
there
have
been
like
two
literally
to
customers
who
have
been
like
I.
Don't
I
don't
want
to
see
it
in
this
list
view
I'd
rather
see
it
in
a
table,
but
the
majority
have
been
saying
it's
fine
to
see
it
in
the
way
that
it
is.
A
E
D
And
then
I
I
have
one
more
point
there
I'm
like
jumping
in
before
we
switch,
but
it
would
be
that
when
you
do
the
solution,
validation
I
think
try
to
include
like
more
personas
than
you
might
not
like
try
to
push
yourself
to
include
more
personas.
So
we
make
this
work
for
more
people,
because
I
think
it
can
have
a
bigger
impact.
E
A
Thanks
I
I
have
two
updates.
One
of
them
is
for
pipeline
insights.
We're
dealing
with
this
problem
of
flaky
tests
forget
if
I
gave
a
definition
of
these
or
not,
but
the
general
one
is
that
when
you
run
tests
they
can
sometimes
fail,
but
the
failure
isn't
real
like
it
wasn't
actually
detected.
It
was
because,
like
the
test
is
actually
written
incorrectly
or
maybe
a
test
that
that
test
relies
on
failed
something
like
that
and
if
it
fails
more
often
than
it
succeeds,
without
actually
detecting
a
failure.
A
It's
considered
flaky,
so
we're
trying
to
understand
from
users
like
their
pain
points
right
now,
their
workarounds
with
how
they're
dealing
with
flaky
tests
and
then
definitely
how
they
Define
them.
The
the
key
insight
for
us
here
is
how
they
Define
them,
because
we
want
to
be
able
to
when
we
Define
them
for
this
MVC.
We
want
to
make
sure
it
matches
their
expectations.
A
A
Well,
it's
a
small
feature,
but
it's
it's
an
important
feature
that
we've
added
for
runners,
it
kind
of
has
to
do
with
the
whole
Runner
Fleet
monitoring,
slash,
Q
stuff
I've
been
talking
about
for
a
while.
So
it's
it's
difficult
for
users
to
be
able
to
see
if
a
runner
is
running
a
job
at
the
moment
and
the
reason
why
that's
important
is
because
if
they
were
to
update
the
runner,
for
example,
it
would
stop
that
runner
from
running
any
jobs.
E
I
just
want
to
say,
I
love
the
idea
of
combining
status
badges
into
one
thing
that
works
because
I've
seen
it
quite
a
few
times
and
I
think
it's
in
like
the
environments
area
as
well,
where
there's
like
multiple
status,
Badges
and
you're,
not
quite
sure
how
they
relate
to
each
other.
So
I
think
that's
a
great
idea.