►
From YouTube: Work item and Plan PM design walkthrough
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
all
right,
this
is
holly
and
just
want
to
do
a
quick
walkthrough
of
sort
of
the
history
of
work
items
so
that,
hopefully,
the
team
will
be
able
to
kind
of
pick
up
where
I
left
off.
Gabe,
of
course,
is
still
a
great
resource
for
this
kind
of
information
as
well,
but
from
a
design
perspective
in
case
anyone
just
kind
of
needs
to
navigate
my
figma
files
or
kind
of
understand
where
to
find
things.
I
hope
that
this
will
be
helpful.
So
let
me
share
my
screen
really
quick.
A
A
I
don't
know
if
I
need
to
go
through
and
set
all
of
these
so
that
anyone
with
the
link
can
edit
and
actually,
I
guess
I
should
maybe
make
gabe
an
editor
on
some
of
these,
but
that
would
be
something
that
if
anyone
needs
me
at
any
point
to
hop
in
and
kind
of
open,
these
up
feel
free
to
ping
me
on
the
alumni
channel.
But
hopefully
someone
with
admin
privileges
can
go
in
and
manage
that
with
no
problems
all
right.
A
So
again,
there
are
a
handful
of
figma
files
that
are
going
to
be
relevant.
The
first
is
this
three
two,
four
eight
eight
nine
new
work
item
view
this
one
is
kind
of
the
larger
file
that
I've
been
using
since
the
beginning
of
work
items
and
a
little
bit
of
background
there.
If
you're
kind
of
new
to
this
project,
we
started
out
by
calling
these
collab
checks,
which
was
kind
of
a
tongue-in-cheek
internal
term,
that
we
were
using
to
refer
to
things
that
are
collaborative
objects
similar
to
issues
or
incidents
requirements.
A
Any
type
of
documentation
or
communication
objects
that
we
currently
have
in
gitlab,
or
look
to
have
in
the
future
in
gitlab.
So
we
were
calling
them
that
in
case
you
look
at
the
history
of
the
project
and
see
issues
that
have
that
kind
of
information
or
use
that
terminology.
A
It's
the
same
thing
there's
also
a
phrase
of
extensible
issues,
and
that
also
ties
into
this.
So
I'll
talk
about
that
in
a
few
moments
as
well,
but
in
this
first
kind
of
big
figma
file,
there
are
lots
of
pages
here
on
the
left.
I
wish
I
could
zoom
a
little
bit
more,
but
I'm
not
able
to
in
figma,
unfortunately
with
their
panels
so
cover.
Obviously,
this
other
views
is
just
sort
of
sort
of
me
doing
some
exploration
surrounding
possibilities
for
these
these
objects.
A
A
lot
of
these
are
a
bit
older,
so
it
may
or
may
not
still
be
relevant
by
the
time.
Someone
listens
to
this,
but
we
definitely
want
for
work
items
the
current
term
for
this
feature
to
be
mobile
friendly,
in
particular,
when
it
comes
to
issue
tracking
users
have
been
expressing
more
and
more
that
they
want
to
see
more
ability
to
use
these
experiences
in
a
mobile
environment.
A
There
was
a
thought
previously,
including
myself.
Having
had
this
that
users
don't
have
an
interest
in
using
gitlab
in
a
mobile
setting.
In
fact,
I
believe
after
doing
some
research
and
talking
with
users
and
evaluating
our
sus
information
and
looking
at
the
market,
I
think
that
there
is
a
great
interest
in
it.
However,
I
think
that
it
is
only
specifically
for
the
issue
tracking
or
work
item
tracking
process.
A
Primarily
our
competitors
have
apps
for
that,
and
they
seem
to
be
very
successful
with
some
users
even
expressing
that
they
prefer
to
use
the
mobile
app
because
of
the
simplicity,
so
we
definitely
wanted
to
start
with
mobile
first
responsive
design.
So
it
is
the
same
code
that
would
be
working
with
the
desktop.
A
So
that's
what
some
of
these
screens
are:
I'm
not
going
to
go
through
all
of
them
in
detail,
just
because
there's
there's
some
duplication
here
and
a
lot
of
these
are
kind
of
pieces
of
a
prototype,
but
a
couple
of
key
areas
of
discussion
are
surrounding
status.
How
status
would
be
presented
within
the
product?
We
explored
this
sort
of
hollow
button
approach,
because
I
have
found
that
users
would
often
click
on
the
status
option
like
if
you
go
to
one
of
our
issues.
A
Currently,
we've
got
this
status
up
here
in
the
top
left
and
it
looks
like
a
button
and
people
have
a
tendency
to
click
on
it.
Thinking
that
it
is
such
and
so
gabe
had
the.
What
I
think
is
really
good
ux
idea
of,
or
interaction
idea
of,
being
able
to
tap
on
that,
and
it
be
a
button
and
toggle
between
multiple
status
options.
A
Currently,
we
only
have
a
couple,
but
I
think
that
the
plan
in
the
future
is
to
expand
status
from
just
open
and
closed
and
promoted,
and
a
few
of
the
existing
items
that
we
have
to
even
more
custom
status
types
and
potentially,
I
would
imagine
custom
status
types
that
are
specific
to
the
type
of
object
that
we're
looking
at.
So
if
it's
an
incident
incident
might
have
its
own
status
options
versus
a
task
which
might
have
separate
options
that
are
relevant
to
that
particular
type
of
object.
A
A
This
is
just
kind
of
showing
some
possibilities
for
expanding,
how
it
might
look
in
the
mobile
setting
with
labels
and
status
and
assignees
and
a
bit
more
information.
Something
else
that
I
really
wanted
to
see
happen
with.
This
was
truncating
the
description
because
in
previous
testing
I
had
found
that
people
ranked
description
as
being
very
high
and
valuable,
but
then
they
would
skip
past
it
when
trying
to
assess
what
the
issue
was
about,
because
often
our
descriptions
are
very
lengthy.
A
So
I
think
there
is
opportunity
there
for
us
to
try
to
find
ways
to
encourage
people
to
write
more
meaningful
and
more
succinct
descriptions,
so
there's
opportunity
probably
to
do
a
little
more
research
there.
But
the
thought
is
that,
after
a
certain
amount
of
characters,
it
would
truncate
and
show
this
show
full
description
as
an
optional
toggle
and
then
anything
that
exists
below
that
any
other
sort
of
like
related
items
or
the
filters
for
drop
downs,
filtering
dropdowns,
I
should
say,
would
show
underneath
that
section,
so
nothing
officially
decided
on.
A
I
did
a
little
bit
of
quick
internal
testing
by
the
way
on
these,
and
I
believe
that
this
middle
one
was
the
one
that
feared
the
best
so
having
the
labels
left,
aligned
and
kind
of
grouped
together.
These
are
missing
the
little
x.
We
do
have
that
now,
so
this
is
again
now,
unfortunately,
a
bit
outdated
of
a
design
but
and
I'll
go
through
how
the
interactions
work
for
some
of
these
in
a
moment.
A
Actually,
let
me
skip
over
so
I'll
just
quickly
touch
on
the
pages
here
on
the
left
and
then
come
back
to
some
of
the
more
details.
So
that's
what
the
first
one
is.
It's
just
sort
of
exploring
some
of
the
different
possibilities
similar
to
that
there
is
on
the
left
here
and
let
me
just
kind
of
group
some
of
these
together.
A
A
The
desktop
view
having
some
of
the
plans
that
we
had
discussed,
such
as
having
description
and
title
left
aligned
on
the
page
and
then
the
discussion
or
comments
on
the
right
so
doing
kind
of
a
split
screen
approach.
I
also
wanted
for
this
line
that
divides
them
to
be
draggable,
so
the
user
could
widen
or
reduce
the
width
of
those
sections
depending
on
which
part
they
wanted
to
see
a
little
bit
more
or
less
of.
A
Sticky,
titles
help.
This
is
actually
a
merge
request.
But
sticky
titles
help
to
give
us
that
title
a
little
bit
of
clarity,
but
they
don't
necessarily
give
us
the
details
that
we
need-
and
this
is
unfortunately
a
very
short
one.
So
not
a
great
example,
but
but
the
goal
was
to
reduce
the
back
and
forth
that
the
user
has
to
do
the
up
and
down
scrolling
associated
with
looking
at
really
long
issues
to
try
to
gain
context
on
how
they
need
to
respond.
A
So
putting
that
side
by
side
hopefully
would
help
with
that.
There
was
a
lot
of
exploration
done
in
this
particular
page
as
well.
This
original
workspace
page
surrounding
where
to
put
the
widgets
and
so
by
widgets.
We
do
actually
have-
and
let
me
go
to
this
real
quick.
This
would
be
a
part
of
nbc
3.
A
Documentation
surrounding
the
work
item
fields,
so
the
widgets
that
we
are
considering
for
work
items
long
term
are
labels
being
able
to
attach
it
to
a
milestone,
setting
a
due
date,
specifying
time
tracking
and
weight
for
sort
of,
managing
and
estimating
effort,
attachments
and
designs.
That's
the
design
management
portion
iteration,
so
all
of
these
areas
and
then,
additionally,
having
the
global
actions,
those
are
currently
displayed.
Well,
this
is
an
epic,
but
for
an
issue
go
to
one
of
these
really
quick
and
again.
A
This
is
known
for
someone
who
isn't
new
to
the
project,
but
for
someone
who
might
be
new,
I
just
want
to
cover
it
real,
quick.
This
is
currently
in
this
little
ellipsis
menu
up
here
on
the
right,
which
is
what
we
are
using
for
sort
of
global
object,
actions,
work,
item
actions
or,
in
this
particular
case,
global
issue,
actions,
things
that
you
can
do
with
the
issue
as
a
whole.
There
is
a
delete
option
too,
but
that's
only
available
for
admins,
so
it
may
not
be
visible.
A
So
that's
what
is
referred
to
by
these
global
actions
here
the
elements
in
that
ellipsis
menu.
Then
we
have
personal
actions
so
being
able
to
toggle
to
do's
being
able
to
copy
the
reference
and
the
email
address.
That
is
this
information
up
here
at
the
top,
as
well
as
these
options
down
here
on
the
bottom
right
corner.
Where
do
we
put
that
information?
A
Let
me
go
back,
keep
going
to
this
epic
here
at
the
top
of
an
existing
issue
and
even
on
the
side
to
sort
of
understand
how
users
are
valuing
those
details
and
the
goal
of
that
is
to
determine
what
needs
to
be
more
prominent
versus
what
can
maybe
be
considered
a
bit
of
a
secondary
option
and
maybe
put
behind
a
menu.
A
A
So
those
are
what
we
mean
by
widgets
everything
that
is
listed
in
this
6287
epic,
the
mvc3
parody
of
work,
item
fields.
Currently
these
things
may
change.
This
is
also
again,
obviously
not
nbc
one,
so
not
sure.
Yet
what
the
timeline
looks
like
for
nbc
3,
but
it
is
worth
just
kind
of
keeping
that
in
mind.
A
There
is
also
separately
in
mvc2.
Nbc2
is
focused
more
on
the
hierarchical
relationships,
parent
child
relationships
and
sibling
relationships
between
work
items
and
that
is
under
product
planning.
So
alexis
would
be
a
great
contact
to
get
deeper
information
about
that.
So
going
back
to
the
figma
file,
that's
just
important
to
remember
that
a
lot
of
the
exploration
surrounding
the
long-term
vision
for
work
items
is
in
this
particular
section,
and
I'm
going
to
actually
update
my
layer
here.
A
A
But
just
know
that
things
probably
have
changed
since
this
work
was
done.
This
is
a
bit
older,
but
there
are
still
some
concepts
in
here
that
are
valuable.
I
think,
to
be
able
to
pull
up
to
for
conversation
purposes
such
as
the
side
by
side
of
description
and
dialogue,
placement
of
those
widgets,
so
I
explored
putting
them
all
the
way
across
the
top.
Personally,
this
is
the
one
that
I
like.
A
These
items
here
at
the
top
that
are
sort
of
global
properties
versus
the
issue,
properties
and
and
people
were
concerned
that
there
was
some
confusion
that
could
happen
there,
so
I
also
explored
putting
them
over
here
on
the
left
under
the
title
and
kind
of
tinkered
with
placement
of
those
and
moving
them
above
the
title
rearranging
and
hiding
and
showing
relevant
information.
A
A
Let
me
see
here
if
I've
got
this,
there
is
an
issue
for
it
and
you
can
see
those
icons
in
that
issue
and
we
will
of
course
need
to
create
new
icons
over
time.
I
think
it's
maybe
issue
type
icon
to
issues,
and
that
would
be
three
two,
two,
eight
eight
eight.
So
that's
also
just
a
good
one
to
kind
of
refer
to.
I
don't
know
that
this
is
the
exact
one
it
might
be
under
this
epic
of
introduce
visual
indicator
of
issue
type
yeah.
This
is
probably
it
so.
A
We've
got
a
handful
of
issue
type
icons,
and
I'm
actually
going
to
include
this
in
my
document
as
well,
just
in
case
anybody
needs
to
refer
to
those
or
add
those
in
in
the
future.
So
that's
something
else
that
would
need
to
be
probably
displayed
here
so
good
to
just
have
that
as
part
of
the
exploration,
the
original
mobile
exploration.
A
This
is
where
I
had
conducted
some
competitor
analysis,
and
there
is
a
recording
of
this
on
get
lab
unfiltered.
I
believe
in
one
of
our
it's
maybe
design,
review
playlist.
So
that's
worth
checking
out.
That
was
where
I
reviewed
a
handful
of
competitors
and
looked
at
both
mobile
apps
and,
I
believe,
also
a
responsive
product
because
most
of
our
competitors,
as
soon
as
you
try
to
access
their
product
on
a
mobile
device,
you're
prompted
to
download
their
mobile
app.
That
was
only
an
exception,
for
I
think
one
or
two
of
the.
A
I
believe
five
that
I
reviewed.
So
there
are
a
lot
of
notes
here
about
the
existing
heuristic
evaluation
of
looking
over
our
current
process
and
the
opportunities
there
there's
also
information
about
what
I
discovered
from
my
evaluation
of
the
competitor
products.
So
this
is
a
good
to
just
review
and
I'll
also
put
a
note
here,
competitor
eval
old
exploration.
A
I
feel
like
there's
not
much
in
here.
Actually,
yeah
there's
not
so
this
was
really
just
showing
how
this
area
here
might
scroll,
and
I
had
a
concern
with
using
tabs
for
showing
comments
designs
dependencies
as
kind
of
a
sidebar
option
with
having
multiple
scrolling,
so
that
was
just
kind
of
playing
with
that.
There's
not
much
in
that
particular
one
notes
and
research
just
goes
into
some
of
the
actual
notes
and
research
that
we
have
acquired
over
time,
including
a
bit
more
of
the
insights
found
when
doing
the
competitor
analysis,
mobile
prototype
annotation.
A
So
this
was
something
I
had
created
for
the
engineers
and
I
would
like
to
maybe
hide
some
of
these
comments
for
now.
But
I'll
come
back
to
that
in
a
bit
close
this.
So
we've
got
all
these
little
bubbles
here
from
the
comments,
unfortunately,
but
this
is
just
where
I
had
gone
through
and
annotated
and
documented
the
specifics
of
the
interactions
and
components
associated
with
the
new
fields.
So
again,
this
is
probably
going
to
be.
A
Changing,
may
have
already
changed
even
very
recently,
so
talking
with
donald
and
gabe
about
any
tweaks
would
be
good
as
well
as
this
editor
bar.
This
is
again
something
that
michael
lay's
team
is
working
on,
so
they
would
be,
as
I
even
noted
here,
they
would
be
a
good
group
to
to
chat
with
about
changes
that
are
happening
there
all
right.
A
So
there
are
a
handful
of
prototype
notes
here
or
prototype
pages,
and
this
is
primarily
where
I
created
just
prototypes
for
showing
to
the
team
possibilities
with
the
product,
and
then
I
also
created
a
separate
document.
I
believe
that
has
the
testing
prototype
that
I
tested
with
users
and
shared
in
dovetail,
so
we
have
the
actually.
Let
me
go
back
really
quick
to
original
workspace.
A
There
were
some
things
that
I
was
exploring
in
terms
of
how
work
items
might
surface
in
the
product.
I
believe
strongly
that
there
is
value
in
showing
work
items
in
three
different
ways:
one
as
a
modal
one
as
a
side
panel
and
one
as
an
actual
page
itself.
A
So
I
showed
an
example
of
that
sort
of
mobile
or
modal
format.
Other
people
liked
having
the
side
panel.
That
way,
you
don't
lose
the
context
of
where
you
are
currently.
So,
if
you
click
to
open
a
work
item
from
let's
say
to
do's,
and
it
opens
it
as
a
side
panel,
then
you
can
still
see
that
you
do's
over
here
on
the
left.
A
Let
me
find
a
better
example
here
being
able
to
just
see
the
work
item
as
its
own
page,
and
some
people
expressed
wanting
to
have
this,
because
it's
easier
for
sharing
it's
easier
to
sort
of
feel
like
you
have
your
your
clear
context,
but
that
is
something
that
would
again
be
good
to
to
collect
feedback
on
once.
We've
gotten
a
little
further
down
the
line
with
this.
A
Also,
there
were
comments
that
some
people
don't
like
the
side-by-side
approach
and
that
some
folks
would
prefer
to
have
the
option
to
have
everything
in
a
single
line.
So
I
believe
that
that
was.
Let
me
see
if
that
was
tested
here
or
if
that
was
maybe
in
the
page
view
so
yeah.
So
that's
in
desktop
prototype.
As
a
page,
I
was
sort
of
exploring
what
it
might
look
like
to
offer
that
as
an
alternative
as
well,
but
going
back
to
this
the
original
workspace.
A
My
thought
is
that
you
could
toggle
between
these
views
open
a
work
item
in
maybe
a
modal
and
have
an
option
to
either
go
to
the
actual
page
itself.
With
that
work
item
that
work
items
detail
view
or
to
be
able
to
toggle
to
a
side
panel
and
then
separately
from
the
side
panel
to
switch
to
a
modal
or
go
to
the
page,
and
let
me
see
if
I
can
figure
out
where
I
put.
A
I
don't
actually
see
that
example
in
this
page,
so
I'm
sure
that
I'll
come
across
it
in
this
video
and
I'll
point
it
out
then,
but
there
were
basically
just
three
icons
that
were
being
shown
and
actually
it
may
have
even
been
maybe
even
been
instead
of
icons.
The
last
iteration
might
have
just
been
in
that
ellipsis
menu
up
here
in
the
top
right.
So
let
me
just
zoom
in
so
this
actions
menu.
At
some
point.
A
Actually
we
had
explored
having
an
option
to
switch
to
side
panel
or
modal,
because
if
you're
on
the
page,
then
the
system
would
have
to
examine
where
you
would
come
from
to
show
context
for
the
additional
page.
So
the
page
view
I
don't
think
had
that
toggle
option,
but
modal
and
side
panel
had
those
those
abilities
to
toggle.
So
I
explored
using
icons
and
then
separately
also
explored
having
those
items
in
a
menu
all
right
going
back
to
this
page
view
of
the
prototype
itself.
A
A
It
seems
like
it
would
just
be
css,
but
that
would
be
a
good
question
for
the
efes
to
expand
on
so
having
a
title
clicking
on
the
title,
and
this
is
just
kind
of
showing
how
it
might
look
populated,
type
and
signees
have
populated.
In
recent
weeks.
I
have
considered
dropping
these
icons,
they're
kind
of
visually
heavy,
and
I
don't
know
that
they're
really
adding
that
much
value
since
we've
got
text
here
that
clarifies
what
the
user
is
able
to
do.
A
But
let's
say
we
go
ahead
and
create
now
status
appears.
We
can
add
in
a
description,
and
this
brings
up
the
description
box.
This
editor
has
changed
to
something
a
bit
more
recent,
but
just
kind
of
showing
the
history
there
so
go
back
to
work
item
view
so
desktop
prototype
as
a
page
is
that
desktop
prototype
is
a
mobile
or
modal
is
all
the
same
information
just
exploring
it
in
a
modal
setting
mobile
prototype
as
a
page
same
thing,
just
walks
walks
us
through
the
experience
in
a
mobile
setting.
A
So
create
work
item
we
can.
I
am
showing
here
the
breadcrumbs.
This
is
also
changed.
Now
that
we
have
reverted
to
tasks.
We
are
not
going
to
have
the
breadcrumbs,
and
I
believe
that
we
still
need
to
probably
revisit
what
this
looks
like
on
mobile.
Now
that
we
have
converted
to
tasks
this.
This
was
all
back
when
we
were
still
talking
about
work.
Items
is
kind
of
their
own,
just
sort
of
standalone
thing
and
not
necessarily
associating
them
with
a
specific
type.
At
that
point,
so
adding
a
title
brings
up
this
editor.
A
And
then
be
able
to
create
and
a
lot
of
this
we
were
attempting
to
have
it
in
line
to
reduce
the
clicks
as
much
as
possible,
but
still
make
sure
that
it's
clear
one
of
the
existing
questions,
I
believe,
that's
still
out
there.
It
might
have
been
resolved
on
michael
lee's.
Team,
though,
is
where
to
place
the
call
to
action
when
editing
in
this
mobile
settings.
Let
me
go
back,
add
a
title,
so
here
we've
got
our
editor
and
we've
actually
expanded
to
include.
A
Description
so
when
we've
got
these
icons
here,
where
do
we
place
this
call
to
action?
I
believe
michael's
team
had
explored
putting
it
in
the
top
right,
but
I
think
maybe
they
have
gone
back
to
this.
The
reason
that
I
had
placed
it
here
in
the
first
place
was
easier
access
when
you're
reaching
by
the
thumb,
but
obviously
this
is
responsive,
web
and
not
native
mobile.
So
we
had
to
consider
how
this
would
surface
in
the
ui
in
a
desktop
setting.
A
A
If
we
go
with
a
modal
approach,
which
is
what
we
are
starting
with
for
nbc
using
tasks,
so
it's
similar,
except
that
the
chrome
so
to
speak,
of
the
the
product,
the
purple
bar
here
at
the
top,
with
the
icons
and
the
access
to
the
admin
menu,
and
all
of
that
is
gone,
and
we
only
have
sort
of
a
sliding
panel
that
overlays
the
page
again.
A
This
is
what
I
was
looking
for
before
this
is
exploring
how
to
show
work
items
in
those
various
modal
versus
side
panel
versus
page
settings.
So
if
I
click
on
this,
like
I'm
opening
this
work
item
from
a
to-do
list,
I
can
immediately
see
it
in
this
modal.
A
But
if
I
think
you
know
what
I'd
really
kind
of
rather
be
able
to
see
that
list
behind
the
modal
and
be
able
to
see
the
details
of
this
as
well,
then
I
could
click
on
this
ellipsis
and
switch
to
a
side
panel
view
or
open
as
a
full
screen.
So
if
I
switch
to
side
panel
view
now,
the
work
item
is
opened
over
here
on
the
right
and
we
have
the
content
here
on
the
left
and
if
I
think
still,
you
know
what
I
actually
want
to
just
focus
on
this
work
item
alone.
A
I
don't
want
to
see
it
necessarily.
In
this
context,
I
can
choose
to
either
switch
back
to
a
modal
view
or
open
as
a
full
screen
which
goes
to
this
sort
of
detail.
View
page
of
the
work
item.
I
still
feel
strongly
that
this
is
a
good
approach
to
provide
users
options
for
how
they
want
to
consume
that
content.
So
that's
what
this
prototype
three
both
is
showing
how
to
open
or
access
this.
A
This
work
item
in
those
various
settings
all
right,
next
figma
file,
so
that
first
figure
file
new
work
item
view
got
very,
very
big
and
we
ended
up
with
several
issues
in
epics
related
to
work
items
that
were
open
over
time.
So
I
ended
up
creating
a
new
document.
New
figma
file,
434106,
which
is
the
design
of
the
issue,
detail
view
with
all
the
related
components
and
objects,
and
that
is
what
this
particular
element
is
about.
A
So
I
did
go
through
and
kind
of
outlined
and
annotated
some
of
the
exploration
surrounding
these
and
made
notes
about
each
of
those.
So
this
would
be
good
to
just
go
back
and
refer
to
if
you
need
to
dig
a
little
deeper
into
that
exploration
and
then
there's
also
the
workspace
which
has
some
additional
exploration,
but
I
think
it's
probably
just
iterating
further
on
the
work
that
we
had
done
previously.
So
I
don't
know
that
there's
going
to
be
a
lot
new
there.
A
So
that's
something
else
that
was
talked
about,
but
I
I
don't
know
that
anything
will
come
from
that
anytime
soon
and
that's
probably
kind
of
a
nice
to
have
for
future
iterations
next,
so
moving
more
into
the
evolution
of
work
items
as
a
task,
so
we
decided,
after
a
period
of
time
that
the
starting
point
nbc
for
work
items
would
be
that
work
items
would
surface
as
a
task.
A
This
is
something
that
users
have
been
asking
for
for
a
very
long
time,
so
it's
definitely
a
big
win
for
users,
because
they
wanted
the
ability
to
break
down
issues
into
smaller
things,
primarily
so
that
they
could
assign
work
to
specific
people
and
be
able
to
have
those
people
estimate
on
that
work
at
a
more
granular
level
than
issues
and
they've
been
using
epics
as
sort
of
the
issue
and
then
issues
as
sort
of
the
tasks
as
sort
of
a
placeholder
solution.
That's
at
least
one
of
the
ways
people
have
been
doing
it.
A
A
So
we
decided
to
offer
that
as
sort
of
the
first
iteration
of
work
items,
this
task
concept
and
the
thought
is
that
tasks
will
be
very
simple.
We
need
a
way,
first
of
all,
to
create
a
task,
and
so
the
the
idea
there
is
that
being
able
to
create
a
task,
and
this
would
be
epic
7110
again,
here's
the
figma
file
for
it.
We've
got
prototypes
for
desktop
and
mobile
as
well
as
sort
of
a
general
workspace
for
these.
A
A
So
some
of
the
exploration
surrounding
that
was
here
is
the
initial
hover
state,
or
how
can
we
show
that
initial
hover
state
and
then
also
again,
how
does
this
surface
in
a
mobile
setting,
because
we
don't
obviously
have
mobile
or
have
hovers
in
mobile,
so
this
document
under
workspace
in
the
7110
epic
file,
this
particular
frame
shows
some
early
exploration
for
how
that
might
surface.
A
This
is
just
the
default
state
of
a
checklist
item.
I
had
some
feedback
that
people
struggle
a
little
bit
with
the
placeholder
content.
So,
just
please
try
to
imagine
that
these
are
just
lists
of
things
that
team
members
need
to
do
for
a
project.
I
think
I
did
actually
update
it
a
bit
later
to
include
some
more
actual
data
yeah,
so
it's
not
on
the
screen.
I'll
show
it
in
a
minute,
but
here
I'm
just
focusing
primarily
on
interactions
so
option.
A
One
was
hover
over
one
of
these
checklist
items
and
a
button
appears
pushing
the
content
to
the
right.
The
good
thing
about
this
is
that
it
would
be
very
easy
to
find
very
discoverable.
A
The
downside
is
that
it
would
be
probably
a
bit
annoying
because
it
shifts
the
content
around,
but
I
just
wanted
to
go
ahead
and
get
the
idea
out
of
my
head
and
see
what
it
looks
like.
So
I
I
noted
pros
and
cons
with
each
of
these
approaches
from
my
perspective
and
and
got
a
lot
of
internal
feedback
as
well.
That
was
really
helpful
on
these.
A
The
next
was
similar,
except
that
this
make
task
option
would
appear
to
the
right
of
the
content.
The
question
then
was:
where
does
it
show
if
the
content
is
really
long
versus?
If
it's
really
short
so
in
this
case,
this
content
is
really
long,
does
make
tasks
still
stay
here?
A
Where
did
the
button
go
type
of
feel
so
pros
and
cons
there
as
well
and
and
tried
to
note
those
as
I
went
next
was
showing
just
an
icon
and
when
you
hover
over
the
icon,
specifically,
you
get
the
option
to
convert
to
task.
A
This
was
the
one
that
I
had
recommended
initially,
which
was
showing
an
ellipsis
menu.
My
thought
was
that
this
is
more
scalable.
We
can
add
items
to
it
as
we
need
to
in
the
future
if
we
need
to
be
able
to
do
more
things
with
these
checklist
items
and
going
with
a
pop-up.
A
This
is
a
variation
of
what
we
ended
up
going
with,
but
it's
a
bit
more
like
this
one,
the
last
one,
the
last
one
was:
why
not
put
the
ellipsis
menu
to
the
left,
where
its
placement
is
always
consistent,
might
be
a
little
less
findable,
because,
typically,
these
menu
items
tend
to
go
on
the
right
side
of
the
content,
but
putting
it
on
the
left
would
ensure
that
it
would
always
be
in
the
same
place.
A
It
would
be
out
of
the
way
it
wouldn't
cause
disruption,
necessarily
for
the
user,
as
they
read
through
this
content,
and
that's
where
we
ended
up
going
this
icon
here
to
the
left
of
that,
I
included
just
to
show,
drag
and
drop,
because
that
is
also
something
else
that
we
want
to
offer,
and
there
is
an
issue
for
that
as
well
and
where
you
know,
might
that
be
placed
when
because
currently
drag
and
drop
lives
on
the
left
side
of
the
content
like
this,
how
might
it
look
and
be
related
to
the
ellipsis
menu
in
this
context?
A
So
that
was
the
exploration
there
also
explored
what
this
information
might
look
like
in
a
markdown
setting
and
had
some
questions
about
that.
The
engineers
have
expanded
on
possibilities
for
this,
including
using
like
a
plus,
to
show
more
detail
for
the
work
item.
Once
it's
been
converted
and
there's
some
issues
that
still
have
some
ongoing
discussion
surrounding
those,
so
it
would
be
good
to
check
with
maybe
gabe
and
donald
and
see
what
what
the
latest
is
on
that
this
is
showing
once
the
item
has
been
converted.
A
So
here
we
have
just
a
standard
link
checklist
item
and
then
here
we
have
a
converted
checklist
item.
This
was
early
iteration
and
it's
changed
since
then,
but
here
we
were
just
showing
that
it's
a
link
when
you
click
it.
It
would
open
the
work
item
potentially
in
a
modal
or
side
panel.
Modal
is
where
we
ended
up
landing
on
that
and
then
sort
of
a
green
icon
to
show
the
status
that
green
icon
is
not
final.
A
A
Maybe
you
separately
converted
something
to
an
epic,
maybe
you've
converted
something
to
a
requirement
we're
using
this
little
badge
to
show
what
that
work
item
type
is
once
we
have
those
again
out
of
the
gate,
we're
only
going
to
have
task
as
a
work
item,
so
that
would
be
the
only
work
item
that
would
show
here.
However,
if
someone
were
to
link
an
epic
here,
there
could
be
a
question
of
whether
or
not
we
need
to
show
a
badge
associated
with
that,
as
well
as
the
status,
which,
again
is
what
that
green
represents.
A
Something
else
to
note
is
that
for
mvc
for
tasks,
I
believe
those
that
are
on
the
free
plan.
These
work
items
would
populate
as
just
this
might
show
it
a
little
bit
better.
A
A
And
kind
of
show
what
the
current
nbc
one
proposal
is,
at
least
at
the
time
of
this
recording.
So
if
I
hover
over
one
of
these
checklist
items,
currently
they're
just
plain
old
markdown
checklist,
I
get
my
ellipsis
menu
to
the
left,
drag
and
drop
is
not
yet
part
of
the
plan.
So
that's
why
there's
no
drag
and
drop
icon
here.
A
Click
on
it
and
I
get
this
convert
to
work
item.
That
was
the
verbiage.
We
ended
up
going
with
for
this
initially,
and
this
is
using
the
popover
component
clicking
that
launches
this
new
work
item
modal
and
we
have
a
title
which
is
inline
editable,
so
I
could
theoretically
just
click
in
here
and
start
typing
and
change
it.
We
also
have
the
ability
to
change
the
task
but
or
type
rather,
but
it
would
default
to
task.
We
may
not
have
the
drop
down
initially.
A
If
we
only
have
tasks
that
might
be
just
a
read
only
and
then
that
could
expand
into
a
drop
down
potentially
in
the
future,
as
we
have
more
options.
Assignees
and
wait
are
also
not
part
of
nbc.
They
would
be
in,
I
believe,
but
just
showing
how
it
might
look
to
have
these
things
weight
in
particular.
I
believe
I've
got
this
represented
as
a
drop
down
here,
but
I
think
we
had
decided
to
change
that
to
an
input
field,
so
that
could
change.
A
Assignees
is
just
both
of
these
are
really
using
the
current
functionality.
That's
found
in
the
right
sidebar
for
these
products.
Well,
assignee
says
white
is
is
not
so
that
might
change
to
an
input
field,
but
weight
in
particular
is
very
important
to
users.
A
Creating
the
task
then
changes
the
visual
and
functional
aspects
of
the
checklist
item
here
in
the
description
and
clicking
on
it
again,
I
don't
know
if
I've
got
an
example
of
this
yeah.
It
gives
us
this
ellipsis
menu
with
the
option
potentially
to
delete
or
any
other
actions
that
might
be
related
to
that
work
item,
and
then
we
can
also
again
go
through
and
change
status
and
weight.
I
think
we
probably
do
need
to
add
in
type
here.
A
I
think
that
we
could
probably
pull
together
what
that
final
experience
might
need
to
look
like
in
a
mobile
setting,
but
that
would
again
be
something
worth
talking
with
the
engineers
about
and
and
gabe
as
well.
So
hopefully
that
gives
a
bit
of
an
overview
of
this
project
as
a
whole,
certainly
of
the
figma
files.
There
is
in
whimsical,
and
I
included
this
link.
A
This
was
also
another
way
that
I
saw
that
potentially
surfacing
in
the
product
was
maybe
having
sort
of
a
list
of
widgets
on
the
side,
with
a
kind
of
an
overall
layout
and
users
could
just
kind
of
drag
and
drop
in
the
widgets
that
they
wanted.
For
that
particular
the
term
we
were
using
at
the
time
was
issuable,
but
you
could
substitute
work
item
at
this
point
as
that
is
you
know
what
the
long-term
view
would
be
and
a
little
more
exploration
here,
but
we
do
have
you
can
see
here.
A
I've
got
quite
a
lot
of
bookmarks
related
to
issues
and
work
items,
and
we
do
have
this
extensible
issues.
A
There
is
an
issue
for
this.
This
is
noted
in
my
document,
my
google
doc
and
then
there's
also
separately.
A
An
epic
this
epic,
probably
has
most
of
the
information
for
the
long-term
vision
about
what
extensible
issues
are
and,
and
it
might
be
valuable
to
go
in
and
change
this
to
extensible
work
items
just
to
try
to
ensure
that
there's
a
bit
more
clarity
that
these
things
would
be
tied
together
in
the
long
run.
A
So
I've
got
my
google
doc
here,
where
I
have
attempted
to
outline
the
most
relevant
items
for
work
items,
including
sort
of
the
older
work
item,
issues
and
epics,
the
sort
of
newer
tasks
approach
and
what
the
visions
are
for
that
I
tried
to
go
through
and
also
update
the
issues
and
ethics
with
images
that,
hopefully,
will
add
some
clarity
so
that
the
engineers
can
continue
on
in
terms
of
the
design
vision
provided
a
next
overview
explanation,
as
well
as
links
to
relevant
figma
files
and
whimsical
and
things
like
that
also
covered
milestones
and
iterations,
and
then
added
in
some
additional
relevant
links,
including
my
research
issues.
A
I
went
through
and
unassigned
myself
to
everything
so
that,
hopefully
folks
can
kind
of
pick
that
up
if
they
choose
to
moving
forward
or
close
those
items,
if
they
don't
feel
that
there's
value
in
them
milestones
and
iterations,
though
we
have
recently
done
some
ux
scorecard
work
on
those
and
got
some
really
good
feedback
from
the
folks
who
did
those
walkthroughs
as
to
how
we
can
improve
and
created
epics
and
issues
for
improvements
surrounding
those
items.
So
those
are
also
listed
in
this
document
as
sort
of
a
point
of
reference.