►
From YouTube: Create UX Update - 13.1 - Ecosystem
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
Hello:
everyone-
this
is
Lemoore
Vance
senior
product
designer
on
the
ecosystem
team,
and
this
is
my
create
UX
kickoff
for
thirteen
point
one.
So
today,
I
want
to
talk
about
this
solution.
Validation
issue
that
I'll
be
working
through
for
the
first
part
of
the
milestone,
and
this
solution.
Validation
issue
is
to
validate
most
of
the
design
work
that
I
worked
through
for
the
mass
integration
feature
and
just
a
reminder
that
feature
the
mass
integration
feature
is
to
allow
instance
and
group
owners.
A
The
ability
to
set
settings
unless
sets
settings
for
each
project
in
a
less
manual
way,
so
give
me
them
more
of
a
bulk
kind
of
controls
over
their
settings.
So,
for
example,
if
I'm
a
group
owner
and
I
have
a
JIRA
group
owner
and
I
have
a
hundred
projects
under
that
group
and
I
want
to
have
make
sure
that
all
those
projects
have
the
same
Duras
setting
I
just
have
to
set
it
once
at
the
group
level,
and
then
all
those
settings
will
propagate
down
to
to
all
the
individual
projects.
A
So
a
lot
of
work
has
been
already
done.
There's
a
lot
of
design
work
that
outlines
the
ideal
state
for
how
the
feature
should
work.
So
that's
all
in
this
issue
here
all
the
different
design
work
based
on
the
different
user
stories
that
I
probably
mentioned
in
our
in
the
last
kickoff
video
for
the
last
milestone.
A
So
this
work
has
been
complete.
We're
also
working
through
this
MVC
discussion
on
how
to
break
down
this
ideal
state
into
a
smaller
iterations
so
back
to
the
solution,
validation
issue.
This
is
really
to
validate
how
some
of
this
new
work
or
the
ideal
state
how
it's
gonna
function
compared
to
this
first
iteration
it
that
we're
proposing
here.
A
So
just
to
give
you
all
an
of
what
that
will
look
like
this
is
looking
right
now
at
JIRA
integration
at
the
instance
level-
and
this
is
the
ideal
state
where,
where
the
instance
level
owner
will
have
granular
controls
over
each
different
field
and
for
our
first
iteration,
we
won't
be
able
to
deliver
this
type.
This
quite
this.
A
Quite
this
type
of
granularity
with
these
controls
just
yet
so
we'll
just
look
like
this,
so
want
to
validate
the
different
user
stories
that
we
have
currently
set
for
our
ideal
state
and
how
much
value
we're
still
going
to
be
delivering
at
this
state
without
those
individual
that
it's
not
that
granular
control
here.
Another
thing
that
the
issue
is
going
to
validate
is
how
an
instance
level
owner
that
might
have
some
like
a
JIRA
service
template
set
up
how
they
would
actually
go
about
migrating.
That
service
template
over
to
the
new
way
of
doing
integrations.
A
So
there's
three
things
that
there,
but
this
issue
is
going
to
work
to
work
to
validate
and
then
hopefully
we're
gonna,
learn
some
other
new
potential
user
stories
and
and
just
really
get
a
build.
Some
confidence
on
the
designs
that
have
been
created
already
yeah.
So
that's
it
for
for
this
quick
kickoff
video,
but
if
you
have
any
questions,
feel
free
to
leave
them
in
the
issue
and
otherwise,
thanks
for
listening.