►
Description
Within this timezone group, various domain counterparts (Engineering Managers, Product Designers, Product Managers, Technical Writer, and/or UX Researcher) contribute to a User Journey Map (UJM) that spans the whole Create stage.
More information:
- Epic: https://gitlab.com/groups/gitlab-org/-/epics/6964
- Issue: https://gitlab.com/gitlab-org/create-stage/-/issues/12944
A
And
welcome
to
the
final
session
of
the
user
journey
map
for
the
create
stage,
and
this
is
the
apac
emea
group.
Let
me
quickly
share
my
screen
to
talk
about
what
we're
going
to
do
today
and
so
last
time
we
met.
We,
of
course,
did
this
intro
session,
where
everyone
collaborated
on
the
steps
here
at
the
top
and
we
brainstormed
them
together.
A
I
then
moved
you
can
see
them
in
yellow
here
at
the
top.
I
moved
them
down
to
this
area,
which
is
the
actual
map
that
we
were
building
together
and
asynchronously.
What
I
asked
each
of
you
to
do
in
this
part
between
the
1st
and
the
15th
of
december
was
to
fill
out
the
remaining
sections
that
now
have
stickies
for
actions,
feelings,
pain,
points
and
opportunities.
A
Thank
you
so
much
for
contributing-
and
this
will
help
definitely
help
this
session-
have
more
content
for
us
to
discuss
and
yeah.
As
I've
always
said,
it
doesn't
need
to
be
right,
things
don't
need
to
be
validated
just
based
on
our
assumptions
and
what
we
think
sasha
the
persona
for
this
user
journey
would
go
through,
would
do
would
feel,
would
think
and
the
pain
points
and
opportunities
to
address
those
pain
points,
and
today,
our
in
in
our
wrapping
up
session.
A
What
we're
going
to
do
is
or
what
I
had
asked
to
do,
but
I
think
we
will
have
to
improve
this
structure
for
next
time
was
that
you
would
review
the
map
beforehand
and
add
questions
and
thoughts
as
comments
so
be
because
we
we
didn't
have
time
to
to
do
all
of
that.
What
we're
going
to
do
now
is
I'm
going
to
first
we're
going
to
have
five
minutes
where
everyone
reviews
the
user
journey,
and
you
can
add
questions
or
thoughts
as
comments.
A
A
If
sasha
does
feels
things
or
experiences,
what
should
we
research-
and
this
is
basically
for
us
to
understand,
of
course,
we're
doing
this
without
any
research.
So
we
already
know
some
things
that
you
know.
We
have
very
high
confidence
that
sasha
does
and
feels
and
and
experiences
certain
pain
points.
But
what
about
other
things
that
we
thought
hey?
Maybe
for
me.
A
I
think
this
could
be
it,
but
I'm
not
sure
so
it'll
be
interesting.
If
we
did
more
research,
even
you
know
just
to
find
other
related
feelings
or
pain,
points
or
opportunities
to
improve.
So
this
would
be.
The
first
part
is
five
minutes
in
silence
where
everyone
would
review
the
map
and,
as
I
said,
add
questions,
thoughts
as
comments.
A
If
you
want,
you
can
even
add
more
stickies
as
you
go
through
it
things,
if
you
remember,
but
the
most
important
thing,
as
I
said,
is
to
think
about
which
ones
you
have
the
least
confidence
on,
and
it
can
be
your
stickies
other
people's
stickies.
It
doesn't
matter
and
then,
after
that,
what
we're
going
to
do
is
we're
going
to
have
around
25
minutes
where
we
will
go
through
the
comments.
A
If
there
are
any
and
also
I
would
invite
each
person
to
share
which
stickies
you
have
the
least
confidence
on,
and
you
will
verbalize
and
say
hey,
I
don't
know
for
this
one.
I
don't
I'm
not
so
sure
that
this
is
something
that
sasha
is
is
feeling.
A
A
Okay,
great
so,
as
I
said,
five
minutes
to
review
what
we
have
here
today
add
questions
or
comments
or
thoughts
as
comments,
add
more
stickies
and
ultimately
think
what
you
don't
have
a
lot
of
confidence
on,
I'm
going
to
set
the
timer
and
I'm
for
five
minutes
with
a
let's
see
a
cuckoo
sound
and
I'm
also
going
to
share
a
bit
of
music
background
music
to
help.
You
think-
maybe
I
don't
know,
let's
see,
enjoy.
B
B
B
B
A
Do
people
want
a
bit
more
time
to
review?
Would
that
be
helpful.
B
A
Okay,
so
now
let's
go
through
and
I'm
going
to
set
the
timer
for
this
to
to
20
minutes
to
sorry
10
minutes
and
I'm
going
to
review
each
comment
that
was
made
to
see
if
there
are
more
discussion
that
we
want
to
have
about
that
specific
comment
before
we
then
share
what
we
have
a
lot
of
confidence
on
or
the
least
confidence
in
this
case.
So
let's
open
the
comments
all
right.
So,
let's
start
by
this
one
by
visiting
rhino,
I
don't
know
who
visiting
rhino
is.
C
B
D
A
C
A
So
david
said
that
different
teams
have
different
way
of
linking
requirements
and
also
can
also
have
distinct,
different
workflows,
making
this
certainty
difficult-
and
this
is
related
to
the
action
of
reading
the
issue,
description
and,
I
think,
yeah
reviewing
the
task
requirements.
A
E
I
think,
from
my
end,
that
could
just
highlight
an
opportunity
across
teams
or
stages
to
look
at
a
more
consolidated
workflow,
for
you
know
even
how
we
approach
issues
to
just
offer
some
certainty
in
workflow,
so
developer
from
team
to
team,
or
maybe
contributors
have
just
a
little
bit
more
certainty.
A
Okay
next
comment:
let's
see
also
from
from
david's
trying
to
establish
the
correct
uri
knowing
who
to
at
mention
knowing
where
to
check
the
docs
for
processes
yeah.
This
is
one
pinpoint
about
entire
reading
the
entire
discussion
to
understand
the
scope
yeah
anything
anyone
would
like
to
add.
A
Right,
moving
on
for
this
pain
point
need
to
clone
repo
locally
to
search
the
code
of
line.
I
also
personally,
I
thought
this
one
was
interesting
and
then
david
said
it's
an
opportunity
for
to
better
yeah,
get
the
capabilities
in
the
repositories
and
and
try
to
improve
on
them
yeah.
I
thought
I
thought
this
was.
What
is
your
personal
experience
david
with
with
this.
E
And
this
to
me
highlights
an
opportunity
over
on
my
team
side.
I
think,
funnily
enough,
with
the
some
of
the
editor
capabilities
to
be
able
to
grep
a
repository
without
needing
to
clone
it
locally,
because
that's
that's
a
use
case
I
run
into
sometimes
I
want
to
find
a
function
as
a
developer.
Sometimes
I
want
to
find
a
class
or
a
method
within
a
file,
and
that
can
be
quite
difficult
to
search
for.
F
Just
adding
to
that,
that's
something
that
works
extremely
well
in
one
of
our
competitors
platforms,
the
search
from
the
web
ui
and
it
you
know,
it'll,
ask
you:
do
you
want
to
search
in
the
repo
or
in
in
the
across
the
whole
site?
I
think
it
is
or
the
group
so.
F
A
Exactly
all
right,
then,
for
this
action,
toggle
back
and
forth,
he
copy
parts
from
original
issue
and
andrei
asks.
I
feel
this
is
a
trivial
action
not
worth
optimizing
for
no.
C
Yeah,
I
was
just
as
I
was
reading
through
all
these.
This
felt
like
something
too
it's
like
at
the
level
of
just
putting
things
on
the
screen
right
and
I
feel,
like
it
kind
of
stood
out
a
little
bit
as
too
too
much
detail.
Guys
talking,
talking
back
and
forth
could
be
just
scrolling
right.
So
I
feel
like
this.
Would
this
is
kind
of
hinting
at
one
of
the
ones
that
I
feel
weakest
about.
D
D
A
Yeah,
no,
that
makes
sense
yeah.
I
think
I
think
there
it's
yeah.
I
agree,
it's
a
trivial
action
it.
It
does
feel
like
we
haven't
optimized,
so
we
have
optimized
to
break
out
the
discussions
from
a
merge
request
into
separate
issues,
but
we
haven't
optimized
this
where
you
have
a
big
issue,
and
now
you
want
to
break
down
into
smaller
issues.
Maybe
your
you
know
intention
is
to
create
an
epic,
for
example,
for
all
of
those.
D
I
I
know
exactly
where
this
came
from.
I
think
this
was
partly
my
personal
thing
of
going
back
and
forth,
but
also,
I
think
I
was
swayed
by
a
competitor's
kind
of
flow
where
you
just
highlight
something,
and
then
you
like,
create
a
new
issue
and
then
they
take
that
text
and
then
pump
it
out
as
the
issue
description
in
in
that
kind
of
scenario,
that's
where
I.
F
Slightly
related,
but
on
the
subject
to
going
back
and
forth,
one
thing
I
find
challenging
is
okay,
so
we
have
our
to-do's
and
you
know
you
can
easily
find
things
from
there
and
of
course
you
can
bookmark
content
in
you
can
get
lab
using
regular
web
bookmarks,
but
there's
no
kind
of
super
easy
way
to
find
kind
of
what
you
had
worked
on
and
if
you're
trying
to
link
multiple
issues
that
aren't
actually
linked.
F
So
I
think
it
would
be
awesome
to
have
some
type
of
bookmarking
inside
of
the
application
somewhere,
that's
personal
to
yourself
and
in
fact
I
actually
opened
an
issue
on
this
some
time
ago.
Yeah,
it's
just
that
you
somehow
you
don't.
Sometimes
you
don't
want
to
actually
connect
the
issue
or
you
don't
want
to
link
it
in
the
text,
but
you
you
need
to
have
that
connection
to
work
on
it.
D
Yeah
so
there's
a
desktop
app
called
git
dock
and
that
was
created
by,
but
you
could
use
that
for
recently
viewed
issues.
He
he
was
experimenting.
He's
actually
experimenting
this
to
see
how
often
it's
used,
because
yeah
bookmarking
is
a
big
thing,
but
yeah.
If
you
want
it
just
sits
at.
F
D
A
Wrap
up
the
the
final
comments
that
we
have
here,
so
this
is
where
we
already
saw
this
one.
Then
david
commented
on
this
pain
point
every
back
and
forth
can
take
hours
discovered
time
zones
can
be
different
time.
Zones
can
be
hard
to
discover
anything
else
that
anyone
would
like
to
add
to
this.
One.
C
I
added
something
somewhere
else
about
making
the
visibility
of
the
online
status
more
visible.
I
feel
like
there's
some
opportunities
there
for
improvements,
but
I
don't
think
that
now
is
the
time
to
discuss
it,
but
I
feel
like
it's
related
to
this,
the
back
and
forth,
and
what
we
can
do
to
mitigate
that
yeah.
It's
a
good
point.
A
A
Let's
see
this
one
in
the
final
seconds
we
have
left,
this
is
the
positive
feeling
that
people
that
sasha
will
have
when
she
feels
supported.
When
an
issue
is
properly
described
and
under
a
question,
can
we
discuss
some
ways
to
reward
the
author
when
creating
any
description?
A
B
E
This
one
is
really
quite
cool
the
three
seconds
what
I've
noticed
is
on
merges
in
the.
E
Very
quickly,
on
the
merges
on
the
singular
checkbox
now
we
have
to
say
look
I've
gone
through
the
requirements
and
this
merge
meets
the
requirements,
we're
getting
much
higher
engagement
than
we
used
to
on
the
you
know,
myriad
of
different
different
points,
and
I
think
that
that
is
just
down
to
it's
a
nice
psychological
thing
for
an
author
to
be
yeah.
I've
read
this:
this
merged
check
the
box.
This
is
good,
and
maybe
that
kind
of
relates
to
this
in
a
slight
way
of
feeling
as
a
completion
for
a
correctly
written
description.
A
All
right
cool,
so
now
what
we're
going
to
do?
We
haven't
had
time
to
review
all
of
them,
but
feel
free
to
do
it
in
your
own
time,
if
you'd
like
so
now,
what
we're
going
to
do
is
I'm
going
to
ask
each
one
of
you
not
in
a
particular
order
to
share
which
stickies
you
have
the
least
confidence
on
and
we'll
just
share
one
begin
in
the
beginning,
so
pick
the
one.
A
You
have
the
least
confidence
on
and
explain
why
and
if
we
have
time
we
will
go
and
and
see
other
cities,
but
for
now
one
sticky
per
person
and
I'll
give
five
minutes
per
person
to
do
that.
So
let
me
start
the
timer
and
I
don't
know
randomly
sean.
You
can
go
first
because
you
were
the
first
person
to
join
the
call
thanks.
A
If
you'd
prefer
for
me
to
ask
someone
first,
while
you,
while
you
take
a
bit
of
time
to
to
look
into
them,
that's
also
okay,.
A
Okay,
okay,
no
worries
so
let's
restart
the
timer
and
who
has
maybe
that's
better.
Who
has
a
a
sticky
they'd
like
to
to
talk
about.
E
E
You
know,
even
as
somebody
who
uses
the
tool
quite
frequently,
I
tend
to
get
lost
on
what
I've
been
doing
and
where
I've
been
and
what's
in
progress
and
what's
not
in
progress
and
things,
various
progress
tends
to
be
shared
across
a
myriad
of
things,
issues
epics,
I
have
stuff
in
external
docs
things
are
backlinked,
some
stuff
is
buried
in
snippets.
E
I
think
I
have
a
wiki
somewhere,
that's
documenting
something
so
there's
an
awful
lot
going
on,
but
tying
that
together
and
solidified
overview,
which
is
really
easy
to
navigate,
I
think,
is
something
we
don't
currently
have
and
that
can
be
challenging
for
users
specifically
new
users,
because
they're
going
to
have
to
take
a
lot
of
time
to
up
skill
and
how
to
navigate
the
products.
E
A
Right,
thank
you
david
for
sharing
that
good
news
is
that
we
already
have
a
team
looking
into
it.
A
A
E
One
question,
then
that
is,
I
suppose
the
inverse
of
this
is,
if
you
didn't
have
a
dashboard
for,
for,
let's
say
some
reason:
a
dashboard
doesn't
come
to
fruition.
E
What
other
opportunities
do
we
have
to
improve
the
visibility
of
your
in-flight
tasks
in
gitlab
as
the
ui
currently
stands,
and
like
things
like
sean
had
mentioned,
you
know
like
being
able
to
bookmark
parts
of
an
issue,
might
be
very
helpful.
I
know
in
a
competing
tool.
One
thing
I
very
much
like
in
issues
is
subtasks
that
you
can
create.
Often
issue
is
a
single
source
of
truth
and
it
makes
navigation
a
little
easier,
but
yeah
that
would
be
a
question.
I'd
throw
out.
A
Yeah,
so
that's
a
good
one.
Any
other
stickies
you'd
like
to
to
share
that
you
don't
have
a
lot
of
confidence
on
it
can
be,
can
be
any
kind
of
sticking
even
actions
or
steps.
It
doesn't
matter.
E
In
that
case,
the
only
other
one
I
have,
which
is
really
really
related
to
which
is
really
really
related
to
this.
Where
does
it
go?
Let
me
try
and
find
it.
E
Here
reading
the
entire
discussion
to
understand
the
scope:
this
is
something
that
I've
experienced
and
if
I
was
sasha
and
I
specifically
had
come
to
the
project
with
a
little
less
experience
or
understanding
the
dynamic
in
a
team.
Sometimes
it's
very
easy
to
get
lost
in
awful
long
discussions
that
take
place
on
issues.
It's
very
hard
to
gather
what
the
correct
context
is,
especially
if
you're
a
newcomer,
maybe
you've
just
been
at
it
in
the
middle
of
a
conversation
thread.
That
is
15
comments.
Long
and
some
of
these
comments
are
quite
meaty.
E
E
So
there
might
be
an
opportunity
for
us
to
look
to
inject
context
into
our
discussions
a
little
bit
to
try
and
help.
Just
you
know,
hitting
the
ground
running
a
bit.
F
Yeah,
that's
definitely
an
issue
david
when
the
when
the
issue
is
old,
right
and
there's,
there's
really
like
a
long
thread,
some
of
which
is
kind
of
possibly
not
relevant
anymore,
and
then
it's
the
ssot
may
or
may
not
be
updated,
and
it's
just
kind
of
quite
difficult
to
see.
A
Right
exactly
exactly
all
right.
Thank
you
david.
I
thank
you
sean
also
for
for
commenting
any
who
else
wants
to
to
share.
D
You
can
pick
me:
okay,
the
part
where
I'm
not
too
sure
is
this
one
step
that
I
put
in
here
I'll
put
a
black
dot
on
the
page
in
the
task
under
yeah
yeah.
So
let's
monitor
emails
for
others
of
feedback.
D
This
one
I
I
wrote
because
this
is
how
I
operate
like
with
my
to-do's
and
the
merge
requests
like
notifications
on
the
top
that
it
doesn't
like
once
you
hit
a
certain
number
like
me
and
like
it's
just
99
and
like
it
stays
like
that,
so
I
don't
know
if
I
got
a
feedback
on
anyone
and
I
kind
of
use
the
email
as
a
way
to
see
if
I
got
feedback
from
a
review
or
like
a
pipeline
feeling
or
something
like
that.
D
But
I
don't
know
that's
just
a
me
thing
or
you
know,
outside
people
actually
use
art
to
and
kind
of,
the
merge
request
personally
to
get
feedback
on
pipelines
and
stuff
like
that.
A
Yeah
completely,
I
I
can
I
can
relate
to
that.
I
think
many
of
us
can
relate
to
it.
Anyone
wants
to
to
comment
on
this
one.
C
A
We're
is
we're
supposed
to
to
talk
about
the
ones
that
we
have
the
least
confidence
on
the
ones
that
we
think
we
should
do
more
research
or
that
we
are
unsure
if
sasha
actually
experiences
that
like
do,
they
does
sasha.
Do
that
think
or
feel
in
that
way,
or
is
there
a
gap
here
somewhere
that
we
don't
know
exactly
what
sasha
does
in
between
these
moments,
and
so
we
need.
C
A
A
Okay,
michael,
do
you
want
to
share
any
other
stickies
that
you
don't
feel
a
lot
of
confidence
on.
D
There's
like
a
whole
area
of
like
address
peer
feedback
and
stuff
like
that,
where
it's
kind
of
like
we
didn't
add
any
tasks,
so
I
don't
know
if
that's
just
because
we
were
unsure
or
yeah
it's
a
whole
area
of
emptiness.
So
for
me,
that's
for
me
personally,
like
I'm
not
too
sure,
but
so
you
mean
this.
This.
B
C
Can
I
speak
about
one
very
quickly
yeah,
do
you
track
my
brown
mouse
or
what
no,
I
just.
A
Sure
is
it
something
that
you
want
to
share
in
in
relation
to
what
michael
was
saying
or.
C
C
I
cough
is
that
this
particular
thing
like
could
be
essentially
looked
at
from
the
perspective
of
a
global
dashboard
or
like
the
whole
task
that
I'm
following
or
it
could
be
something
much
more
granular
about.
What
are
the
reviews
that
I
currently
have
in
flight?
C
What
are
the
mrs
that
I
have
currently
waiting
for
reviews
so
and
that
alludes
a
little
bit
to
the
the
solution
to
heart,
but
maybe
that
would
be
part
of
the
research
then
to
validate
whether
this
is
a
generic
need
to
have
a
bird's-eye
view
of
my
ongoing
work
when
I'm
executing
whether
it's
a
code
review,
whether
it's
the
authoring
of
a
solution
and
and
the
board-like
view
here-
was
hinting
at
a
sort
of
a
board
of
mrs
under
my
purview.
C
So
the
ones
that
require
my
attention
as
we're
working
on
right
now
would
be
something
like
providing
a
way
to
see
a
board
for
them
like
we
have
for
issues,
but
for
for
merger
guests
that
are
under
my
radar,
not
not
necessarily
the
ones
I
created,
but
the
ones
that
I'm
involved
in
actively
as
an
assignee
or
or
viewer.
C
But
I
thought
I
just
wanted
to
put
that
push
a
little
extra
and
researching
this
further.
F
That's
a
that's
a
great
point,
andre
because
in
fact,
if
you
comment
or
you
know
otherwise
participate
in
an
issue
or
an
mr,
you
get
an
email
about
it,
even
if
you're
unassigned
from
it,
but
we
don't.
As
far
as
I
know,
we
don't
have
any
other
way
to
access
it.
C
I
don't
think
we
can
so
you'll
be
so
the
way
I
envisioned
this
would
be
like
sort
of
a
board
that
would
be
having
some
sort
of
checkboxes
where
you
could
select
emerging
questions
that
I've
I'm
reviewing
I've
authored,
I'm
a
participator
in
and
then
you
could
just
toggle
that
on
and
off
it
could
be
a
filter.
It
could
be
something
else
but
yeah.
F
So
yeah,
so
we
we.
We
already
have
a
lot
of
the
information
right
because
we
have
the
subscribing
to.
C
A
All
right,
yeah
sure,
is
there
any
other.
Stick
you'd
like
to
share
or
not
so
much.
A
That's
that's
more
than
okay.
Let's,
let's
stop
the
timer
michael!
I
don't
know
if
you
had
any
other
you'd
like
to
discuss
or
if
it's
it
was
mostly
those
those
that
area
that
we
were
seeing
before,
that
you
weren't
sure
yeah.
D
I
I
don't
have
any
more
to
add
for
the
confidence
of
all
the
stuff.
A
F
Well,
in
fact,
I
just
added
I
just
added
a
sticky,
just
as
we
were
talking
about
this,
it's
kind
of
an
opportunity.
So,
if
you
follow,
can
you
see
my
screen?
Can
you
see
yeah
yeah?
So
this
is
somewhat
related
to
the
discussion
we're
already
having,
but
I
personally
use
the
commit
history
or
the
you
know,
the
the
the
heat
map
against
my
idea,
the
activity
yeah.
I
actually
personally
use
that
all
the
time,
because
you
know
I'm
thinking
now.
F
What
was
that
issue
I
worked
on
yesterday
or
earlier
today
and
and
so
I'll
go
to
the
the
day.
You
know
usually
it's
within
the
last
week,
because
that's
kind
of
as
far
as
I
can
probably
remember
and
then
so
that
kind
of
works
actually
as
a
history
except
it's,
it's
not
fantastic
like
some.
F
If
you,
if
there's
too
much
in
the
day,
you
have
to
kind
of
you
know
scroll
through
everything,
do
the
we're
all,
but
I
guess
it's
kind
of
that's
the
point
of
we
are
tracking
this
stuff
and
you
know,
and
we
could
possibly
expose
it
in
a
different
way.
F
A
F
A
Right,
yeah,
that
that
makes
that
makes
a
lot
of
sense.
Anyone
would
like
to
add
to
what
sean
is
sharing
here.
F
Yeah,
no,
I
think
it's
I
think
the
common
theme
is,
we've
got
an
overlooked
load
of
information
and
and
how
do
we?
How
do
we
manage
it?
How
do
we
give
our
users
tools
to
to
to
basically
look
at
the
information?
That's
already
there.
We
are
tracking
all
this
stuff
and
it's
just
it's
really
just
bubbling
it
up.
A
A
Exactly
exactly
especially
us
at
kit
lab
that
we
use
gitlab
for
everything,
so
other
companies
have
other
tools.
You
know
that
for
specific
purposes,
so
they
there's
a
separation
of
concerns.
But
for
us
it's
everything:
people,
ops,
product
development,
onboarding
everything
is
in
the
same
thing.
So,
okay.
A
Exactly
exactly
all
right,
so
let's
stop
the
timer,
then,
if
no
one
has
anything
else
they'd
like
to
share.
A
So
that's
also
valid,
and
one
thing
I
I
wanted
to
to
share
is
that
you
can
vote
more
than
once
on
the
same
sticky
if
you
want.
So
when
I
start
the
voting
session,
you
just
click
on
the
stickies
that
you
want
to
vote.
If
you
want
to
vote
more
than
once,
you
just
keep
clicking.
If
you
want
to
remove
your
votes,
you
shift
click
to
remove
it
from
sdk.
B
B
A
B
A
All
right,
so
there
was
not.
There
was
not
a
lot
of
consensus
and
that's
good.
Don't
worry,
because
we
we
have
two
other
groups
doing
the
same
thing
and
we
will
try
to
find
patterns
hopefully,
but
in
any
case
the
ones
that
had
more
consensus
were
these
three
at
the
top
improving.
What
did
I
work
on
view?
Just
something
that
we
discussed?
A
Also
monitor
emails
for
alerts
of
feedback
and
finding
similar
pieces
in
the
code
base
might
not
be
straightforward,
so
I
think
we
discussed
these
three
themes
more
or
less.
Let's
take
a
quick
look
at
these
here
feeling
supported
when
an
issue
is
properly
described,
keep
track
of
mrs
issues
via
bookmarks.
Don't
know
what
keywords
to
search
for
in
docs
improve
global
overview
of
currently
in-flight
tasks,
board-like
view
improvisability
of
online
status,
pain,
point
every
back
and
forth
can
take
hours,
another
pain,
point
getting
feedback
might
take
extra
time.
A
These
two
steps
address
peer
feedback,
fixed
standards,
failures,
and
then
we
have
a
couple
of
actions
here
or
sorry,
feelings,
not
sure
of
which
labels
that
are
required
can
tell
difference
between
label
and
team
this.
This
might
confuse
especially
people
that
are
on
boarding
on
gitlab
at
mentioning
someone.
The
list
can
be
slow
and
the
actions
send
to
it,
with
link
to
release,
notes
and
add
weights
to
issue
weight
in
sidebar.
D
Yeah,
so
I
voted
on
the
steps
address
peer
feedback,
yes,
extended
issues
as
in
the
yellow
part
underneath
them
the
actions
I
felt
like
when
I
put
their
steps
down.
I
was
like
oh
there's,
probably
a
lot
more.
That
happens
here
like
I
just
pure
feedback,
and
then
you
jump
back
into
the
like
your
local
ide.
Or
can
you
make
the
changes
directly
in
the
india
in
gitlab
and
like
fixed
standards?
Issues
is
a
very
like
editor
thing,
like
you
know,
spaces
commas,
and
things
like
that.
D
Like
just
linting
rules
like
like
how
many
of
these
standard
failures
are
because
people
are
editing
inside
the
editor
within
the
product
and
then
they
get
it.
B
B
A
A
Cool
thank
you,
michael
for
sharing.
Anyone
else
would
like
to
to
share
our
comments
on
the
results.
F
Sure
so,
there's
two
there's
two
stickies
that
are
somewhat
related,
which
is
not
sure
which
ables,
which
labels
are
required
and
can't
tell
the
difference
between
a
label
and
a
team.
So
labels
are
very
powerful.
I
think
we've
as
a
product
we've
got
a
great
labeling
feature.
It
looks
really
well,
but
I
can
imagine
you
know
for
particularly
for
someone
new
coming
to
a
project.
What
do
all
these
labels
mean,
and
this
would
be
the
same
on
client
projects?
F
What
do
all
these
labels
mean,
and
I
know
we
can-
I
think
we
can
hover
over
them.
But,
for
example,
if
you
look
at
priority
there's
about
four
different
labels
for
right,
so
I
happen
to
know
which
one
to
use,
but
how
would
someone
know
which
is
the
right
label,
and
I
guess
you
know
that
we
also
happen
as
at
gitlab,
we
use
labels
to
identify
teams,
so
that
somewhat
confuses
it
further.
F
I
wonder
if
we
have,
we
have
some
hierarchy
of
labels.
I
wonder
if
that
could
be
extended
in
some
way.
A
Yeah,
that's
very
interesting
thought
sean.
Thank
you
for
sharing
that
yeah.
One
thing
that
just
came
to
mind
when
you
were
talking
about
it
is
that
we
make
we
try
to
have
very
good
descriptions,
concise
descriptions
for
the
labels,
but
those
are
only
shown
when
you
hover
the
labels
after
they've
been
added
so
exactly
they.
They
help
you
after
they're
added,
not
when
you're,
adding
them,
which
is
probably
the
most
important
step,
is
when
you're
picking
them
and
we
don't
show
them
anywhere.
A
So
that
might
be
a
good
thing
for
us
to
look
into
yeah
and
overall,
I
agree
with
with
what
you
shared
you
know.
Labels
being
required
is
is
a
interesting
topic,
because
we,
basically,
we
developed
labels
a
lot
and
made
them
so
powerful
so
that
we
didn't
have
to
develop
custom
fields
for
issues
which
would
solve
the
requirement
part
that
you're
hinting
at.
But
anyway-
and
this
is
a
huge
topic
separate
from
this
discussion.
A
All
right:
let's,
let's
wrap
this
up-
we
don't
have
more
more
time
here.
So
thank
you
so
much
again
for
everyone
for
participating,
I'm
just
going
to
quickly
go
through
the
the
steps.
So
what
I'd
like
for
everyone
to
do
after
this
session
is
well,
while
it's
still
fresh,
if
you
can,
please
share
your
thoughts
and
learnings
from
this
activity
that
we
did
today
in
the
epic
wrap-up
thread.
A
So
there's
a
link
in
the
issue
that
you
can
find
it
or
you
can
also
look
at
the
thread,
the
epic
itself,
and
you
can
also
there's
also
another
thread
there
for
the
intro
session.
So
if
you
haven't
shared
your
thoughts
about
the
introduction
session
that
we
did
a
couple
weeks
ago,
you
can
also
find
another
thread
for
it.
A
So
there's
the
intro
session
thread
and
the
wrap-up
session
thread
and
what's
going
to
happen
next,
is
that
I'll
upload
this
recording
to
youtube
and
I'll
have
the
great
task
to
try
to
combine
the
work
that
we
did
here
with
the
work
that
the
other
groups
are
doing
into
a
single
user
journey
map
for
the
create
stage
for
this
specific
user
journey.
In
this
case,
so
let
me
see
if
I
can
celebrate.
A
Yeah
there
you
go,
we
we're
wrapping
up,
oh
confetti
and
and
before
we
part
ways,
I'm
going
to
ask
each
of
you
just
to
share
how
you're
feeling
now
what's
your
mood-
and
you
can
share
that
in
the
chat
here
in
zoom,
there's
an
emoji
picker
on
the
right
side
of
the
comment
area
and
just
share
how
you're
feeling
with
an
emoji,
good
bad.
I
hope,
excited
after
this
session
and
thank
you
again
for
participating.