►
From YouTube: UX Experience Baseline, Q2 2019: Understanding dependencies as they relate to a larger scope
Description
Going over understanding dependencies as they related to a larger project scope or feature - https://gitlab.com/gitlab-org/gitlab-design/issues/449
A
I'm
Annabelle
and
I'm
one
of
the
product
designers
at
get
love
I'm
on
the
planned
stage,
which
is
the
stage
that
focuses
on
features
like
the
issue.
Tracker
portfolio
management
features,
integration
with
external
trackers,
markdown,
rendering
and
email
notifications
in
this
video
I'm
going
to
be
walking
through
my
assigned
job
to
be
done,
which
is
based
on
understanding
dependencies
within
a
git
lab
epic,
so
understanding
how
issues
and
sub
epochs
relate
to
any
given
parent
epic.
Just
to
give
you
a
breakdown
of
how
this
is
set
up,
my
official
job
to
be
done.
A
The
I
mean
it's
pretty
long,
so
I'm
not
going
to
read
the
whole
thing,
but
it
needs
to
be
in
a
certain
format.
So
when
creating
a
task
task,
see
within
a
larger
list
of
tasks
that
need
to
be
completed
to
deliver
a
feature,
I
want
to
identify
and
document
the
dependencies
for
task
C
so
that
I
can
prioritize
tasks.
The
appropriately
healthy
assignee
of
task
C,
understand
and
make
sure
they
know
where
their
work
falls
in
the
larger
scope
of
the
project
or
a
feature
for
each
stage.
A
I've
already
gotten
them
all
here
in
screenshots,
there
is
an
emotional
grade
and
that
can
be
it
can
be
positive,
neutral
or
negative
and
then,
at
the
very
end,
there's
a
grading
rubric
for
the
entire
flow
and
that's
a
through
F
kind
of
what
you'd
expect.
F
is
not
good,
so
I
think.
That's
all
you've
got
here
so
I'm,
just
gonna
jump
right
into
the
flow
I'm
going
to
use
an
epic
that
we
already
have
existing
on
get
lab
comm.
A
A
Okay
for
step,
one
I
want
to
view
my
epic
and
attach
to
issues
and
for
this
I'm
kind
of
going
to
be
using
the
persona
of
a
product
owner
or
a
project
manager.
So
for
my
step
one,
it
would
be
I
navigate
to
the
epic.
My
team
has
been
working
on.
Here's
the
epic
my
team
has
been
working
on.
The
emotional
grade
is
positive.
This
is
what
I
wanted
to
see.
I
see
all
the
issues
that
comprise
this
epic,
you
can
see
on
my
sidebar
metadata,
the
ancestors
where
I
can
see.
A
You
know
where
this
epic
lies
in
the
grander
scheme
of
things
and
I
see
who's
assigned
to
things.
What
the
milestones
are
for
these
issues
and
which
ones
are
closed.
I
also
really
like
the
fact
that
I
can
choose
the
order
here.
So
in
this
case
it
looks
like
new
issues
have
been
added
to
the
top
I
prefer
that
they
were
elsewhere,
so
I'm
going
to
move
them
below
the
already
scheduled
items,
so
that
I
can
prioritize
the
things
that
are
already
scheduled
and
look
into
figuring
out
where
these
are
going
to
fit
in
later.
A
So
emotional
grave
is
positive.
There
second
step
is
creating
a
new
issue.
I
have
my
team
has
decided
that
not
decided.
We
have
noticed
that
an
issue
has
come
up
and
we
need
to
add
it
as
a
part
of
this
epic.
So
I
would
typically
click
if
I
want
to
add
an
issue.
I
would
click
this
plus
link.
This
is
a
pattern
that
we
have
kind
of
all
over
get
lab.
You
can
add
new
items
from
this
button,
so
I
would
assume
that
I
could
do
the
same
here.
It
says
paste
issue,
link
and
I.
A
Don't
have
an
issue
link
because
I
haven't
created
the
issue
yet
so
the
emotional
grade
is
negative.
It's
a
little
frustrating,
so
I
I,
don't
really
know
where
to
go
from
here.
My
next
assumption
would
be
this
plus
button.
I've
created
issues
from
here
before,
but
I
can't
I,
don't
I'm,
assuming
it's
because
I'm
on
the
group
stage.
Well,
I
know
it's
because
it's
on
the
group
stage,
but
that's
not
immediately
obvious.
So
the
next
thing
I
would
try
to
do
is
go
to
issues,
and
that
was
another
negative,
emotional
and
grade.
A
If
you
couldn't
tell
so,
let's
see
if
I
can
create
an
issue
from
here
and
I
can
new
issue
in
get
lab
Enterprise
Edition,
so
this
was
set
up
luckily
for
me
to
already
be
on
Enterprise
Edition,
but
a
lot
of
the
time
I
work
in
Community
Edition.
So
this
would
be
an
added
step
if
I
wanted
to
add
community
edition.
I'd
have
to
do
that
and
then
click
new.
So
in
this
case
it
was
already
set
up
lucky
for
me.
So
I
will
click
that
new
issue
get
left,
Enterprise,
Edition
and
I'm.
A
Finally,
where
I
wanted
to
be
in
the
first
place,
I'm
in
Enterprise
Edition,
we
can
get
back
org
on
the
new
issue
form,
so
it
was
kind
of
negative
getting
here
and
now
my
emotional
grade
is
just
kind
of
neutral.
This
is
what
I
expected
to
see
when
I
got
to
the
new
issue.
Page
I
can
fill
out
my
issue
title
issues.
A
Tree
I
can
fill
out
my
description.
Assignee
milestone.
Labels
weigh
everything
that
had
come
to
expect
from
the
issue
form.
I'm
not
going
to
submit
this
because
this
issue
already
exists
so
pretend
that
I
did-
and
this
is
the
result-
here's
my
issue-
it's
got
everything
that
I
expected
to
see
so
again
neutral.
A
It's
not
blowing
me
away
with
any
unexpected
positive
surprises,
but
it's
good
so
now
I
want
to
attach
this
issue
to
my
epic,
which
is
what
I
wanted
to
do
in
the
first
place,
feel
free
to
ignore
this,
because
I've
been
messing
around
with
this
a
lot.
This
all
these
system
notes
multi
here
but
anyway,
going
to
add
this
to
my
epic
I
would
go
to
the
sidebar,
because
this
is
I
add
metadata,
there's
no
edit
button
here,
which
is
another
negative
emotional
grade.
This
is
what
I've
come
to
expect.
A
I
can
edit
anything
else
here
and
I
can
add
a
Sinese
I
can
add
milestones.
Everything
has
an
edit
button,
basically,
except
for
epic,
so
I
do
remember
that
I
had
to
paste
any
issue
link.
Unfortunately,
I
didn't
keep
the
tab
open,
because
I
didn't
realize
that
I
would
get
stuck
again
so
now,
I
need
to
go
back
and
search
for.
My
epic
I
picked
her
at
the
group
level.
Glad
these
breadcrumbs
are
here
so
now.
A
A
Ok
that
worked
emotional
grade
is
neutral
on
that,
not
because
I
think
it's
a
super
interaction,
but
it's
what
I
expected
because
I
finally
did
it
the
way
it
told
me
to
it's
right
at
the
top
kind
of
like
what
I
expected
too
I
wouldn't
want
it
to
be
at
the
bottom
in
case
it
got
lost.
So
here
it
is
just
like
the
issues
I
moved
earlier.
I
don't
want
this
to
be
at
the
top,
so
it's
not
scheduled
yet
and
I
don't
want
to
prioritize
it
until
we've.
A
You
know
gone
through
the
UX
and
made
sure
that
the
developers
are
aware
of
it
and
we
have
everything
sorted
out
with
a
milestone,
so
I'm
going
to
add
it
to
the
bottom
of
the
open
issues
for
now
and
then
I
can
check
back
later
and
and
do
some
more
stuff.
So
that's
good!
That's
that's
a
positive
again!
I
really
like
that.
I
can
drag
these
into
the
ordering
step.
A
Four
I
didn't
mention
step
two
and
three,
but
the
second
one
was
attaching
issued
epic
and
the
third
was
reordering
them,
which
I
just
did
so
step
four
establishing
a
hierarchy
and
dependencies.
If
I
go
back
to
my
issue,
option
I
can
see
now
that
the
epic
is
in
the
sidebar,
which
is
expected
still
no
edit
button.
A
That's
a
neutral
reaction
as
I
was
expecting
it
part
of
this
job
to
be
done,
was
understanding
dependencies
and
how
they
relate
to
each
other.
This
one's
a
little
tricky
because
we
don't
have
blocking
issues
in
it
or
anything
that
sort
of
says
this
needs
to
come
first
or
this
issue
can't
be
done
without
this
other
issue.
So,
as
a
workaround,
we
have
a
couple
of
things
to
do.
A
There's
the
ordering
I
just
put
things
in
this
could
signify
to
a
team
that
things
need
to
be
worked
on
in
this
exact
order
that
doesn't
really
work,
because
these
are
different
types
of
issues
like
this
is
UX
research.
It's
assigned
to
a
researcher.
It
doesn't
need
to
be
done
before
some
of
these
other
things,
but
we've
got
you
xers,
front-end
and
back-end
assigned
to
other
things.
So
there
is
that,
if
you
want
to
use
it
that
way,
another
sort
of
workaround
is
this
related
issues.
A
Widget,
you
can
add,
maybe
if
it's
blocked
by
maybe
if
this
is
a
front-end
issue
and
it's
blocked
by
the
backend
needing
to
be
implemented.
First,
you
could
add
the
back-end
issue
as
a
related
issue
and
you
would
know
they're
related,
but
they're,
not
necessarily
blocked
and
there's
no
way
to
enforce
the
ordering
here.
So
that's
something
that
be
changed
but
I
did
know.
This
wasn't
a
feature
available,
get
lab
and
let's
see
that's
kind
of
it
actually
for
the
job
to
be
done
here.
A
For
helping
me
assignee
understand
how
things
work
in
the
grander
scheme
of
things,
there's
there's
always
the
epic
page,
which
shows
exactly
he's
assigned
to
what
and
anyone
can
look
at
this.
It's
just
kind
of
hard
to
find,
which
is
the
biggest
reason
that
epics
in
general
have
a
not
great
emotional
score.
In
fact,
most
of
them
were
negative,
just
based
on
how
much
work
it
took
to
get
to
this
to
the
stage
and
how
difficult
they
are
to
find.
So
if
we
go
back
to
my
grading
rubric,
which
alcohol
over
here.
A
I
gave
this
entire
experience,
see
which
is
average.
The
workflow
needs
improvement,
but
user
can
still
finish
completing
the
task.
It
usually
takes
longer
to
complete
the
task
than
it
should
user
may
abandon
the
process
or
try
again
later
frustration
level
is
medium.
I
would
say
it
was
medium
to
high
in
some
cases,
task
completion
successful,
but
with
unnecessary
steps.
I
think
everyone
can
agree
there
that
there
were
quite
a
few
steps
to
this
to
attach
an
issue
and
steps
to
complete
task
or
average
complexity.
They
definitely
weren't
too
complex,
but
they
were.
A
They
were
just
numerous,
which
is
never
a
good
thing,
so
that
is
it
for
the
entire
experience
of
understanding
dependencies
within
a
feature
or
an
epoch
in
the
future.
We'll
we'll
add
some
recommendations
here
and
hopefully
schedule
some
issues
to
fix
these
things,
so
be
on
the
lookout
for
that.
Thanks
for
watching.