►
Description
Going over Verify and Release UX work for the upcoming milestone to align on possible overlaps and dependencies between Product Designers.
A
For
that,
in
the
meeting
invite
you
can
see
the
link
to
the
UX
board
that
actually
I
have
transplanted
to
verify
and
release
UX
on
board.
Sorry
for
repetition
and
I.
Think
I
was
previously
the
one
that
you
mentioned.
You
created
for
the
CIC
18
one
time
ago
and
I
think
we
chatted
that
that
wasn't
really
used
so
I
yeah
date.
A
few
things
just
change
the
participants
to
be
to
the
current
team
members
and
change
the
titles.
A
So
the
only
thing
it
does
it
right
now
filters
for
the
UX
labelled
issue
and
for
our
participant
that
are
currently
in
them
fortify
and
release
UX
team.
It
does
not
filter
on
the
milestone
so,
but
we
could
add
that
filters
if
we
want
so
I
think
the
goal
that
we've
been
discussing
earlier
would
be
just
to
use
this
sport
and
I
actually
want
to
focus.
Multiple
things
would
be
nice
to
see
how
accurate
the
data
is
on
the
board.
A
I
would
be
curious
to
give
each
of
us
a
time
right
now
to
kinda
like
go
for
the
column
and
see.
Are
we
missing
anything?
Do
we
see
anything
weird
because
again,
I
need
you
to
kind
of
like
help
me
validate.
That
and
second
of
all
here
maybe
provide
a
quick
walkthrough
by
every
stage
group
and
see
what
exciting
is
happening
in
the
stage
groups
and
maybe
water
possible
dependencies
or
collaboration
that
we
will
need
between
ourselves.
B
The
only
thing
that
summer,
like
while
I
was
wondering
about
is
so
the
intention
is
to
go
over
work,
we're
actively
working
on
right
now,
so
we're
like.
Are
we
intend
to
filter
on
not
my
milestone
on
purpose?
So
are
we
filtering
on
the
workflow
labels,
or
are
we
gonna
filter
on
something
else
like
I'm,
just
I,
just
filtered
for
myself
here,
I'm
thinking
about
like
hey,
you
know
some
things
around
her
and
myself
through
some
issues
which
I
thought
I
already
did,
but
perhaps
I'm
like
I
think
I'm
tracking
them
differently.
B
A
C
C
Know
it's
quite
tricky,
I
think
make
sense
for
the
things
I,
like
the
things
that
we
are
working
on
right
now
for
us
and
the
upcoming
ones.
But
it's
to
me
at
least
it's
becoming
more
and
more.
The
muscles
are
becoming
more
and
more
fluid
I'm
working
on
these
around
the
backlog
that
I'm
not
prioritizing
against
the
development
deadline,
but
I'm
just
working
on
things
that
belong
to
a
broader
epoch
where
I
brought
her
a
team,
so
kind
of
doesn't
answer
a
question.
But
it's
also
this
this.
C
A
Yeah,
maybe
we
could
give
that
a
try
and
then
see
you
know
that,
basically,
where
we
end
up,
let's,
let's
take
this
session
as
a
as
a
pilot
as
that
testing
session
and
let's
see
yeah
how
much
value
it
will
bring
and
how
we
will
need
to
change
it
or
adapt,
or
you
know,
like
kind
of
like
transform
the
conversation.
So
now
you
could
just
like
see
I
basically,
I
will,
let's,
let's
keep
a
stage
to
everyone
of
us
and,
let's
see
kind
of
like
how
relevant
to
each
stage
group.
A
The
issues
that
are
there
in
the
board
will
be
because
I
know
when
I
understand
that
we
all
work
in
a
different
way.
Somebody
uses
masks
on
somebody
is
more
like
combat
style
and
yeah.
Well,
just
give
it
a
go
and
see
where
we
end
up
yeah,
so
yeah,
hey,
Anna
I'll,
just
give
it
over
to
you,
because
at
least
I
see
your
name
first
on
the
board.
Would
you
like
just
to
kind
of
like
Winston,
give.
C
So
it's
a
mess
when
I
look
at
it.
I'm
like
I,
don't
even
understand
what
are
the
things
that
are
assigned
to
me
because
I
don't
look
at
those
issues
like
this,
so
I'm
going
to
filter
by
milestone
because
I
think
for
now
that's
what's
gonna
give
you
an
idea
of
what
is
going
to
be
fun,
mented
implemented
on
1300
that
I
design,
so
those
issues
are
not
active.
C
Those
are
all
in
reviewing
there,
so
you
axe
is
ready,
so
the
first
one
is
to
allow
I
release
milestones
to
be
added
to
the
release
base
or
D
Y.
So
this
is
belongs
to
like
a
bigger
effort
to
make
all
the
API
attributes
around
generation
of
releases
be
available
in
the
UI,
though
this
probably
this
12.0.
So
it's
a
leftover
and
also
another
small
issue
that
comes
from
development
and
small
coffee.
So
when
I
look
at
this,
it
looks
like
I'm,
not
a
unity
for
$13.
A
A
C
C
C
We
only
when
developers
can
schedule
the
implementation
when
they
have
capacity.
Okay,
yeah
I
know
the
milestone.
Is
the
delivery
right
for
the
release
post
for
to
being
a
brother?
So
when
I
work
with
them
and
I
save
you
access
ready,
they
move
from
the
plenty
water
to
the
dashboard.
Okay,
it
works.
For
me,
okay,
Nadia
help
me.
A
Sorry
I
was
taking
notes
so
I'm.
Actually,
my
first
question
with
that.
So
right
now,
I
feel,
like
your
column,
is
being
their
biggest.
What
is
the,
how
do
you
think
Quetelet
takes
this
priority
like
how
does
give
up?
So
why
is
the
first?
One
is
the
first.
The
second
is
the
second
in
okay,
I'm
like
how
does
the
qiblah
shows
the
order
of
the
issues?
Is
it
relevant.
D
A
C
D
Chicken
Clint,
like
was
it
like
headers,
are
like
it's
something
in
there,
so
sarah
has
changed.
We
have
a
board
for
our
stuff
and
it's
basically
like
that
kind
of
a
Kanban
board,
and
we
have
little
headers
in
our
column
of
like
to
do
doing
dining
backlog,
and
so
we
can
just
drag
the
tiles
into
the
sections
that
we
need
them
to
be.
Don't
know
how
she
did
that.
D
So
it's
not
that
you
should
change
the
title
of
the
issue.
It's
like
you
have
this.
It's
like
a
placeholder
issue,
maybe
looks
like
she
did,
so
we
can
just
move
these
anywhere.
We
want
under
the
doing
and
then
we
have
like
to
do
and
then
blocked
and
backlog.
So
there
it's
kind
of
like
individual
Kanban
boards.
D
D
C
D
Yeah
I'd
show
you
my
ignorance
of
how
our
actual
program
works
so
yeah,
so
that
there's
that,
but
otherwise,
no
like
we
can,
we
can
drag
so
I.
Guess
we're
grooming
in
that
sense,
because
there's
no
other
status
that
will
move
them
for
us,
because
these
look
to
be
like
placement
issues
that
she
created
as
T
be
used
as
like
column
headers,
but.
C
A
B
C
Way
we
use
it
in
release
management
that
we
have
the
combo
box.
Let
me
show
my
screen
and
then
you
have
that
these
that
are
in
the
workflow,
and
there
are
science
you
you
like
here,
but
then
you
also
have
the
milestones
columns.
So,
for
example,
I
know
that
these
are
the
things
priorities
for
thirteen
that
RP
ones.
B
B
C
The
way
I
use
is
that,
because
the
bars
are
they
belonged,
let's
say
to
the
PM
or
the
EMS.
I
have
my
issue
here
and
then
these
are
my
priorities,
although
they
are
not
labeled,
but
those
are
assigned
to
me
and
I'm
my
board
and
then
everything
else
that
is
on
12,
10,
13
or
13
1
whatever
and
merge
requests
I
take
care
of
them.
Let's
say
on
the
side,
because
the
boards
yeah
and
I
also
use
this
one,
so
the
P
ones
for
engineers
that
require
anywhere
support.
So
it's
difficult
to
concentrate
everything.
C
One
view,
that's
why
maybe
we
can
add
milestones
these
and
deaths,
but
each
team
with
their
PM's
and
me,
and
they
have
a
different
like
a
particular
way
to
organize
things.
I
think
they're,
gonna
use
something
like
this,
for
example
to
say:
yeah
they
meet
Lee
is
working
on
this
DHG
visualization
and
I'm
also
working
on
something
related
to
pipelines.
Whatever.
Then
we
can
cross-reference
listings
and
have
a
conversation,
but
what
happen
you
just
to
look
at
it
and
see
what
I'm
doing
next
I
cannot
even
tell
you
from
this.
It's
very
it's.
A
It
sounds
like
done,
and
one
I'm
curious
to
give
you
the
ability
to
keep
your
perspective,
but
by
what
you
can
admit,
you're
saying
it
sounds
like.
Maybe
we
should
not
for
if
we
ever
to
continue
with
these
meetings,
maybe
we
should
be
using
each
of
our
own
ways
to
show
that
priorities
to
show
the
work.
For
example,
can
you
have
the
issue
Timmy
tee?
You
have
the
board
with
your
own
label.
A
So
maybe
you
know,
while
we
are
presenting
I
can
see
us
also
you
each
one
of
us
using
our
own
boards
or
issues
to
like
just
because
the
goal
here
is
to
a
line
right.
It's
not
necessarily
to
utilize
that
board
that
we
created,
if
that's,
not
gonna,
not
really
gonna
work.
I,
know
what
you
guys
think
and.
C
Then
maybe,
if
you're,
using
like
this
board
or
whatever
other
tools
or
assets,
maybe
we
should
just
list
the
issues
that
we're
going
to
be
working
on
in
the
document
first,
but
the
agenda
doc
or
something
you
say
that
yeah.
Those
are
my
issues
and
those
are
the
topics
or
this
overlaps
with
third
for.
B
Like
a
one-time
like
create
an
agenda
for
the
items
that
this
to
be
discussed,
it's
gonna
be
very
clear.
We
have
a
common
document
which
we
can
comment
in
right
in
yeah,
I
see
that
as
a
because
we're
all
working
so
differently
currently-
and
there
might
be
some
consistency
later
in
the
future,
but
for
now
I
think
that
if
I
can
you
know
and
in
between
solution
ad
or
a
solution,
I.
E
I
was
gonna
say
that
I
agree,
I
mean
I,
don't
think
everyone
needs
to
present
the
same
way.
I
think
the
board
right
now
actually,
for
me,
I'm
not
claiming
these
as
a
like
canonical
solution,
but
for
me
it
definitely
matches
a
little
bit
of
how
I'm
working
on
the
things
that
I'm
working
of
course
there's
a
lot
of.
E
We
worry
we're
kinda
like
in
a
mixed
situation,
because
we
have
implementation
issues
that
have
designed
components
or
inside
dependencies
and
design
issues
that
are
just
design
issues
but
yeah.
Those
are
my
thoughts.
My
doubts
is
that
I
can
totally
use
this
work,
but
I'm,
okay,
with
anyone
doing
their
thing
and
just
outlining,
which
I
think
still
looking
at
all.
A
Oh,
it
sounds
like
the
proposal
from
Waianae
geometry
that
some
work
for
them
is
to
have
like
a
document
for
these
sessions,
where
we
would
be
like
listing
the
things
that
we
are
currently
working
on.
Would
you
be?
Would
everyone
be
okay
to
try
that
in
the
future,
if
I
would
make
such
a
document
for
us
and
yeah.
E
C
Then
we
can,
just
for
example,
uniquely
uses
like
mike,
has
is
important
in
me
to
use
it
something
we
can
just
link
this
in
the
document
and
then
just
present
or
just
share.
You
know
we
don't
have
you
to
copy/paste
like
a
list
of
issues
somewhere
else,
because
I
had
this
I
realize
I
had
this
problem
last
week,
where
I
was
updating
my
priorities
in
two
different
places
and
that's
counterintuitive.
B
How
I
thought
about
it
is
that
we
like
just
for
this
one
time,
location
in
the
dark.
We
do
this
like
we
copy
the
URLs
and
I
unlikely.
I
got
this
Chrome
extension,
which
makes
it
really
easy
for
me
to
copy
all
my
tabs
in
my
current
window
and
paste
it
as
one
big
block
into
a
document.
Then
that
does
not
become
my
single
source
of
truth,
but
it
does
allow
us
to
have
discretion
in
that
one
single
meeting
we
have
in
order
to
be
able
to
say
inside
of
the
document
per
issue.
B
We
can
say:
hey
I'm
interested
in
this
issue.
I
think
this
could
be
very
valuable
and
then
paste
them,
because
if
we
only
link
towards
you
know,
you
link
towards
your
issue
I
link
towards
my
board
Kuang
links
towards
this
other
list
of
assigned
issues.
Then
we
cannot
have
that.
You
know
comments
per
issue
kind
of
thing.
What
what
were
you
thinking
about?
That.
C
B
C
C
Something
like
the
same
as
we
do
with
with
our
agenda:
that's
why
we
say
research
issues
or
issues
that
are
blocked,
and
things
like
that.
But
I
know
maybe
we
can
try
later
and
see.
What's
what
structure?
What
are
we
trying
to
present?
You
know
so
that
everyone
in
a
way,
even
though
you're,
showing
different
issues
but
kind
of
meets
the
similar
criteria
here
like
next
up
or
needs
research
or
in
progress
validation,
whatever.
A
Yeah
I
think
grouping
is
always
how
help
me
helpful
for
like
readability
and
also
like
viewing
somebody's
else's.
What
because
it's
not
usually
very
easy
to
understand
what
somebody
else
is
doing.
I
think
if,
when
it's
kind
of
like
structured
by
some
type
of
yeah
like
label,
like
that,
your
research
or
I,
don't
know
or
design
sprint
or
ideation
or
whatever,
it's
always
more
helpful
to
digest
and
well
anyway,
I
really
appreciate,
like
everyone
kind
of
like
brainstorming,
as
we
go
right
now
here,
I
think.
A
As
with
every
other
meeting
format,
we
will
eventually
come
to
a
bit
more
ideal
as
face,
but
I
think
this.
Some
great
idea
is
just
to
like
give
it
a
go
and
see
how
this
will
work
out.
But
to
me
this
sounds
like
a
good
proposal.
I'll,
probably
just
like,
add
a
table
or
something
or
like
a
format
that
we
could
reuse
for
every
session.
I
have,
as
notes
and
I,
would
play
some
columns
like
that
and,
of
course
feel
free
to
help
me
out
with
columns.
B
A
I
think
that
I
just
wanted
to
suggest
this
anything
looks
like
try
to
do
a
little
bit
of
a
good
job
here,
just
well.
Whatever
we
have
today,
yeah
I
feel
free
to
even
like
show
your
maybe
I
was
thinking.
Maybe
everyone
can
use
their
own
ways
to
track
the
work
right
now.
Also,
it's
useful
to
see
how
different
people
are
in
different
states
are
tracking
the
board
like,
for
example,
hannah
has
one
way
to
media's.
E
E
E
E
Right
is
currently
working
on
adding
management
capabilities
to
the
group
level
runners,
and
there
is
what
we're
doing
this
is
because
we
have
a
big
client
would
be
supreme
who's,
moving
from
EEE
from
self-hosted
to
dot-com
and
in
that
transition.
Part
of
the
things
that
they
were
requiring
was
like.
We
need
something
to
manage
runners,
the
same
way
that
we
manage
runners
from
the
admin
level
at
self-hosted.
So
we
came
up
with
the
solution
solution
which
is
basically
creating
things
at
the
group
level.
So
there's
there
has
been
a
lot
of
design
going
on.
E
E
Testing
has
a
lot
of
things
going
on
right
now
as
well.
There's
a
lot
of
low-hanging
fruit,
things
that
we
are
trying
to
do
right
now
with
M
our
widget,
so
we're
shipping.
Actually,
this
one
is
somewhere
here,
we're
shipping,
the
accessibility,
merge,
request
widget,
so,
for
instance,
right
now,
I
have
review
to
do
for
DS.
There's,
probably
gonna
be
a
little
bit
of
design
iteration
happening
on
these.
This
is
an
implementation,
but
there's
also
like
a
handful
of
things
related
to
this,
which
are
basically
signed
items
that
are
happening
for
13.1.
E
There
so
yeah
there's
several
like
merge,
request.
Widget
initiatives
happening
right
now,
we're
working
on
certain
point
on
those
there's
also
a
couple
of
things
that
we're
doing
on
visual
review
tool.
So
one
thing
that
we're
gonna
do
is
that
we're
going
to
allow
we
should
review
tool
to
accept
a
screenshot
from
the
clipboard,
and
that
has
a
couple
of
like
design
things
that
we
got
to
do.
E
I
already
did
a
mock-up
for
this,
but
we
might
need
to
redo
that
because
we're
gonna
be
more
M
and
we
see
for
this
this
design,
code,
quality
reports
or
filter
and
search.
This
was
gonna,
be
design
adding
for
thirteen
point,
oh,
but
we
actually
moved
that
to
thirteen
point
one
one
right
now,
but
I'm
still
gonna
work
on
thirteen
point.
E
These
one
is
blocked,
but
we
have
a
big
initiative
with
RAF
code
coverage
right
now.
So
we
did.
We
have
a
canvas
ready
that
we're
working
on
it
already
did
kind
of
a
useful
mapping
session.
We
James
about
these.
It
went
pretty
well,
so
we're
basically
planning
the
MVC
for
these
I
have
to
do
more
mock-ups
for
these
god.
There's
many
things.
There's
one
extra
cool
thing
that
I'm
working
on
right.
Now,
these
link
to
test
reports
from
Mr
widget,
that's
a
full
feature
and
I
already
wrote
the
code
for
this
whole
feature.
E
So
I'm
excited
about
that,
because
it's
like
the
first
time
that
I
happen
that
I
actually
wrote
it
from
end
to
end.
It's
failing
a
bunch
of
pipeline
so
definitely
already
means
top
point
and
that
hopefully
it
makes
it
to
third
point
second
point:
oh,
but
yeah
I'm
excited
that
I
took
that
one
I
was
able
to
put
it
together.
A
E
That's
a
great
question,
so
we
are
gonna,
have
another
sink
up
for
13
point.
Oh
I
think
I
think
there
unblocked.
Basically
the
conclusion
that
we
reach
was
you
do
your
thing.
We
do
everything
that
you
tell
us
what
you're
doing
so,
we're
aware
of
that
and
vice
vice
versa.
So
I
think
that
was
kind
of
like
the
conclusion
and
blocking
venue.
You
know
like,
let's
simply
communicate
to
each
other.
A
E
A
This
is
amazing
thanks
a
lot
with
overview
of
what
Runner
and
testing
RBZ
with
in
terms
of
functionalities.
So
again,
if
like
the
goal,
is
towards
it
to
find
dependencies
each
other
or
you
know
like
something
where
places
where
we
could
advise
each
other,
that's
perfect.
So
thanks
a
lot
for
taking
the
first
play
here.
Jimmy
did
you
wanna?
Could
you
walk
us
through
some
of
your
stuff
yeah.
B
Actually,
one
comment
towards
one's
work.
I
put
the
link
into
it
into
the
document.
It's
about
his
first
item.
I
was
relief
trying
to
get
you
know
this
one
thing:
where
is
it
for
the
family
founded,
but
there's
this
one,
an
interview
which
I
did
with
the
customer
Nvidia
and
they
we
thought
that
we're
gonna
talk
about
public
apartment,
which
we
didn't
do
in
the
end
at
all.
B
They
want
something
very
different,
so
you
know
there's
that
point
of
like
understanding
of
something
and
our
understanding
of
something
yeah
and
basically
what
we
what
we
talked
through
was.
You
know
like
how
to
be
like
brothers
and
they're
there,
their
fleet
of
runners-
and
they
have
some
special
things
about
that
as
well,
but
it
might
be
very
interesting
young
go
to
through
that
one.
It's
the
eighth
one.
It's
like
yeah
I'm,
seeing.
A
B
B
So
same
board,
but
I
felt
it
a
little
bit
differently.
So
this
are
my
programs
issues.
These
are
not
all
I
need
to
do
a
little
bit
cleaning
up,
but
these
aren't
please
have
some
of
the
most
important
ones.
So
this
is
distributing
daily
crown
schedules
of
the
hour
is
a
pretty
pretty
weird
issue
interests
about
this
is
then
our
schedules
and
their
crunch
I'm,
set
to
a
specific
time.
B
Everyone
selecting
the
presets
which
allows
our
fleet
of
runners
to
spike
on
those
set
time,
so
it
is
more
of
like
a
resolving,
and
you
know
what
an
infrastructure
issue,
but
also
providing
a
good
experience
towards
the
user,
and
not
you
know
making
that
a
negative
experience
anyway,
not
too
much
special
than
just
some
conversation.
If
you're
interested
in
joining
joining,
let
me
see
come
up
with
design
for
this
life,
dag
that
is
in
full
effort.
B
I
hope
I
hope
that
we're
doing
a
little
with
different
progress
there,
which
front
end
and
UX
both
idat
towards
agreeable
and
feasible
concept,
sort
of
immediately
going
for
something
that's
gonna,
be
merged
into
master
because
of
the
the
nature
of
this
kind
of
problem,
but
trying
to
get
to
in
visualization
with
the
visualization,
with
a
reduce
scope
that
can
visualize
the
connections
between
deck
jobs.
For
now
on,
there's
it's
very
complex
with
a
very
visual
issue.
It's
very
interested
to
read
it.
B
B
Don't
use
more
into
work
for
refinement
right
now,
because
it
was
I
really
intended
to
be
developed,
and
then
there
was
something
wrong
room
which
we
need
to
look
into,
but
that
New
York's
warning
is
not
important
and,
lastly,
a
be
testing
problem,
validation,
which
I'm
working
on
a
discussion
guide
for
the
validation
effort
there
not
too
much
yet,
but
all
help
is
welcome,
especially
for
this
one.
If
you
have
any
related
items
you
know,
hey
I
would
like
to
find
out
this.
B
C
It
was
supposed
to
be
1210
thing.
You
have
13
dogs,
you
I'm
gonna,
read
your
issue
description,
but
it's
so
interesting
to
see
that
you
have
in
DUI
the
Quran
this
kindness
right
every
day
at
4:00
a.m.
and
every
week.
Yes,
thanks,
Orion,
etc,
and
for
us
developers
they
say
that
making
this
translation
dy
was
too
difficult,
so
I'm
just
gonna.
C
B
It's
there
and
there's
a
few
solutions
being
discussed.
I
think
one
is
the
superior
one,
but
increases
the
scope
of
a
quick
fix.
Do
you
know
like
properly
doing
it,
but
there's
some
in-between
solution
as
well,
and
we
finalize
that
that
discussion
I
have
yet
to
look
into
it
today,
so
we're
left
it
before
it
went
out
of
office
thanks
for
that
issue,
I
will
surely
look
into
them
by
the
way
it
links
towards
a
PNG.
Is
that
correct.
C
C
C
So
that's
not
very
interesting
for
this
meeting,
and
the
next
big
thing
should
be
working
on
is
the
when
for
sure
that
it's
scheduled
is
the
director
level
see
ICT
group
dashboard
that
have
super
weird
name,
but
it's
pretty
much
having
the
ability
to
see
data
about
your
project
on
a
group
level
and
that
this
will
be
interesting
to
these
personas
race.
Monitor
my
as
director
is
so
very
important.
People
that
want
to
know
other
projects
are
doing
how
their
release
is
mainly
for
now
their
releases
and
we're
focused
on
just
a
few
data
points.
C
So,
for
example,
the
number
of
projects
in
your
release
and
the
latest
release
how
many
what
percent
of
the
project
actually
released,
the
last
five
five
lines,
the
past
cetera
and
I
haven't
started
like
any
UX
per
se,
and
it
is
ideal
in
opposing
this
issue.
This
has
been
going
on,
I
think
for
two
milestones
for
two
reasons.
The
first
one
is
that
we
want
to
make
sure
that
we
are
reused
in
pajamas
components
or
view
components
and
the
ones
for
data
visualization
that
we
have
I'm,
not
very
complete,
so
I
need
to
look
into.
C
What
can
we
do?
What
can
we
reuse?
Another
thing
is
that
we
change
the
scope
of
needs
a
couple
of
times
to
make
sure
that
we
are
not.
You
know
creating
too
many,
so
many
opportunities
to
over
commit,
if
that's
make
sense,
anyways
and
I'm
going
to
try
to
look
at
this
now,
because
it's
13.3
just
to
have
an
idea
of
what
components
we
would
need
if
we
can
reuse
so
many.
Why,
for
example,
from
the
environments
dashboard,
but
it's
known
about,
etc,
etc.
C
So,
not
really
like
you
actually,
the
most
per
se
as
in
ready
to
be
implemented,
but
I'm
going
to
be
working
on
this
dashboard
Network
level.
That's
one
thing
and
the
thing
I
have
here
is
the
ability.
It's
like
delete,
religious
in
the
UI
on
the
release.
Page
I
have
the
prototypes,
but
the
prototypes
are
not
here
so,
as
I
mentioned
before
and
now,
if
you
go
to
project
or
review
releases,
you
have
a
button
and
god
this
was
not
here
guys.
It
has
been
missing
for
years.
C
So
what
we
want
is
to
allow
users-
it's
not
here
after
they
create
a
release.
Add
it
and
then
be
able
to
delete
this
item
right
now.
I
can
only
do
it
through
the
API,
so
not
super
exciting
I
already
have
the
mock-ups.
So
it's
a
small
update
and
the
last
one
is
identification
of
historical
releases.
So
it's
a
lot
of
release,
release
release,
which
is
the
ability
to
like
when
you've
changed
the
release
date
for
a
release.
C
Item
say
that
was
in
the
past
right
to
create
ovaries
last
year
yesterday,
whatever,
but
you
want
to
change
the
release
dates
to
today.
For
some
reason,
we
have
something,
as
called
as
historical
reason,
which
you
need
to
figure
out
the
name
for
that
the
same
way
as
we
have
a
copy
release
right
now,
release
in
the
past,
but
you
can
also
create
a
release
either
in
the
past
or
move
the
date
to
correct
date
or
the
future.
So
these
are
important
for
release
evidence
and
again.
C
This
is
already
like
acceptance
criteria
proposal,
not
this,
but
prototypes
are
missing.
So
my
items,
as
you
can
see,
are
super
small
because
I
already
groomed
most
of
them
they
are
in
the
backlog
or
there
are
being
scheduled
for
13.3,
13.0,
etc.
So
those
are
the
things
that
I
have
pending
and
let
me
see
if
I
can
show
you
some
of
the
UX
issues
here.
Yeah
and
the
issues
that
I
have
my
pipeline
now
are
all
in
that
I
don't
have
any
UX
open,
but
mostly
really
large
requests
and
that's
my
life.
C
It's
quite
scary
because
it
seems
like
I'm
not
doing
a
lot
so
wait
a
week,
then
everything's
gonna
be
a
mess
but
yeah
my
items,
I'm
not
super
exciting,
but
I.
Think
I'm.
Looking
to
you
what
Dimitri
has
shown-
maybe
some
of
the
items
they
are
ready,
they
are
considered
UX
ready.
They
need
to
be
revisited,
so
it
might
be
a
good
chance
to
have
this
conversations
to
make
sure
that
the
the
Purple's
are
are
aligned.
Yeah.
E
So
that
rapid
crash
that
it's
blocked,
but
it's
not
really
blocked,
because
what
we're
doing
right
now,
it's
doing
like
recovery
and
kinda
like
we
really
did
the
campus
review
and
everything
for
that.
One.
Someone
also
also
made
for,
like
director
level
type
of
thing
you
know
like
people
like
it's
gonna,
be
basically
a
graph
where
people
can
see
code
coverage
and
analyze
how
their
Koresh
is
changed
through
time,
so
they
can
like
tell
their
executive
team
like
hey,
teamÃs,
these
well
or
not
or
whatever
so
yeah.
E
E
C
C
E
E
A
All
right,
well,
I,
feel
like
this
was
super
insightful
was
really
nice
for
me
also
to
see
some
of
the
part
I
wasn't
aware
that
are
happening
and
hey
I
just
want
to
make
sure
cuz
I
think
every
one
of
you
commented
that
it
looks
like
I'm
not
doing
enough
less.
This
not
be
our
worry
during
these
presentations.
I
know
how
everyone
of
you
are
is
busy
right
now
so
yeah.
A
Let's
put
it
this
way,
let's
not
measure
the
busyness
in
the
number
of
issues
we
present,
because
this
is
not
really
color
ated
to
the
business
so
yeah.
Let's
not
be
worried
about
that
part.
Thanks
a
lot.
Everyone
for
sharing
this
I
love
that
it
allowed
us.
This
completion
allowed
us
to
already
identify
some
dependencies.
I'm
gonna
be
working
on
the
proposal
for
the
format
for
this
session.