►
From YouTube: Navigation exploration in milestone 15.2
Description
Sharing navigation solution ideas with the foundations group for feedback
Source issue: https://gitlab.com/gitlab-org/gitlab/-/issues/365403
A
A
I
in
some
ways
I
kind
of
feel
like
I'm,
showing
off
an
idea
of
like
what
our
future
house
could
look
like,
and
if
you
want
to
live
here
too,
which
we
all
do,
I'm
sure
you
have
opinions
on
it
and
I'd
love
to
hear
those
good,
bad
or
otherwise.
So
I
have
a
few
questions,
just
as
like
prompts
to
help
you
think
through,
as
I'm
talking
through
each
idea
what
maybe
comes
to
mind.
So
I
think
something
stands
out
to
you
surprises
you
or
something
you're
curious
about.
A
A
B
C
A
A
Okay,
so
one
of
the
things
that
we
did,
jeremy
and
nick
as
well
since
you
weren't
there
for
some
of
those
meetings
was
we
explored
some
of
the
recurring
themes
that
we're
seeing
either
through
sus
or
through
different
verbatims
and
user
research
kind
of
aggregating,
the
things
that
we've
seen
and
heard
over
the
years
and
the
way
that
we've
highlighted
what
stuck
out
to
us,
the
most
are
three
things
we
are
noticing
users
feel
overwhelmed.
So
we
want
to
address
that.
We
want
to
address
how
users
orient
themselves
across
the
platform.
A
So
that's
moving
from
groups
to
projects
or
elsewhere
into
the
product,
and
then
I
even
think
there's
a
meaningful
way
that
we
can
help
users
pick
up
where
they've
left
off,
so
that's
jumping
back
into
their
pipelines.
They've
kicked
off.
Merge
requests
that
they're
doing
reviews
on
so
on
so
forth.
All
the
many
things
that
you
start
in
gitlab
get
distracted
and
come
back
to
some
point
so
around
those
themes
is
what
I
was
focused
on
when
coming
up
with
these
different
solutions.
A
All
right,
I
should
now
be
sharing
sigma
again.
Hopefully
yeah,
okay,
sweet,
so,
first
solution.
I
call
this
one
minimal
features.
The
reason
I
call
it
that
is
this
is
a
recurring
choice
that
I'm
making
around
a
few
of
my
designs,
but
we
just
have
so
many
pages,
specifically
in
gitlab,
I'm
avoiding
the
word
feature,
because
I
think
that
can
sometimes
be
confusing.
A
A
This
can
get
quite
overwhelming
for
users,
and
I
think
we've
been
seeing
that
a
lot
and
then
also
it
can
be
confusing
at
times
when
you're,
looking
at
a
group
or
a
project
they're
similar,
but
not
the
same,
epochs
appear
in
one
but
not
in
the
other.
You
can
see
multiple
things
in
one
like
issues
across
multiple
projects,
but
only
issues
in
one
project
in
a
different
view,
so
in
that
way
I'm
leaning
towards
finding
a
way
to
show
less
the
user.
A
I
haven't
removed
everything
from
view,
but
like
one
way,
I'm
considering
that
is
a
timer
right,
only
got
started
on
watch,
one
way
of
considering
doing
that
is
by
taking
them
out
of
the
left
hand,
menu
and
putting
them
into
a
page.
So
one
way
that
might
happen
is
maybe
labels
doesn't
appear
in
the
left-hand
menu.
It
appears
in
the
sidebar
somewhere
on
the
project
overview
page.
A
That's
just
one
idea.
We
could
consider
there,
but
what
I'm
thinking
of
this
one
is:
let's
not
show
any
more
than
five
features
at
a
time,
at
least
by
default.
Let's
be
opinionated
on
what
we
think
users
might
need.
For
this
example.
I've
pulled
some
of
the
most
frequently
visited
pages
in
the
product,
as
well
as
some
of
our
key
ultimate
features,
but
still
give
them
a
way
to
access
all
the
numerous
features
that
we
have
in
the
product.
Hopefully,
this
list
can
be
a
little
shorter
than
it
is
today.
A
I
think
it's
something
like
65
or
70
pages
can
be
discovered
through
the
left
side.
Menu
of
a
project,
I
think
some
of
those
could
just
be
eliminated,
possibly
like
locked
files.
I
don't
think
that
needs
to
necessarily
be
a
page,
or
at
least
it
can
be
a
page
but
doesn't
have
to
be
a
page
in
our
menu,
but
with
that,
I'm
also
trying
to
find
ways
to
draw
attention
to
a
specific
area.
So
I
want
to
use
the
left
sidebar
as
its
unique
attribute
in
a
project.
A
I
want
to
differentiate
that
from
somewhere
else,
so
in
this
design,
you'll
notice
that,
on
the
left
hand,
side
it
focuses
on
the
project
information
where
you
can
switch
between
your
projects.
So,
instead
of
defaulting
to
the
avatar
we're
using
the
icon
here
and
then
above
it
is
more
of
a
global
context.
A
A
So
if
you
were
to
play
with
prototype,
you
can
jump
between
the
project
apple
and
the
home
dashboard
page.
That's
pretty
much!
All
you
can
go
to
I'm
imagining
in
this
design
that
the
breadcrumb
and
the
search
bar
your
notifications
to
in
your
profile
that
stuff
would
not
be
sticky
like
it
is
today
it
would
scroll
up
with
the
page.
So
when
you're
in
the
middle
of
an
issue,
you
would
not
see
those
things,
but
you
have
to
scroll
back
up
to
find
them
yeah
and
that's
solution.
One.
A
D
A
Yeah,
so
I
mean
mainly,
I
would
say,
the
scope
is
around
how
we
are
considering
a
change
around
these
the
scaffolding
of
the
product,
so
the
way
you're
moving
around
with
the
left
sidebar
the
global
header,
but
there
are
weaknesses
in
the
features
that
we
may
offer
today,
like
the
dashboard
page,
only
showing
your
most
recent
projects
or
your
activity
feed.
So
there
might
be
some
ways
to
improve,
for
example,
reorienting
users
by
getting
them
to
a
more
meaningful
place.
So
I'm
open
to
the
fact
that
this
is
probably
not
the
best
dashboard
idea.
A
A
E
A
I'm
not
looking
so
much
for
the
insights
you
might
have
around
like
how
can
we
better
leverage,
color
or
drop
shadows
or
the
architecture
of
certain
elements
to
draw
attention
or
to
redirect
to
other
areas?
I
definitely
want
to
work
on
refining
those
ideas
with
you
more,
but
I
would
say
each
of
these
solutions
is
kind
of
different
from
the
other
one,
and
I
want
to
more
or
less
look
at
like
if
this
was
the
frame
for
our
house.
Does
it
seem
to
work
right
for
us?
Does
it
help
more
than
it
does
today?
A
Now,
I'm
not
completely
sure
one
works
better
than
the
other,
which
is
where
I
think
we
want
to
take
some
of
these
ideas
of
the
testing
and
then
figure
out.
Do
they
actually
help,
or
do
they
potentially
make
it
worse,
so
yeah
some
things
may
be
missing
and
it
may
not
be
obvious
if
you
haven't
been
thinking
about
it
all
the
time,
you're
right,
it's
kind
of
hard
to
call
out
all
the
little
things
that
I
went
into
each
of
them,
but
I'd
be
happy
to
answer
any
specific.
If
it
comes
up.
D
Oh,
that's
fine
yeah
that
helps
that,
but
I
don't
get
too
much
of
some
of
the
things
so
so
let
me
ask
this
question
then
with
and
you
can
feel
free
to
kick
this
to
the
end.
If
you
want,
I
don't
want
to
slow
up
the
process,
but
with
each
concept,
I'm
curious
how
it
aligns
with
those
themes
and
what
is
kind
of
the
leaning
leading
theme.
That's
driving
yeah,
like
direction.
D
A
I
I
wish
I
was
that
creative
and
thought
about
doing
it
that
specific
way,
but
to
counter
that
I
will
try
and
make
sure
that
I
highlight
how
it's
addressing
those
three
themes.
So
with
this
one,
reducing
just
the
number
of
features
or
pages
that
we're
putting
off
sidebar.
I
think
that
helps
reduce
the
amount
of
cognitive
load
on
our
user
to
specifically
help
them
reorient
across
the
platform
using
a
home
dashboard
page.
A
That
has
elements
that
are
more
of
a
top-down
or
global
view
that
help
you
kind
of
span,
work
elements
you
might
have
so
one
concept,
I'm
playing
with
there
are
things
like
save
views
and
queries,
which
is
something
that
we've
talked
about
before
or
having
drafts
that
you
can
pick
up
whether
that's
an
issue,
you've
started,
never
finished
or
comment,
you've
started
and
never
submitted
or
review.
You
started
and
never
submitted
those
things
are
kind
of
just
like
lost
in
the
ether
right
now,
and
hopefully
you
find
them
again.
A
So
those
are
elements
to
try
and
get
users
back
into
the
things
that
they
were
working
on
and
then
in
terms
of
picking
up
things
where
they've
left
off
I
mean
this
could
be
something
like
the
pipeline
status
with
something
that's
important
to
me.
I
just
keep
tabs
open
to
watch
pipelines
and,
I
think,
that's
incredibly
inefficient.
There
should
be
a
more
live
feedback
way
in
our
product
to
make
sure
you
have
awareness
of
where
pipelines
are
at
if
there's
something
you're
triggering
specifically.
D
A
Using
probably
some
poor
visual
design
choices
to
just
try
and
make
it
look
different
like
I
want
the
project
view
in
this
design
to
feel
different
than
the
home
dashboard.
I
want
them
to
have
a
unique
feel,
so
you
don't
feel
like.
Oh
am
I
looking
at
the
same
thing
and
my
sidebar
is
just
slightly
different,
or
can
we
use
some
visuals
to
actually
distinguish
the
pages.
D
D
D
I
like
we
had
those
notification
badges
for
like
issues
and
mrs
at
the
top,
and
I
think
those
are
probably
pretty
wet
widely
used
today,
and
I
would
assume
maybe
a
big
reason
is
that
is
for
that,
like
theme
of
kind
of
picking
up
where
you
left
off
or
things
that
you
know
you've
assigned
to
right.
So
I
understand
that
now,
there's
like
this
dashboard
page,
which
provides
that,
but
it's
on
some
level
not
really
you're,
not
able
to
access
this
information
from
anywhere
any
page
that
you're
at
it's.
A
A
Part
of
what
I
would
love
to
see
is
just
an
overhaul
of
notifications
as
well,
so
that
we
can
better
catch
users
when
they
need
to
know
when
something
is
alerting
them,
but
not
creating
unnecessary
noise
for
them.
So,
yes,
it
is
helpful
to
know
that
new
issues
been
assigned
to
me,
but
do
you
have
to
be
telling
it
to
me
all
the
time
once
I've
gotten
it
assigned?
I
know
where
it
is,
and
I
know
how
to
find
it
so
again,
this
is,
I
think,
where
we'd
want
to
lean
on
some
user
testing.
A
D
A
Yeah,
I
think
one
thing
we're
going
to
eventually
run
into
and
I
don't
want
to
try
and
necessarily
just
design
for
a
problem
we
don't
have
yet,
but
I
imagine
more,
things
will
become
assignable
or
become
responsibility
for
people
over
time.
Right
now
we
act
like
only
issues
and
merge
requests
are
important,
but
I'm
sure
things
like
incidents
pipelines
and
all
those
things
are
things.
A
All
right,
so
this
one,
I'm
called
lovingly
fewer
folders.
So
again,
all
these
are
starting
as
best
I
can
from
a
project
view,
so
still
keeping
that
same
kind
of
conceptual
model
of
mind
where
we
still
have
projects
inside
groups
subgroups
and
groups.
I
don't
see
that
necessarily
changing
anytime
soon,
like
that
still
seems
to
be
the
backbone
of
what
I'm
hearing
from
workspace
around
how
they're
keeping
their
groups
and
projects
architecture,
but
there's
still
going
to
be
like
a
back-end
difference
there,
just
potentially
in
our
ui.
A
We
might
still
have
a
difference
between
a
group
and
project.
So
in
this
case
I'm
only
showing
what
would
be
showing
for
project,
and
here
I
have
a
manage
folder
a
build
folder
and
our
operations
and
secure
again
still
playing
with
that
idea
of
showing
them
less
at
a
time.
So,
ideally,
these
are
features
that
users
are
visiting
together.
So
we
might
see
that
users
often
go
from
issues
to
merge
requests
to
ci
cd
to
boards
and
because
we
know
that
heavy
relationship
we
want
to
group
them
together.
A
What
I've
noticed
is
users
tend
to
just
kind
of
skim
through
what
they're
looking
for
the
more
buckets
they
are,
the
longer
it
takes
to
kind
of
sort
through
the
items
I
think
you
can
be
like
up
to
like
12
or
so
today
that
you
have
to
sort
through
and
for
this
one
instead
of
having
a
home
dashboard
page
specifically
dedicated
helping
you
reward
reorient.
This
one
is
more
focused
on
using
global
search
to
help.
A
You
have
these
like
shortcut
links
to
give
you
a
view
of
different
information,
so
the
explore
page
admin
area,
newer
ideas
like
a
recently
visited
list
or
even
your
drafts
again
I've
pulled
the
pipeline
status
up
into
the
global
header
to
try
and
distinguish
from
the
left
sidebar,
I'm
not
strongly
confident
in
users.
Picking
up
on
the
differentiation
between
the
global
header
and
the
left
sidebar,
I
feel
like
what
I've
been
observing
is
that
users
tend
to
just
ignore
the
top
bar
and
just
focus
on
that
left,
sidebar
and
they're,
not
necessarily
thinking.
A
A
B
A
B
A
Idea
all
right,
so
this
one
I've
called
the
sidebar
layers
so
for
this
one,
I've
also
removed
the
global
navigation.
I'm
kind
of
stuck
with
that
theme
of
the
breadcrumb
and
search
your
profile
remaining
at
the
top
of
the
page,
but
being
probably
secondary
information
that
you're
not
going
to
use
all
that,
often
probably
even
possibly
even
tertiary,
focusing
on
making
sure
users
know
where
they
are
so
that
breadcrumb
seems
to
be
really
drawing
users
attention
and
it's
helping
them
know
where
they
are.
A
But
it
is
interesting
that
we
don't
always
display
the
page
name
that
you're
on,
possibly
because
that's
listed
on
the
page
itself
at
times,
but
it
could
help
reinforce
exactly
where
it
is
for
this
one.
I've
played
with
the
idea
of
taking
out
things
like
to
do's,
merge,
requests
and
issues
and
replace
them
with
notifications
that
same
work
concept,
where
we
join
issues,
merge,
requests
and
those
kinds
of
things.
So
in
nick's
initial
question,
how
do
I
know
where
things
are
and
what
their
status
is
from
anywhere?
A
This
would
allow
you
to
keep
that
context
without
having
to
go
to
a
dashboard
page.
So
same
type
of
features,
you
can
go
find
your
activity
feed,
which
already
exists
today,
but
probably
the
biggest
thing
that's
different
here
is
you
have
pin
projects
and
groups,
so
I've
pinned
a
few
projects
and
groups
in
this
example
that
I
often
use
and
switch
between.
So
for
me,
in
real
life,
this
will
probably
be
like
git
lab
pajamas
design
system,
git,
libor,
gitlab.com
and
gitlab
development
kit.
A
This
allows
me
to
switch
between
those
contacts
a
little
bit
faster
and
it
would
always
be
anchored
to
the
page.
So
when
the
sidebar,
the
contextual
sidebar,
is
collapsed,
those
elements
would
always
remain
there.
I
can
always
pull
out
the
things
that
are
specific
to
my
project
now,
within
the
project
view,
I've
still
stuck
with
the
we're
being
opinionated
on
ideas
that
we
want
to
reduce
the
number
of
features
that
we're
proposing
that
are
in
the
sidebar.
A
For
this
one,
I
did
explore
a
bit
of
a
dashboard
page,
it's
a
little
different
than
the
first
one,
so
some
things
that
don't
necessarily
appear
in
the
global
sidebar
things
like
bookmarks,
so
being
able
to
save
any
page
in
gitlab
way.
We
don't
really
have
that
feature
today.
We
have
to
rely
on
your
web
browser
for
that,
helping
you
find
things
that
you've
been
mentioned
in
or
like
the
typical
global
dashboard
views
for
snippets
security
environments,
those
kind
of
things
and
then
finding
your
recently
visited
groups
and
projects
again.
A
D
A
Yeah,
that's
a
good
point
and
again,
I
think
all
these,
like
smaller
visual
design
decisions,
we
can
totally
negotiate
and
figure
them
out
more
or
less
like
with
this
one,
keeping
everything
in
a
vertical
left:
sidebar,
no
global
header,
but
it's
now
oriented
on
the
left,
getting
a
switcher
to
switch
between
contexts,
grouping
the
elements
for
the
contextual
menu.
Next
to
that
global
nav.
Does
that
feel
in
comparison
to
like
a
horizontal
to
a
vertical
just
thinking
about
those
types
of
differences
that
scaffolding,
the
framing
of
gitlab
itself?
A
So
I
don't
think
it
would
actually
look
that
much
different
than
we
have
today
on
a
mobile
view,
but
our
I
don't
think
our
numbers
on
small
devices
is
very
high.
So
it's
not
a
key
concern
of
mine
at
the
moment
it's
more
like
I
would
want
to
make
sure
desktop
works
the
best
and
to
make
sure
that
mobile
isn't
broken.
It
should
still
be
accessible
and
usable,
but
it
shouldn't
drive
the
desktop
experience.
I
don't
think.
D
I
did
like
how
you
are
surfacing
the
pipelines
within
the
projects.
I
do
like
the
pinned
projects
as
well.
This
to
me
gives
it
like
makes
a
lot
of
sense.
You
know
the
way
it's
structured,
I
wonder
if
the
pipeline
spinners
could
like
even
go
a
level
higher
to
those
pin
projects.
If
you
had
one
running
like
on
the
apple
project,
you
might
see
the
spinner
of
the
pipeline
or
its
progress
so
that
you
didn't
have
to
keep
opening
them
all,
but
yeah.
A
It's
cool
yeah,
that's
a
good
point
risen
while
you're,
describing
that
it
made
me
remember
that
I
also
was
playing
with
how
you
would
be
able
to
access
the
features
here.
So
this
is
different
than
the
previous
two
designs.
I
was
showing
where
it's
more
of
a
modal
view,
you're
scrolling
through
the
options,
this
drawer
item
would
have
all
the
different
features
in
it
again.
I
hope
we
can
reduce
this
list
a
bit
more,
but
you
could
decide
what
you
want
to
toggle
on
and
have
in
your
project's
left
side
menu.
A
So
you
get
some
options
on
by
default.
Maybe
we
turn
on
repository
and
security
dashboard
by
default.
But
if
you
really
care
about,
I
don't
know
releases,
then
you
can
choose
to
add
those
things
in
the
prototype.
Doesn't
add
them
in
for
you
today,
but
that's
just
one
way
that
we
might
give
users
the
ability
to
show
the
things
they
care
about
most,
so
it
doesn't
have
to
be
varied,
a
layer
if
they
care
about
it.
A
Hopefully,
that's
like
the
best
of
both
worlds,
where
we
can
minimize
the
amount
of
things
we
show
users
at
one
time,
but
still
give
them
the
flexibility
to
keep
what
they
care
about
their
fingertips.
I'm
a
bit
squeamish
of
the
thought
of
minimizing
and
then
having
users
get
frustrated
that
they
have
to
do
like
two
or
three
clicks
to
get
to
the
thing
they
visit
in
every
single
project.
D
Similar
to
the
point
that
jeremy
had
made
earlier
about
the
search
bar
looking
like
it's
part
of
kind
of
that
page
you're
on,
I
can
see
that
and
like
the
user
menu,
perhaps
being
more
tied
to
that
far
left
navigation
bar
just
because
those
book,
those
both
those
things,
are
kind
of
like
global
one's,
a
global
navigation,
one's
a
global
menu.
I
know
that
the
left
sidebar
is
kind
of
already
packed
in
this
example,
but
right.
A
We
can
always
take
stuff
out
too,
like
I
I'm
putting
ideas
in
here
that
may
never
come
to
fruition
like
I'll
I'll
pick
on
my
own
idea
like
drafts.
That
may
never
actually
happen
like.
There
are
definitely
concepts
that
we
might
take
out
of
here
to
prioritize
more
important
things,
and
if
the
more
important
things
is
switching
projects
and
groups,
then
yeah
so
be
it.
A
A
I
could
use
that
to
find
the
different
groups
there
and
then
the
home
dashboard
page
still
keeps
the
left
sidebar,
but
the
left
sidebar
changes
depending
on
which
location
of
the
product
you're
in
so
in
this
area.
You
now
have
things
like
recently
visited,
but
all
the
normal
features
that
we
have
in
the
product
today
that
are
in
the
global
header
have
been
pulled
into
the
section.
So
your
to-do
list,
your
issues,
merge,
requests
instead
of
putting
things
in
the
menu
menu
groups,
projects,
security
operations,
snippets
environments,
all
those
dashboard
pages
also
appear
here.
D
A
If
I
was
looking
for,
I
don't
know
the
blueberry
project,
I'd
probably
my
first
thing
would
be
to
search
for
it,
but
I
think
in
theory
you
could
go
to
the
home
page:
go
explore
your
projects
and
search
and
filter
by
name
just
kind
of
like
you
do
now
on
the
home
project
page
but
yeah.
It
would
all
kind
of
be
dependent
on
where
you
are
like
using
the
breadcrumb
may
or
may
not
be
the
right
thing.
You
would
have
to
have
some
knowledge
about
it.
A
E
A
Yeah,
I
think
it's
fair
feedback.
I
do
know
that.
I
think
there
are
a
lot
of
users
that
see
our
breadcrumbs
and
think
about
their
groups
and
subgroups
and
projects
as
a
directory.
So
I
feel
that
for
some
of
them
it
only
is
natural
to
want
to
explore
it
in
such
fashion,
but
yeah.
Maybe
there
are
some
ways
that
we
can
just
better
help
them
explore
that
without
having
to
lean
on
the
breadcrumb
as
a
navigational
element.
A
A
A
D
A
Right
yeah,
and
for
like
this
one
I
mean
this
is
no
different
than
our
current
existing
one.
Where
it's
just
like
a
to-do
list,
I
was
trying
to
explore
some
of
the
ideas
of
trying
to
reduce
that
feeling
of
being
overwhelmed
by
just
using
a
dot
indicator
rather
than
like
a
full-on
badge
counter
at
times.
A
You've
got
something
you're
gonna
go
check
out
once
you
viewed
it,
that
dot
might
go
away
so
that
it
goes
out
of
your
mind
and
you
can
go
back
to
it
when
you
need
to,
but
that
way
you're
not
keeping
count,
how
many
numbers
or
what
the
number
is
in
your
badge,
because
that's
what
I'm
doing
today,
there's
I
think
nine
assigned
to
me
and
I
have
to
mentally
pay
attention
to,
did
that
increase
to
10.
Did
it
go
down?
I
don't
know.
A
A
A
I
know
nick
maybe
has
some
experience
with
that,
as
he's
had
to
kind
of
navigate
that
challenge
with
the
global
search
as
they
try
and
index
all
this
information.
But
I
think
this
aligns
with
reducing
the
feeling
of
being
overwhelmed
because
there's
less
places
to
go
it's
more
about.
What
are
you
looking
for
so,
instead
of
having
to
find
your
specific
project
or
find
your
specific
group,
you
just
go
to
the
future.
You
care
about
and
search
for
the
thing
that
you
are
looking
for,
which
requires
a
little
bit
of
forethought
coming
into
it.
A
A
75
000
issues
and
you're
just
not
going
to
know
where
to
start
so
in
this
example,
I've
I
have
a
left
sidebar.
It
would
never
change.
It's
always
gonna,
be
the
same.
I've
chosen
specific
handful
of
features
again
that
are
most
popular
pages
to
visit
right
now,
the
product
as
a
starting
point,
and
just
to
help
illustrate
that
this
is
agnostic
of
a
group
or
project
view.
A
If
that's
even
possible,
I
don't
know
if
we
can
afford
to
even
do
that,
but
I
wanted
to
at
least
have
the
idea
on
the
table
and
the
only
other
page
that
I
did
besides
this
one,
because
I
didn't
explore
a
home
dashboard
page
in
this
one
was
just
having
a
browse
page
that
is
more
full
for
both
groups
and
projects.
They
are
not
just
a
group
page
with
subdirectories
of
subgroups
and
just
a
project
list
like
it
would
just
be
one.
So
you
could
have
both
your
space
so
things
that
belong
to
you.
A
A
This
might
not
be
as
overwhelming,
but
for
this
one
specifically,
I
think
this
is
where
saved
views
would
be
really
important,
because,
as
I'm
further
utilizing
gitlab
creating
custom
views
of
things,
I
would
want
to
be
able
to
shortcut
back
to
them.
So
I
don't
have
to
recreate
the
same
thing
over
and
over
and
over
again,
but
it
would
help
reduce
some
of
the
confusion
around
like.
Where
am
I,
in
the
platform
you've
specified?
A
What
happens?
If
you
clear
all
these
filters,
I
don't
know
we
probably
would
give
you
500
error,
because
until
you
you
need
to
filter
by
at
least
one
thing.
Otherwise,
you'll
break
our
database,
but
yeah
just
a
same
similar
concept
of
trying
to
reduce
the
sheer
volume
of
things
that
we're
showing
giving
users
the
ability
to
kind
of
pin
what
they
care
about
and
save
where
they
want
to
go,
but
still
giving
that
like
global
context
view.
A
D
D
The
other
thing
is,
we
typically
render
these
lists
says
lists
but
like
when
you
get
to
an
issue
list
like
this,
you
might
want
to
view
it
as
a
board
or
a
gantt
or
roadmap
or
other
ways.
Besides,
just
our
current
lists
to
view
that
data
and
right
now
we
make
people
go
everywhere
to
find
those,
so
I
think,
having
these
views
in
one
spot,
where
you
could
rotate
between
different
views
on
the
same
set,
makes
a
lot
of
sense.
D
E
A
A
Yeah,
I
haven't
really
explored
that
all
that
much,
but
I
think
that
makes
sense
like
give
users
a
few
out
of
the
box
views
that
we
think
might
be
useful
for
them.
I
think
a
great
way
to
start
would
be
the
things
that
we
already
create
those
notifications
around
those
badges
today
that
tell
you
what
issues
are
assigned
to
you.
Merge
requests,
reviews
that
kind
of
stuff.
A
A
A
D
B
E
B
The
second
one
is
very
similar,
but
maybe
there's
not
as
much
differentiation
between
when
you're
in
a
group
or
a
project
and
a
dashboard,
because
you
always
have
that
header
at
the
top
and
the
sidebar
is
group
is
more
opinionated
in
the
sense
that
it's
grouped
into
specific
sections.
And
then
you
can
add
things
to
those
sections.
A
B
The
third
one,
this
one
is
a,
I
would
say,
is
more
drastic
change
where
it
has
a
way
to
easily
switch
groups
and
projects
on
the
left.
There's
some
main
navigation
items
on
the
left
as
well,
and
me,
I'm
not
sure
exactly
what
these
are
yet.
I
haven't
dived
into
it,
but
then
the
sidebar
within
a
grouper
project.
The
items
in
the
sidebar
are
more
related
to
me
personally.
Yep.
B
A
E
I
I
do
have
a
question
because
just
back
to
kind
of
the
initial
thought
on
the
visual
side
of
things,
I
feel
like
that
could
maybe
influence
the
testing
more
than
you
might
want
it
to
so.
Is
there
a
way
to
to
to
go
into
text
wireframe
things
like
that
where
it
simplifies
the
testing
so
that
it's
purely
based
on
the
concept
and
the
mental
model,
and
not
anything
to
do
with
aesthetics
or
hierarchy
or
or
concept.
A
I
would
be
curious
to
know
if
users
would
be
able
to
recognize
the
complexities
that
they're
introduced
with
the
product
today.
So
I
don't
know
if
it'd
be
easy
to
discern
like
do.
They
know
if
they're
in
a
group
or
project
depending
on
what
we're
showing
them
with
just
like
a
wireframe,
but
I
mean
perhaps
we're
asking
the
wrong
question.
E
Yeah
because
I
I
think
to
be
honest,
as
you
pull
up
through
these
granted,
it's
the
first
time
like,
if
you
showed
it
to
me
right
away.
I
wouldn't
necessarily
be
like.
Oh
that's
a
project
or
that's
a
group
right.
I
would.
I
would
still
have
to
walk
through
kind
of
my
decision
tree
first
to
even
get
there,
so
I
don't
know
that
it
to
me.
C
D
A
That's
a
great
question
I'll.
Let
ashley
provide
some
more
color
to
it,
but
one
of
the
things
that
we
had
chatted
with
adam
about
from
ux
research
was
like
hey.
We
have
some
like
rather
complex
ideas
that
we
want
to
test
and
we
want
to
know
what
the
best
way
is
to
validate
these
concepts.
So
I
would
say
we
haven't
drilled
down
specifically
what
that's
going
to
look
like
yet,
but
ashley
and
I
have
been
collaborating
on
a
list
of
I
guess.
Eventually,
it
boils
down
to
some
scenarios.
C
A
Yeah,
I'm
not
entirely
sure
how
I
would
do
that,
let's
just
say
if
I
was
taking
solution
five
and
like
solution
three,
just
because
they
are
conceptually
so
different,
like
one
kind
of
assumes,
we
keep
our
architecture
as
it
is
today,
and
you
have
to
navigate
to
a
group
or
project.
Have
your
specific
view
so
like
this
one,
where
you're
you're
still
staying
within
a
project
view
it's
hard
to
sh.
A
I
can't
like
show
this
page
as
easily
in
solution
five,
where
you
probably
have
to
go
drill
down
and
find
a
readme
in
a
repository
to
see
that
same
thing,
but
they're
they're
kind
of
different,
so
yeah.
As
I'm
saying
I
don't
know
what
the
best
task
would
be
to
give
them
or
what
to
present
them,
which
is
what
I
was
looking
for
us
to
kind
of
decide.
I
was
like
this
is
what
we
want
to
test,
so
I
can
try
and
recreate
them
in
the
prototypes.
We
never
really
got
to
pinpointing
that
this
milestone.
B
So,
for
instance,
maybe
this
one
performs
better
at
picking
up
where
you
left
off,
whereas
the
second
one
and
I'm
pulling
this
out
of
nowhere.
The
second
one
performs
better
at
orienting
the
users
across
the
product
and
all
of
the
tasks
and
all
the
research
questions
that
we're
asking
in
the
study
should
all
tie
back
to
those
so
that
we
have
clear
measures
of
which
one's
performing
better
and
then
from
there.
We
can
see
all
right
if
this
was
performed
better
here
and
this
one's
performing
better.
B
In
terms
of
the
tasks
and
like,
for
example,
this
one
here,
it
doesn't
sound
like
there
would
be
a
project
overview
page,
so
that
kind
of
puts
us
in
an
interesting
position
right
where,
like,
if
the
research
is
saying
we
land
everyone
on
the
project
overview
page.
What
does
that
mean
for
this?
This
prototype
here.
A
E
A
Yeah,
it's
a
it's
a
hard
line
to
walk.
I
agree
and
that's,
I
think,
where
it
gets
really
challenging.
Is
there
are
good
elements
about
our
navigation
for
sure,
but
I
think
some
of
the
shortcomings
are
tied
to
performance.
Barriers
are
tied
to
missing
features
or
just
general
mis
understanding
of
gitlab
itself,
and
so
it
feels
like
it
bleeds
into
other
areas
of
the
product
like
notifications
or
a
dashboard
page
or
the
overview,
because
we
have
to
lean
on
other
things
to
make
up
for
the
deficits
right
now.
A
D
E
For
me
to
kind
of
find
my
way,
it's
like
an
all
or
nothing
kind
of
deal,
and
then
three
that
are
for
the
breadcrumbs,
because
I
just
think
that
that
to
me
is
when
I
think
about
the
accessibility
implications
and
the
ux
implications
of
mixing
patterns
like
that.
I've
never
seen
an
outcome
be
positive
in
that
way.
E
A
That's
fine
thanks
for
the
feedback.
I
really
like
your
thinking
through
on
solution.
Five.
I
had
not
considered
that
aspect
of
it,
but
it
makes
sense.
I
do
feel
like
it
a
little
bit
over
rotates
to
assuming
you've
got
a
lot
of
things
you
care
about,
but
there
there's
definitely
some
segment
of
gitlab
that
doesn't
have
thousands
of
projects
that
they
work
in.
They
work
in
like
two
very
happily
and
it's
less
of
a
challenge
for
them,
and
this
might
make
that
experience
worse
for
those
people.
E
Yeah,
it's
and
we
can
do
this
like
at
another
another
instance
or
async
or
something,
but
I
did
always
back,
have
a
concept
that
was
similar
to
this,
that
maybe
we
can.
We
can
hash
that
out
or
whatever,
but
it
it
has
more
of
a
grouping
between
a
global
high
level,
but
then
more
of
that
tailored
to
project
or
individual
view,
but
in
that
same
kind
of
a
concept
of
a
rigid
left
sidebar.
So
we
can
maybe
explore
that
when
we
have
time
yeah.
A
B
The
one
that
I
was
hesitant
about
was
actually
the
first
one
and
it
may
just
be
further
refining
the
idea,
but
my
first
reaction
was
like
the
header
disappeared
on
projects
and
groups
and
going
back
and
forth.
I
see
that
actually
a
lot
of
content,
like
the
whole
right
side
of
the
header,
is
the
same.
All
of
it's
the
same,
except
for
there's
a
breadcrumb
and
the
pipeline
running,
but
but
the
other
part
is
purple.
So
that
was
just
confusing
to
me.
B
E
Yeah,
I
think
that's
where
I
was
going
with
that
continuity
and
not
knowing
what
was
what
and
that's
where
some
of
the
visual
design
could
maybe
really
hurt
testing
if
this
concept
is
viable
from
a
you
know,
you're
taking
somebody
from
this
higher
level
to
a
deeper
one.
If
the
visual
design
followed
that
path
and
and
helped
the
user
understand
where
they
were
at
in
that
flow,
that
would
help.
But,
as
is
it
it
it's
doing
the
opposite,
where
it's
making
you
feel
more
lost,
rather
than
hey.
E
A
A
B
And
kind
of
looking
at
ashley's
point
we
there
are,
you
know
we
have
to
keep
the
breadcrumb
one,
it's
just
we
have
to
so
that's
one
of
the
ones
I'll
test
and
then
there's
kind
of
the
one
where
everything's
on
the
left
side,
that's
another
one
and
then
the
first
two
they're
different,
but
they
feel
similar,
similar
ideas
in
terms
of
grouping.
So
maybe
those
are
the
three
categories
that
then
in
15
3.
We
start
kind
of
refining
further.
D
Just
curious
was
the
breadcrumb
one
tied
to
being
able
to
kind
of
change
projects
and
groups
in
that
method.
Or
could
we
explore
a
concept
that
had
the
breadcrumbs
more
front
and
center,
but
maybe
not
as
that
sort
of
switcher
like
we
experienced
in
this
prototype,
because
that's
where
I
had
the
most
problem.
A
A
Now
it
may
not
be
the
best
placement
for
it,
but
at
least
how
it
stands
was
how
he
thought
it
should
work
so
we'll
at
least
keep
that.
But
if
there's
another
idea,
you're
saying
about
maybe
making
a
breadcrumb
front
center,
I
think
that
would
be
okay.
I
still
think
the
limitation
to
the
breadcrumb
is
like
you
better
know
where
the
thing
is
because
otherwise
you're
just
gonna,
be
stuck
in
scrolling
menus
looking
for
something
that
may
not
even
be
where
you're
looking.
But
I
guess.
A
E
Yeah-
and
I
know
that
at
the
apple
level
like
it
makes
sense
to
change
things,
but
if
you're
changing
things
at
the
tree
level
like
then,
it
makes
somewhat
less
sense,
because
your
context
is
still
going
to
shift
right,
you're
not
going
to
have
an
apple
project
under
the
house,
and
so
for
me.
I
think
that
conceptually
now
understanding
kind
of
the
how
you've
explained
it.
E
I
think
that
you,
you
could
do
something
with
this
concept,
a
if
it
wasn't
called
bread,
crumbs
and
b
if
it
didn't
look
like
bread
crumbs,
where
it
was
it's
more
of
a
tiered
approach.
It's
something
some
other
metaphor,
but
not
breadcrumbs,
because
immediately
that
infers
a
specific
interaction
and
it
infers
a
specific
aesthetic
and
both
of
which
are
what
I
find
problematic
about
the
the
concept.
E
So
if
you
had
a
way
that
you
know
explore
something
on
that
that
you
could
still
understand
that
you're
nesting
you're
getting
deeper,
then
it
could
work.
It's
kind
of
akin
to
to
concept
three
which,
which
has
this
sense
of
depth.
You've
got
a
global
level.
You've
got
a
specific
level
that
that
me
has
that
nesting
approach,
and
so,
if
there's
a
a
some
kind
of
a
method
to
have
that
similar
type
of
a
depth
feel
at
that
higher
level.
B
E
So
I
will
say
that
this,
this
type
of
direction
is
probably
my
favorite,
and
I
know
it's
very
you
know
it's
very
slack
like
and
there's
other
tools
like
that
too,
but
it's
it's
kind
of
used
to
even
even
some
of
the
design
tools
that
I'm
used
to
from
the
right
sidebar,
where,
like
the
old
photoshop
illustrator
days,
where
you
have
your
groups
of
of
of
views
and
widgets
and
you're
able
to
quickly
jump
in
and
see
those.
So
this
kind
of
aligns
with
some
of
my
mental
model
too,
but.
A
Well,
I
don't
feel
like
it's
by
any
means
copying.
I
think
it's
mostly
just
understanding
that
we
face
a
similar
problem,
that
a
lot
of
other
applications
that
give
you
multiple
places
to
go
in
their
application
have
like
you
got
to
switch
between
servers
and
discord.
You
got
to
switch
between
servers
and
slack.
You
got
to
switch
between
things
and
different
other
platforms.
You
have
and
they've
all
kind
of
found.
A
Oh,
it
helps
users
to
find
what
they're
looking
for
the
one
challenge
that
we
have
that's
different
than
others
is
relies
on
our
access
control
model.
So,
whereas,
like
I
get
every
slack
workspace
that
I've
been
added
to
at
my
fingertips,
I
have
to
live
with
the
fact
that
I'm
in
a
thousand
plus
projects
and
get
live
already,
so
I
can't
just
put
every
single
project
in
the
left
sidebar
by
default.
That
would
be
pointless.
It
probably
would
give
me
15
useless
projects
at
the
top
or
not
useless,
just
ones
that
I'm
not
using.
A
So
we
have
to
work,
find
a
unique
way
to
help
users
put
what
they
would
care
about
there.
So
in
this
yeah
like
in
this
one,
you
can
maybe
pin
your
project
or
maybe
your
stars,
but
I
think
if
star
is
conceptually
different
nick-
and
I
had
a
little
chat
about
that
last
week,
like
to
me
stars-
are
things
that
you
like
socially
support,
maybe
or
interested
in,
but
maybe
not
like
the
thing
you're
working
on
it.
All
kind
of
depends
on
what
you
use
gitlab
for.
E
Agreed
and
me
alluding
to
other
tools
is,
is
more
of
a
compliment
than
a
not
than
oh
you're.
Being
it's
it's
a
more
of
a
positive
because
we
don't.
We
don't
need
to
reinvent
the
wheel
right.
That's
if
there's
a
paradigm
that
works
and
has
the
same
similar
constructs.
Then
there's
no
need
to
reinvent
that
so
yeah
yeah.
B
B
I
think
is
closest
related
to
number
two
yep
and
then
jeremy
was
just
talking
about
one
jeremy
or
austin.
I
know
you've
looked
at
it
is
that
idea
largely
different
than
one
of
the
proposals
here
and
is
that
something
we
should
explore,
or
is
it
kind
of
along
the
same
lines,
but
maybe
visually
different
for
right.
E
Yeah
this
was
done
a
long
time
ago,
and
so
I
would
have
to
kind
of
go
back
and
re
rework
some
of
my
thinking
here
or
think
through
it
to
explain
it
better
to
me.
That's
why
I
brought
this
one
up
as
it
feels
closest
to
five,
but
maybe
with
some
more
clear
grouping
of
very
high
level,
get
lab
concepts
and
then
more
specific
project
related
things
or
group
related
navigation
in
their
own
sections,
but
all
contained
and
clearly
kind
of
identified.
A
Yeah
he's
just
saying
visually
like
it's
a
left
sidebar
with
like
these
more
just
imagine
just
global
features
versus
like
our
devops
features,
except,
I
think
the
difference
here
is
jeremy's
living
within
the
constraints
of
you
still
need
to
be
looking
at
a
specific
project
and
those
features
tied
to
that
specific
project.
Whereas
these
things
are
more
of
your
top-down
view,
your
global
scope
of
everything.
E
A
A
Yeah
I
heard
a
menu
menu
which
this
one's
a
grid,
dot
menu,
but
not
quite
the
same
so
yeah.
Those
are
those
are
all
the
ideas.
I've
had
a
lot
of
fun,
this
milestone
working
through
each
of
them.
I
wish
I
could
confidently
say
like
this:
is
the
one
we're
going
to
definitely
go
test,
but
I
think
what
we
know
for
sure
is
there
needs
to
be
a
little
more
refinement
of
them
yeah.
A
A
C
Oh
yeah,
sorry
I
I
won't
be
able
to
attend
that,
but
I
will
definitely
read
through
the
notes.
Maybe
it'd
be
good
to
sync,
because
I
won't
be
there
for
that
meeting
or
the
weekly,
but
just
thinking
about
some
of
the
things
that
were
mentioned
in
terms
of
maybe
deciding
on
which
ones
ultimately
will
be
tested
and
maybe
moving
towards
more
just
like
the
lower
fidelity
wireframes
and
stripping
it
down
a
little
bit.
C
B
That
makes
sense
and
that
since
that
would
be
more
lightweight,
I'm
thinking,
then
potentially
we
could
do
refinement
in
15
3,
and
this
lightweight
research
to
kind
of
help,
facilitate
a
direction
and
then
in
1504
would
be
the
larger
study.
With
a
more
built
out
prototype
that
we
test,
we
wouldn't
be
doing
that
with
five.
Obviously,
it
would
be.
We
would
move
forward
with
whatever
we
learned
in
153.
A
Yeah,
so
I
think
what
I'm
hearing
is
break
them
down
into
their
hierarchical
elements,
so
focus
less
on.
What's
on
the
body
of
the
page,
but
more
around
like
how
do
you
move
between
things
just
using
whether
it's
a
top
or
left
sidebar,
depending
on
the
design
and
then
start
from
there
and
find
a
way
to
test
it,
which
I'd
be
fine?
A
Putting
those
things
together,
probably
useful
to
check
in
with
jeremy
and
see
if
he's
got
some
ways
to
help
make
them
feel
the
same,
even
though
they
are
structurally
different
in
some
ways
and
then
actually,
if
you
could
just
give
me
an
idea
of
just
like,
maybe
just
like
one
or
two
things
that
we
would
want
to
make
them
do.
I
think
that
would
give
me
enough
to
make
the
like
three
or
four
interactions.
We
want
each
one.
C
So
yeah,
you
wouldn't
necessarily
need
to
be
build
out
a
bunch
of
interactions.
It
would
be
more
static.
If
that's
what
we're
talking,
because
I
thought
that's
what
you
guys
were
talking
about,
but
yeah,
we
could
still
evaluate
like
basically
the
similar
tasks
that
we
were
going
to
do,
and
it
would
just
be
more
of
like
do
they
know
what
they're
looking
at
as
opposed
to.
Can
they
like
do
all
the
clicking
to
get
through
it.
A
C
C
A
C
I
feel
like
that's
okay,
if
they're
all
similar
to
that
and
as
long
as
like,
whatever
we're
asking
them
to
decipher
like
there's
enough
to
make
up
you
know
for
them
to
get
to
some
understanding
based
on
how
much
we
show
so
like
if
we're
asking
them
like.
How
would
you
you
know,
switch
from
a
group
to
a
project
we
obviously
have
to
show
enough
to
where
that
would
be
decipherable,
but
also
enough
that
it's
not
like
the
only
thing
on
the
page,
because
then
that's
kind
of
unfair.
C
B
B
D
A
E
Yeah,
too,
and
and
to
the
point
about
aesthetics
too
there
I
think
you
could
test
different,
wireframe
layouts
right,
where,
if
you
just
did
these
into
boxes,
you
could
you
could
put
the
tiered
sidebar
with
maybe
different
color
gradation.
You
could
put
a
header
and
a
sidebar
with
different
sections
and
leave
no
content
and
simply
even
ask
users.
Where
would
you
expect
to
change
a
project?
Where
would
you
expect
of
a
search
for
for
x?
E
E
Yeah.
That
makes
sense.
I
know
that
adds
complexity
to
the
testing,
but
it
you
know
even
a
few
questions
like
that
would
help,
I
think,
get
a
sense
of
you
know
what
might
work,
because
maybe
this
concept
works
really
good,
but
people
don't
expect
it
in
a
linear
fashion.
You
know
that
kind
of
thing
so.