►
From YouTube: Create UX Update - 13.0 - 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
So
in
this
milestone,
I'm
really
going
to
be
focusing
on
just
continuing
the
work
that
we've
been
working
through
over
the
past.
You
know
three
or
so
milestones,
which
is
called
this
mass
integration
at
a
group
level
at
the
group
level,
in
instance,
level-
and
this
is
the
epic
for
this
I'm
not
going
to
go
too
much
in
a
detail
about
what
this
works
about.
I
did
a
UX
showcase
on
this,
maybe
a
week
or
two
ago,
so
I
recommend
checking
that
out
to
learn
more
about
this,
but
at
a
high
level.
A
A
So,
for
example,
right
now
we
have
this
functionality
at
the
instance
level
called
service
templates,
so
that
allows
you
or
that
allows
an
admin
to
set
up
a
template.
So,
for
example,
they
could
go
to
Gaea
here,
set
their
own
URL
and
hit
save.
So
now,
every
project
that's
created
on
this
instance
will
automatically
have
a
JIRA
integration
set
up
and
they
will
have
this
URL
set
up.
A
So
this
has
some
limitations,
so,
for
example,
if
that
project
owner
now
decides
to
override
this
URL
with
something
else
and
hit,
save
me
as
the
admin
has
no
idea
that
that's
been
overridden
and
there's
no
way
for
me
to
just
hit
save
again
and
have
that
have
those
changes
propagate
down
to
all
the
projects.
So
it
really
really
works
it
just
like
as
a
one-way
flow
right
now
it
really
works
it
just
as
a
template.
A
So
that's
that's
what
what
this
new
functionality
will
bring
is
a
the
ability
to
dynamically
kind
of
update.
This,
like
I,
mentioned,
let's
just
say,
phu
kham
again,
and
if
I
had
saved
all
my
projects,
whether
they're
all
new
and
old
projects,
will
all
have
this
value
set
and
we're
also
introducing
a
way
for
the
admin
to
see
what
what
projects
are
actually
overriding.
These
settings
because,
for
example,
you
may
actually
want
some
projects
to
to
not
use
these
settings.
A
So
that's
that's
kind
of
the
the
summary
of
what's
happening
in
this
this
epoch,
so
the
design
work
for
this
has
been
wrapped
up
in
twelve
ten.
That's
all
that
could
all
be
found
in
the
this
issue
called
end
and
maka
for
mass
integrations.
So
if
you
want
to
learn
more,
there's
also
a
kind
of
video
walkthrough
that
walks
through
some
of
these
prototypes
and
user
stories,
but
back
to
the
work,
that's
going
to
be
happening
at
13.0.
I
have
an
issue
here.
A
A
We
wanted
to
kind
of
automatically
pull
them
for
you
from
your
gr
instance,
but
again,
there's
some
inconsistencies
with
how
they're
there
api's
are
set
up.
So
this
is
still
a
work
in
progress.
We've
done
a
lot
of
work
already
on
this
issue,
some
really
hoping
that
we're
gonna
be
able
to
close
this
in
13.0
just
some
background
on
even
what
this.
What
this
even
means-
I,
don't
know.
A
If
anyone,
if
everyone
on
the
team
knows
but
I'm
gonna,
just
go
back
here
and
pretend
that
let's
say
this
is
a
at
the
project
level
and
let's
say:
I-
go
to
G
R,
my
JIRA
integration
of
the
project
level
you
can
see
here.
This
is
this
field
that
says
just
transition
IDs.
So
this
is
I,
think
for
even
existing
users
of
JIRA
I.
Think
it's
hard
to
understand
what
this
even
is.
A
So
to
give
you
all
a
quick
summary
of
what
a
transition
ideas
are
this.
What
this
integration
does
is
imagine
that
you
are
using
JIRA
for
all
your
project
management
and
you're
using
the
conv
Kanban
board
functionality,
and
you
have
some
issues
that
are
in
backlog.
Some
are
in
development
and
some
are
maybe
like
already
in
the
close
column.
A
What
will
happen
is
that
will
that
will
change
this,
this,
the
the
status
of
that
JIRA
issue
to
to
transition
over
to
the
last,
the
last
column
or
the
last
workflow?
That's
the
senior
JIRA
project.
So
what
this
field
actually
is
asking
for
is
it's
asking
for
the
last
it's
asking
for
the
ID
of
that
last
state
in
your
workflow,
your
JIRA
workflow.
So,
for
example,
you
would
want
to
be
looking
for
the
issue.
The
ID!
That's
for,
like
the
closed,
is
board,
for
example,
so
yeah.
A
So,
there's
a
lot
of
improvement
that
we
could
do
here
just
to
make
just
just
with
like
better
help
text
and
microcopy
just
to
first
of
all
explain
what
this
functionality
even
does,
but
also
just
making
it
easier
for
you
to
get
that
ID.
So
just
for
me
to
understand
how
to
get
this
ID
I'm
just
gonna
go
through
that
process
really
quickly.
So
what
I
had
to
do
was
first
I
had
to
go
through
this
go
through
the
documentation.
Thankfully,
there
was
like
a
I
read
through
this
really
quickly,
but
I.
A
Think
Lee,
there's
a
pretty
good
video
here
on
how
to
to
go
about
doing
doing
that.
So
I
ended
up
then
going
through
watching
this
video,
and
here
are
the
the
JIRA
columns
that
you're
a
common
board
like
I
mentioned
so
I
forgot,
where
it
was
somewhere
in
the
video.
This
kind
of
just
describes
the
functionality,
but
in
order
to
get
that
ID
not
gonna
find
khun's.
A
I'm
not
gonna,
find
it
now
but
anyways
in
order
to
get
that
ID
I
had
to
kind
of
obviously
go
through
his
documentation
and
then
find
there's
different
links
that
you
have
to
go.
Click
through
inside
of
your
your
JIRA
project
to
get
to
somewhere
where,
where
the
the
G
R
API
is,
and
that
actually
lists
out
all
of
your
lists
out
a
JSON
file
of
all
those
all
your
all
your
existing
IDs
for
all
your
for
your
boards
or
from
sorry
for
your
columns.
A
So
once
you
have
that
ID,
then
you
could
go
back
here
and
then
you
paste
that
ID
in
here.
So,
for
example,
let's
say
your
last
column
is
12
like
your
closed
column
in
JIRA,
so
you'd
put
your
12
in
there
and
hit
save
it's
very
unintuitive
and
we
could
definitely
do
a
better
job
of
making
that
more
user-friendly.
A
So
in
this
issue,
we've
kind
of
worked
through
this
where's
that
issue
again
I
hear
so,
ideally,
there's
like
a
kind
of
a
low
fidelity
mock-up
here,
where
we're
kind
of
going
with
this.
So,
instead
of
asking
the
user
to
just
enter
an
integer,
we
could
ideally
kind
of
surface
these
IDs
with
a
more
human
readable
label
and
then
just
allow
them
to
kind
of
pick
and
choose
which,
what's
their
last
workflow
ID
and
hit
save
yeah.
So
going
back
to
the
board.