►
From YouTube: Plan UX walkthrough of work item annotations
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
Hey
everyone
just
wanted
to
give
a
quick
overview
of
the
annotations
for
the
work
item
screens
if
anything
is
missing
or
if
you
have
any
questions
at
any
point,
please
let
me
know
there
is
a
lot
to
kind
of
cover
here,
so
I
want
to
be
mindful
of
time,
but
also
find
any
opportunities
to
reduce
scope
if
need
be
for
mvc.
If
I,
if
I
have
misunderstood
anything
or
added
in
more
than
what
we're
capable
of
doing
I'm
happy
to
have
those
conversations,
so
this
is
first
screen
is
just
some
general
design
details.
A
The
padding
for
the
designs
is
consistent
with
the
current
site,
so
we
currently
have
16
pixel
margins.
I
believe
on
the
left
and
right
I
put
padding,
but
I
think
technically,
it's
margins
on
the
left
and
right
of
the
design
and
I
believe,
top
and
bottom
as
well,
so
it
should
be
consistent
with
that
no
changes
there.
A
One
key
difference
is
that,
after
thinking
about
it
further
reviewing
competitors
and
talking
with
folks,
I
feel
that
it's
better,
that
we
have
these
items
open
by
default
in
a
new
panel,
so
it
would
open
either
on
mobile
as
an
overlay
here
or
on
desktop
as
a
modal
and
eventually
I'd
love
the
thought
of
having
those
available
in
the
side
panel
as
well,
but
we
don't
necessarily
have
to
explore
that
for
nbc.
A
I
did
create
designs
showing
it
also
directly
on
the
page,
it
being
the
screens
that
I'm
about
to
walk
through
here
the
various
pages
associated
with
the
use
case
for
work
items.
So
I
do
have
an
example
of
it
displayed
directly
on
the
screen
with
the
get
lab
chrome
around
it,
the
navigation
and
all
of
that,
but
I'd
like
to
reduce
context,
switching
to
explore
going
with
this
as
an
overlay.
A
So
if
anyone
has
questions
or
concerns
about
that,
please
let
me
know
so
that's
kind
of
what
these
first
two
notes
here
are
about
for
the
breadcrumbs.
I
have
a
question
here.
This
might
be
out
of
scope,
so
if
it
is
just
let
me
know,
but
I
love
the
thought
of
being
able
to
reduce
some
of
the
information
overload.
That
happens
with
breadcrumbs.
A
So
I
would
love
to
have
just
the
top
level
group
followed
by
the
immediate
project,
followed
by
either
new
work
item,
if
they're
creating
a
new
work
item
or
the
actual
work
item,
name
or
id,
rather
as
part
of
the
breadcrumbs
rather
than
have
all
of
the
various
levels
represented
and
instead
have
the
little
dot
dot
dot
here
to
show
sort
of
the
in
between
areas
for
those
and
when
they
click.
Perhaps
it
expands
to
show
those
details
in
like
an
overlay
or
a
tooltip.
A
We
do
obviously
have
that
currently,
but
I
think
it
shows
that
maybe
five
levels
deep
or
it's
a
few
levels
deeper
than
than
I
would
like.
I
would
like
to
show
it
sooner
just
on
mobile,
in
particular,
to
reduce
the
amount
of
information
that's
being
squished
in
there.
Also,
I've
heard
from
people
that
not
only
is
it
not
necessarily
meaningful
to
see
all
of
the
various
levels,
deep
that
the
item
exists
in,
but
it's
a
little
confusing
actually
as
well.
People
don't
really
know
how
to
interpret
it
or
know
what
to
do
with
it.
A
So
I'm
hoping
that
that
could
reduce
some
of
the
confusion,
but
again
might
not
be
nbc.
So
let
me
know
if
that's
the
case-
and
we
can
in
that
case,
go
with
the
current
breadcrumbs
approach
and
then
continue
to
iterate
on
it
in
the
future.
A
For
the
title,
this
really
should
be
in
terms
of
font,
weight
and
size.
The
same
as
the
current
title
sizes
that
we
have
for
the
issues
screens
and
I
couldn't
find
just
a
title
in
gitlab,
ui
and
storybooks.
So
if
I'm
missing
something
there,
please
let
me
know,
but
I
really
did
try
to
look
through
it
and
find
something
that
was
just
the
title
represent
represented,
so
that
I
could
pull
the
name
and
have
that
included
here.
But
I
couldn't
find
it.
A
So
I
tried
to
just
kind
of
evaluate
the
color
difference,
which
is
really
the
only
difference
in
terms
of
the
title
styling,
which
would
be
that
gray,
400
and
then
this
would,
of
course,
also
be
clickable,
so
you
would
click
into
it.
The
user
could
immediately
edit
it
and
once
they
have
edited
it,
it
would
default
to
the
styling
that
we
have
for
our
current
titles
on
issues.
A
A
The
work
item
specifically
until
they
have
added
in
the
title
and
on
the
flip
side
of
that
they
can
add
in
only
a
title
theoretically
and
hit
create,
as
as
we
have
previously
discussed
next
is
assignee.
This
is
also
a
bit
of
a
new
component
in
that
this
circle
here
doesn't
exist
in
our
current
styles.
I
talked
with
jeremy
about
this.
A
Originally
I
had
agreed
based
on
his
recommendation,
to
go
with
the
sort
of
rounded
square
button
that
we
do
currently
have,
but
after
looking
at
it,
when
you
have
a
signees
applied,
let
me
just
go
down
here
where
you've
got
a
situation
like
this.
You've
got
the
sort
of
circular
avatar
beside
this
rounded
square,
plus
button.
It
felt
odd
it
almost
felt
like
like
it
would
have
a
different
result
than
being
associated
with
the
assignees.
If
you
were
to
select
it.
A
However,
I
know
that
that
is
a
new
pattern,
if
that
is
something
that
we
need
to
compromise
on
for
nbc,
I'm
I'm
open
to
discussions
on
that.
The
actual
text
for
that
should
also
be
consistent
with
our
link
styles,
and
I
think
I
just
realized
here
that
I
didn't
include
the
name
for
that,
so
I
will
add
in
the
the
name
for
that.
Just
so,
you
all
have
it
for
the
description.
Placeholder
again
I
added
in
the
text
color,
I
also
put
in
the
font
size
and
the
font
weight.
A
So
just
something
else
to
note
there
and
again
they
should
be
able
to
select
title
assignee
or
description
and
edit
those
at
any
point
when
they're
in
this
creation
process,
similar
to
our
existing,
create
issue
process,
but
they
cannot
create
the
work
item
as
a
whole
until
they
have
added
a
title
in
in
particular,
the
buttons
are
also
consistent
with
the
buttons
that
we
currently
use
for
creating
a
new
issue.
I
did
add
in
the
names
and
sizes
and
information
related
to
those.
A
But
please
let
me
know
if
anything
is
missing
there
or
any
questions.
You
can
see
that
I
put
in
the
disabled
state
when
the
title
until
the
title
is
entered
the
styling
for
the
cancel
the
background.
I
had
one
small
question
about.
We
do
have
this,
and
this
is
this
gray
footer
background
I'm
referring
to.
A
So
there
is
a
simple
top
border
applied
here
at
the
top
of
this
element
that
I'd
like
to
remove.
If
we
can
again
I'm
not
going
to
die
on
that
hill,
if
that's
something
that
is
going
to
add
to
the
scope
unnecessarily
for
this,
then,
because
I
know
that
might
be
tied
to
other
places
in
the
product,
then
I'm
okay
revisiting
that
and
going
with
the
default
footer
style.
For
that
gray
background
as
well,
the
next
is
inline
title
edit.
A
I
also
wanted
to
just
quickly
note
I
don't
have
all
of
the
screens
represented
here
that
are
in
the
prototype,
just
because
some
of
them
are
a
bit
redundant.
They
have
the
same
details
that
I've
already
documented
here,
so
I
only
documented
screens
that
have
components
that
haven't
been
documented
yet
earlier
in
this
process.
So
every
screen
has
some
documentation,
but
any
screen,
that's
not
represented,
is
not
represented
solely
because
I've
already
documented
the
styles
for
it
here
somewhere.
A
A
A
A
A
The
create
button
should
switch
to
that
success
state
once
the
title
has
been
entered
as
well,
and
then,
of
course,
the
other
details
here
are
noted
as
well
up
in
screen
one
so
screen.
Four
here
represents
showing
the
description
update
with
no
content,
and
this
is
again
focused
a
bit
more
on
mobile
at
the
moment.
This
information
should
also
still
translate
over
to
desktop,
with
the
exception
being,
of
course,
the
keyboard
here
should
not
display
would
not
display,
obviously
on
a
desktop
environment.
A
But
do
this
sort
of
visual
panel
switch
situation
when
you're
on
a
mobile,
but
that's
what
I
would
ideally
like
to
go
for
so
again,
if
they
tap
add
a
description
on
mobile.
That
panel
would
kind
of
slide
out
of
view
and
be
replaced
with
this
panel,
and
this
is
represented
in
the
prototype
as
well
and
and
I'll
actually
do
a
quick
walkthrough
of
that
in
a
separate
video
just
in
case
anybody
needs
a
refresher
on
that.
A
So
in
this
case
I've
got
the
back
link
here
at
the
top.
There
is
a
question
that
I
have
here
for
jeremy
as
to
whether
or
not
this
should
follow
the
same
pattern
as
the
edit
buttons
in
the
sidebar,
which
are
gray
links,
dark
gray,
links
versus
the
blue
links
that
we
have
defined
associated
with
links
in
storybook.
A
So
I'll
confirm
with
him
just
to
be
sure
for
the
chevron
I
put
in
the
name
of
the
chevron
and
the
size
as
well.
Please
again,
let
me
know
if
there's
anything
else
that
I
need
to
include
there,
I'm
not
even
sure,
if
name,
for
example,
chevron
lg
left
is
what
you're
looking
for,
if
you
or,
if
you
specifically
need
the
gl
dash
icon
or
whatever
the
the
component
name
is
so
please
again.
A
Let
me
know
that
too
and
I'll
be
happy
to
add
that
in
but
I'll
let
you
all
know
my
proposal
in
this
case,
for
the
con
title
is
that
it
be
that
dark
gray
just
so
that
it
helps
the
user
to
kind
of
have
a
bit
more
of
a
sense
that
this
is
sort
of
a
a
navigation
point
and
not
necessarily
just
a
link
within
the
text
and
hopefully
help
to
kind
of
articulate
a
bit
more
that
it's
it's
meant
to
be
for
navigating
through
an
experience
and
not
just
clicking
and
going
to
another
page,
even
though
I
suppose
that
kind
of
is
that
I
also
had
a
question
change
this
to
nbc.
A
I
would
love
for
when
they
go
into
that
edit
view,
if
a
title
has
already
been
added
that
it
show
convert
plan
objects,
for
example,
it
would
show
the
title
of
that
work
item
here
to
help
them
to
know
that
hey
when
you're
done,
you
can
go
back
even
if
you
don't
make
any
changes.
You
can
just
select
that
and
go
back
into
the
view
for
that
work
item.
A
If
they
have
not
yet
added
a
title,
then
perhaps
it
would
just
say,
return
to
work
item
or
you
know,
return
to
create
work
item
or
even
potentially
just
show
the
arrow.
But
if
that
can't
be
done
for
mbc
to
show
the
title
and
to
have
that
level
of
customization,
then
just
showing
the
arrow
is
fine
for
now,
and
we
can
continue
to
test
and
learn
with
that.
Once
we've
got
it
built
in
into
the
hands
of
users,
the
tabs
should
be
the
standard
tabs.
Ui
I
put
in
the
theme
and
the
style.
A
A
For
the
desktop,
it
should
be
just
kind
of
that
condensed
left
aligned
set
of
tabs
so
I'll
make
a
note
too
go
back
and
add
those
in
for
the
editor
itself.
This
is
something
I
want
to
confirm
with
michael
lay.
His
team
has
been
doing
a
lot
of
work
on
the
editors
and
there
is
a
little
bit
of
overlap
in
the
design
decisions
he's
been
making
versus
what
I've
been
making.
A
I
want
to
be
consistent
with
his
team
there,
because
I
think
they
have
made
a
bit
more
progress
than
than
we
have
in
terms
of
actually
editing
and
constructing
changes
in
this.
This
editor
piece,
so
I
just
want
to
verify
with
him
that
these
icons
work
or
if
he
has
any
existing
icons,
but
I'm
trying
to
do
a
condensed
approach
to
this,
and
perhaps
when
they
select
this
particular
icon
here
it
reveals
the
three
add
list
types,
like
add
checklist,
add
bullet
list.
Something
like
that.
A
This
reveals
the
input
I
believe
layout
type.
So
each
of
those
would
have
like
when
you
tap
them,
they
would
bring
up
a
little
tool
tip
menu
that
the
user
could
interact
with.
I'm
not
sure
if
that's
going
to
be
his
team
or
our
team
as
well
to
create
this.
So
that's
something
else
that
I
need
to
get
a
little
bit
of
understanding
on,
and
let
me
actually
add
that
note
into
in
addition
to
checking
with
him
on
the
icons
who
is
building
the
updates
to
this
editor.
A
So
that's
an
open
question
for
the
description
itself
fairly,
similar
to
the
description
that
we
currently
have.
I
don't
think
this
is
the
exact
font
I'm
using
just
our
style
guides,
mono
font,
but
whatever
the
typeface,
rather
is
that
we're
currently
using
for
that
editor
view,
that's
totally
fine
for
the
edit
mode
and,
of
course,
when
they
toggle
to
preview,
it
should
be
whatever
is
defined
either
with
their
styling
preferences
or
with
our
current
system
as
well,
and
then
I
went
ahead
and
put
in
some
details
there
as
well
for
the
save
button.
A
So
if
they
click
save,
it
would
take
them
back
to
this
view
where
they
could
continue
to
complete
updating
the
work
item.
If
they
are
in
the
process
of
creating
it,
they
would
see
that
create
button
and
cancel
button
set
here.
If
they
have
already
created
it,
but
they
have
simply
chosen
to
go
back
and
edit
it,
they
could
select.
A
The
description
in
the
created
work
item
view
and
return
to
that
overlay
screen
where
they
would
see
something
potential
like
this
and
they
could
just
choose
to
save
or
if
they
tap
on
the
title
up
here
at
the
top,
then
it
would
ideally
prompt
them
if
they
have
made
a
change
and
give
them
the
option
to
choose
to
save
or
not.
So
please,
let
me
know
too,
if
I
need
to
represent
that
in
my
screens,
and
let
me
put
a
question
here
just
to
check
with
you
all,
so
I
don't
forget
to
follow
up.
A
So
please,
let
me
know
about
that
as
well
and
I'll
be
happy
to
add
in
that
question
something
else
to
note.
So
once
I
have
created
my
title
and
I
have
actually
created
the
work
item
itself,
there
are
a
few
changes
that
happen
in
this
view,
and
some
of
them
again
might
not
be
nbc.
So
this
is
something
I'll
need
to
confirm
with
the
pms
about
the
first.
A
Is
that
one
it
exists
in
an
overlay,
so
in
that
case
they
would
have
this
close
button
where
they
could
just
close
out,
and
that
would
return
them
to
wherever
they
were
in
the
product.
This
overlay
should
not
just
happen
when
they
create.
It
should
also
happen
when
they
just
attempt
to
select
a
work
item
and
view
it.
A
Obviously,
at
the
top
here,
we've
got
the
work
item
id
in
place,
I'm
just
using
the
hashtag
for
now
to
represent
that,
but
I
I
don't
think
we've
completely
decided
just
yet
as
to
how
we're
going
to
identify
those,
but
I
did
include
the
overlay
icon,
close
name
and
size,
I'm
also
including
this
ellipsis.
This
may
not
be
nbc.
A
And
this,
in
my
opinion,
would
include
just
some
of
the
standard
actions
create
new
work
item,
close
work
item,
potentially
some
of
the
actions
that
we
have
related
to
that
item,
so
I'll
verify
with
the
pms
about
that.
Otherwise,
we
would
just
not
show
any
sort
of
menu
action
menu
for
managing
work
items
from
that
screen
or
really
from
any
created
work
item
screen.
A
Next,
we
have
and
again
ellipsis
information
is
here
the
status.
This
is
also.
This
badge
is
a
bit
of
a
new
component
in
that
it
is
just
kind
of
a
variation
of
our
existing
badge
component.
So
we
do
currently
have
badges
that
have
text
and
have
a
little
icon
in
them.
However,
the
icon,
I
believe,
is
only
aligned
to
the
left.
I
couldn't
see
a
way
to
align
it
to
the
right
using
storybook,
so
I
would
like
for
it
to
be
aligned
to
the
right
and
to
use
our
pencil
icon.
A
Let
me
make
a
note,
and
actually
maybe
I
have
it
here.
Let
me
just
see,
I
don't
think
I
do
add
in
closed
version.
A
A
The
title
again,
I
couldn't
find
a
label
set
of
pre-defined
styles,
which
I
was
kind
of
surprised
about.
Again.
I
might
be
missing
that
somewhere,
but
I
couldn't
find
it
in
storybook
that
defines
what
the
label
styling
needs
to
be,
or
a
name
associated
with
that.
So
please
again,
let
me
know
if
I'm
missing
anything
there,
I
tried
to
just
show
that
it
would
be
our
standard
typography,
the
font
weight
would
be
bold,
it
would
be
gray
900
and
actually
do.
I
have
that
noted
anywhere
else
here.
A
For
labels
for
status
next
is
the
show
full
description
link,
and
this
is
just
showing
some
notes
regarding
this
particular
piece
I
put
in
450
characters
so
once
the
user
has
put
in
a
lot
of
description
and
it
exceeds
450
characters,
I
would
love
for
it
to
truncate
and
have
show
full
description.
This
is
in
preparation
for
comments
to
be
introduced
eventually,
so
that
comments
don't
just
get
pushed
down
way
below
a
bunch
of
dialogue
in
the
description.
A
I
do
have
a
question
here
for
jeremy
as
well,
if
this
should
follow
the
same
pattern
as
the
edit
buttons
or
the
sidebar
links
for
this.
This
link
text
of
show
full
description
again.
I
think
the
dark
gray
is
appropriate
here,
but
I'll.
Let
you
all
know
if
that
needs
to
change,
and
I
think
that
is
all
for
that
screen
for
the
next
screen.
Here
really,
the
only
difference
that
I
haven't
covered
would
be
the
assignees,
and
in
that
case
I
put
in
the
avatar
information.
A
A
So
those
would
should
be
reflected
here
in
terms
of
success
or
danger
to
show
the
open
or
closed
colors
and
then
also,
of
course,
have
the
labels.
The
check
marks
should
be
the
same
that
we
currently
have
for
drop
downs,
the
done
link
in
this
case.
I
made
it
a
blue
because
I
believe
that's
how
we
have
it
for
our
sidebars,
but
I'm
going
to
check
with
jeremy
again
to
confirm
that
color
opportunity
and
whether
or
not
it
needs
to
be
one
or
the
other.
A
The
change
status
here
should
be
the
same
as
manage
assignees
down
here,
and
it
should
really
be
the
same
size
of
titles
as
the
other
elements
that
currently
have
drop
downs
and
then
the
assign
yourself
same
thing.
I
have
a
question
about
the
styling
of
this
with
jeremy
about
again
blue
versus
gray
text,
but
it
should
be
consistent
with
the
unassigned
option
that
we
currently
have
in
terms
of
styling
and
the
drop
down
for
new
assignees,
and
then
the
styling
for
the
search
and
the
search
component
itself
should
also
be
the
same
as
assignees.
A
So
no
changes
there.
The
only
difference
here
is
this
option.
When
you
have
applied
an
assignee,
I
went
with
the
styling
that
we
currently
have
in
this
drop
down
and
just
added
in
the
close
icon.
But
I
want
that
to
be
become
a
list
of
assignees
that
have
been
applied
and
they
can
just
select
to
remove
them
if
they
choose
to
kind
of
similar
to
how
labels
work.
So
that's
everything
at
a
quick
glance.