►
Description
Related issue: https://gitlab.com/gitlab-org/gitlab/-/issues/416801
A
Hi
everyone-
this
is
Emily
cybrandt
senior
project
designer
on
plan,
project
management
and
today
I'm
going
to
be
walking
through
some
of
the
changes
that
we
are
proposing
to
attribute
and
attribute
selection.
As
part
of
the
work
item
detail
view
updates
so
before
I
dive
into
this
I
want
to
quickly
take
a
look
at
what
attributes
and
attribute
selection
look
like
on
both
a
legacy
issue
and
then
also
a
work
item,
so
a
task
so
on
our
Legacy
issues.
Today,
attributes
are
here
in
the
sidebar
in
order
to
edit
them.
A
We
click
the
edit
button.
It
makes
an
individual
attribute
editable
and
then
we
can
make
a
selection
attributes,
look
quite
a
bit
different
on
work
items
so
I
have
an
example
here
with
a
task
here.
The
the
attributes
not
only
look
a
bit
different,
but
they
also
behave
differently
so
they're
shown
here
at
the
top
and
in
order
to
edit
them.
I
can
hover
over
to
see
that
this
is
an
editable
item
and
then,
when
I
click
into
it,
I'm
right
away
into
an
editing
mode.
A
So
you
know,
as
we're
thinking
about
updates
to
the
work
item,
detail
view
we
really
want
to
think
about
particularly
the
migration
path
as
we're
working
to
migrate,
epics
issues
and
other,
like
planning
objects
into
the
workout
and
framework.
We
want
to
make
sure
that
as
we're
going
through
that
migration
we're
thinking
about
both
usability
and
consistency,
so
we
want
to
make
sure
that,
for
example
like
when
we
migrate
epics
to
work
items,
but
issues
are
still
in
the
old
issuable
framework
that
there's
not
such
a
giant
gap
between
those
things.
A
We
know
already
that
users
don't
really
think
about
that
as
like
a
big
difference,
they
don't
really
see
or
they're,
not
really
as
tuned
into
like.
Is
it
an
issue?
Is
it
an
epic?
We
want
to
make
sure
that,
when
you're
doing
a
similar
task
like
updating
a
label
on
a
planning
object,
we
want
to
make
sure
that
that's
like
a
consistent
experience
for
you,
no
matter
where
you
are
so
with
that
I'm
going
to
dive
into
the
designs.
A
A
That
is
something
that,
if
we
decide
to
do
this
for
work
items,
we
would
also
have
to
Port
this
back
to
Legacy
planning
objects
as
well,
and
we
would
even
have
to
talk
to
the
create
team
for
Mrs
and
make
sure
that
they're
aligned
with
this
and
from
our
research.
We
know
that
getting
into
the
editing
state
is
not
really
something
that
users
are
struggling
with.
It's
not
really
a
user
need.
So
that
is
why,
from
a
ux
perspective,
our
ux
recommendation
is
to
make
a
much
smaller
change
in
this
area.
A
So
the
change
we're
proposing
is
very
similar
to
what
we
have
on
issues
and
ethics
today,
with
the
edit
button,
bringing
the
edit
button
back
in
for
consistency,
but
making
some
visual
updates
to
make
it
a
little
bit
more
condensed
and
a
little
bit
cleaner
to
match
the
rest
of
the
work
item
detail
and
by
keeping
things
consistent.
That
allows
us
to
iterate
into
the
migration
path.
So,
if
epics,
for
example,
were
to
move
to
work
items
but
issues
weren't,
this
would
not
be
a
problem.
A
So
what
we
know
from
research
is
that
the
biggest
area
for
opportunity
biggest
area
of
opportunity
for
improving
the
usability
of
attributes
is
in
the
selection
of
the
attributes,
particularly
multi-select.
So
things
like
labels,
assignees
single
select
patterns,
are
much
simpler
and
probably
don't
really
need
much
of
an
update.
A
So,
with
that
in
mind,
I
have
proposed
a
couple
different
options
and
both
of
these
options
have
pros
and
cons
and
they're,
both
ones
that
you
know
ux
would
really
be
comfortable
moving
forward
with.
So
this
is
something
that
I'd
really
like
to
get
yells
feedback
on
in
terms
of
feasibility
time
and
also
you
know,
usability
what
what
what
the
rest
of
the
team
thinks
so
I'll
just
walk
quickly
through
the
couple
different
options
that
we're
proposing.
A
The
first
option
is
very
similar
to
what
we
have
in
Legacy
issues
and
epics.
Today,
with
the
select
item
and
the
drop
down,
but
some
just
little
tweaks
to
clean
this
up
and
make
it
a
little
more
usable,
an
easy
way
to
clear
everything,
an
easy
way
to
apply,
because
some
users
don't
know
that
they
have
to
click
out
in
order
to
apply
their
changes.
A
A
So
this
is
something
that
we
would
have
to
back.
Pour
it
into
Legacy
issues,
epics
and
probably
make
available
for
the
create
team
for
Mrs,
make
sure
they're
aligned
with
this
as
well,
because
when
you're
selecting
labels
across
git
lab,
we
want
that
to
be
a
consistent
experience.
No
matter
where
you
are,
we
don't
want
you
to
have
to
think
that,
like,
oh,
you
know
which
type
of
object
am
I
on.
How
do
I
do
it
on
this
object?
A
We
want
that
to
be
a
consistent
experience,
but
we
believe
that
this
is
a
bigger
usability,
Improvement,
so
I
think
it
really
is
worth
that
work
to
be
able
to
backboard
it
into
Legacy
issuables,
because
there
are
a
lot
of
usability
improvements
here,
so
I
detail
more
of
the
pros
and
cons
here.
I
would
love
to
get
y'all's
feedback
thanks
for
watching.
Please
leave
your
feedback
in
the
figma
or
on
the
issue
thanks
so
much
bye.