►
From YouTube: Issue refactor convergence sessions 2021-05-13
Description
In this session, we explored ideas for the following opportunities: Make it more efficient to understand what’s changed / what’s new since the last time I interacted with a Collabject?
Take the outcomes of threaded discussions and efficiently capture them in the description?
Reduce the amount of context switching between Discussions - Description, Collabject - Collabject?
Related issue: https://gitlab.com/gitlab-org/gitlab/-/issues/329549
A
Thank
you,
so
I
just
want
to
preface
this
primarily
for
engineers
that
might
listen
later,
that
I'm
not
saying
this
is
final
proposal
on
anything.
This
is
just
brainstorming
and
doing
some
exploring
with
possibilities
so
I'll,
just
kind
of
walk
through
some
some
ideas
that
I've
had
so
we've
seen
this
before.
This
is
the
to-do
list
that
we
looked
at
last
time,
and
this
is
me
exploring
how
to
access
the
object
from
anywhere
in
the
product
or
possibilities
surrounding
that.
So
let's
say
that
I
have
selected
this
issue.
A
That
jeremy
has
tagged
me
into
dues,
and
maybe
we
have
this
panel
that
slides
out
to
the
right
again
still
kind
of
exploring
this
idea,
because
I
see
that
it's
a
pattern,
that's
been
kind
of
consistently
used
amongst
competitors
and
even
some
companies
that
are
solving
similar
design
problems,
but
not
necessarily
the
same
types
of
industry
problems.
So
I'll
talk
about
that
in
a
moment
as
well.
A
A
We
have
the
title
and
the
description
so
in
the
research
that
I
had
done
for
sticky
headers
in
the
past,
I
found
that
most
people
were
not
interested
in
reading
the
description.
Unless
they
had
to,
they
would
read
the
title.
They
would
skim,
maybe
a
little
bit
of
the
description,
and
then
they
would
go
straight
down
to
the
conversation.
A
So
my
thought
is.
Maybe
we
could
truncate
the
description
but
still
give
the
option
to
potentially
show
a
full
description
if
they
want
to
and
click
to
expand.
That
would
push
the
comments
down
and
they
would
still
have
to
scroll,
but
then
they
could
collapse
it
back
up
if
they
want
and
not
necessarily
have
to
have
so
much
space
dedicated
to
something
that
they
may
not
need
to
see.
But
once
in
a
while
the
conversation
section
here,
I'm
still
kind
of
working
on,
but
I
was
telling
mike
earlier.
A
I'm
a
big
fan
of
medium
and
to
me
medium
is
a
platform
for
communication
and
collaboration.
So
someone
posts
an
idea
or
an
article
or
a
concept,
and
then
people
talk
about
it,
and
so
I
like
the
way
that
they're
solving
this
collaboration,
challenge
of
they
have
the
article
in
their
case,
they
have
the
conversation
panel
come
up.
A
It's
not
visible,
though,
until
you
click
on
a
button
that
launches
it
and
once
it
launches
it,
actually
overlaps
a
portion
of
the
article
and
you
kind
of
have
this
a
top
level
conversation
thread
that
starts
to
happen.
The
responses
aren't
visible
by
default.
You
have
to
click
on
a
little
chat
bubble
to
initiate
that
view,
and
so
I
was
kind
of
taking
a
cue
from
that
by
playing
around
with
maybe
having
this
count.
A
That
shows
you
how
many
responses
there
have
been
to
this
top
level
comment,
but
you're
only
seeing
top
level
comments
in
this
thread.
If
you
were
to
click
this,
you
know
number
and
reply,
then
it
might
expand
down
kind
of
an
accordion
approach.
To
reveal
that
conversation,
I
think
they
actually
go
three
levels
deep
and
at
the
third
level
there
is
a
continue
reading
question
mark
kind
of
prompt
where
you
can
click
that,
and
it
replaces
this
entire
panel
with
that
thread,
so
you're
not
just
kind
of
going
deeper
and
deeper
and
deeper.
A
You
eventually
get
a
chance
to
say
you
know
what
I'm
so
deep
in
this
conversation,
I
want
to
just
see
just
that,
and
it
replaces
the
entire
panel
with
that,
with
the
option
to
go
back.
They
also
have
an
ad
reply
kind
of
in
that
context,
but
it's
not
the
field,
that's
visible,
all
the
time.
It's
just
a
link
and
when
you
click
the
link,
it
expands
to
show
like
an
input
field,
I'm
still
playing
with
ideas
for
this
and
for
layout
for
that
not
necessarily
sold
on
those
concepts.
A
But
I
like
the
thought
of
hiding
some
of
those
things
until
you
need
to
see
them.
One
challenge,
of
course,
would
be
how
to
link
to
those
conversations
if
you
choose
to
later,
and
I
think
that
maybe
you
could
have
that
on
so
one
of
the
ways
that
they
deal
with
it,
I
think,
is
actually
having
the
ability
to
view
that
comment
as
its
own
page,
which
I
have
always
felt,
was
a
little
weird.
A
But
it
is
something
we
could
explore
or
having
this
go
to
the
full
detail,
version
of
the
page
and
drop
down
similar
to
what
we
currently
have.
So
that's
another
possibility
there
also
through
an
emoji,
but
we
could
also
include
the
thumbs
up
and
thumbs
down
and
have
some
other
options
related
to
that
specific
comment
as
well.
A
I
hid
the
maintainer
and
I
guess
the
the
emoji
was
the
only
other
piece
and
I
thought
maybe
that
could
reside
either
in
the
person's
little
tag
that
pops
up
when
you
hover
over
their
name
or
even
be
accessible
from
like
a
detail.
Section
related
to
this
comment,
but
I
don't
know,
I
think
it's
more
related
to
the
person
than
to
the
comment.
So
something
tied
to
their
name
makes
a
little
more
sense
to
me,
but
again,
that's
another
piece
of
content
that
I
wonder
if
it's
valuable
enough
to
see
all
the
time.
A
This
is
just
kind
of
showing
a
way
that
maybe
we
could
have
access
to
some
of
the
most
important
pieces
which
it
might
be
debatable
if
these
are
the
most
important.
So
I'm
happy
to
discuss
that
as
well,
but
in
kind
of
what
I'm
calling
an
action
bar
type
of
approach.
So
I
know
we've
had
people
ask
about
being
able
to
switch
between
issue
types.
A
My
my
goal
with
this
would
be
to
find
a
way
to
separate
out
the
core
pieces
of
a
call
object
which
I
would
see
as
being
the
title
and
the
description,
and
maybe
the
issue
type
from
all
of
the
other
things
that
may
or
may
not
be
specific
to
that
type.
And
so
in
that
case,
if
you
were
to
change
the
type,
then
maybe
you
would,
you
know
immediately
change,
just
those
things
just
the
type
itself
without
impacting
those
things
unless
you
had
specified
something
data
related
that
was
unique
to
that
type.
A
So
if
you
have
an
incident
and
you
added
in
a
link
that
is
a
component,
that's
specific
to
incidents,
you
would
get
perhaps
a
prompt
that
says
you've
applied
something
that's
unique
to
this
issue.
Type
or
clabject
type
you'll
have
to
lose
those
changes
if
you
switch
to
another
type,
but
I'd
love
for
it
to
be
that
easy,
because
I
think,
as
we
add
issue
types,
it's
going
to
become
more
of
a
challenge
for
people
to
be
able
to
and
more
of
a
need
for
people
to
be
able
to
make
that
switch.
A
A
The
emojis
is
opening
the
emoji
panel.
I
haven't
yet
solved,
for,
if
you
add
in
a
bunch
of
emojis,
we
currently
just
show
all
of
them
in
a
line.
My
thought,
maybe
is
that
you
could
show
them
somehow
in
this
panel,
maybe
above
or
below
the
search,
something
that's
kind
of
segmented
out.
But
again
I
don't
know
if
that's
something
that
people
really
want
to
see
all
the
time,
but
we
could
have
it
launch
in
a
larger
view,
if
we,
if
we
want
to
labels,
this
is
not
my
proposed
layout
for
the
labels.
A
This
is
just
again
a
way
of
kind
of
taking
what
we
currently
have
in
the
sidebar
and
putting
it
into
a
condensed
space
to
show
that
they
could
see
the
labels
that
are
related
to
this
issue
or
collab
check
and
manage
those
in
some
sort
of
little
panel
assignees.
I've
got
two
listed
here.
My
thought
is
that
either
we
could
just
show
one
and
show
a
number
or
we
could
maybe
go
up
to
like
three.
If,
by
chance
there
are
more
than
three
and
show
a
number.
A
If
there
are
more,
however,
I
don't
think
we
usually
have
that
many
and
it
might
make
more
sense
to
just
show
one
person
and
then
plus
two
more
or
something
like
that
to
signify
that
there
are
others,
and
then
the
plus
button
here,
of
course,
to
show
that
you
can
either
manage
or
create
those
people.
From
this
section,
this
arrow
would
launch
in
a
new
view.
I
haven't
yet
explored
how
I
want
to
maybe
adjust
the
layout
in
that
view,
but
I've
got
a
lot
of
ideas.
A
B
B
B
A
A
The
third
one
in
this
context
is
reduce
the
amount
of
context,
switching
between
discussions,
description,
collaborate
and
kind
of
the
back
and
forth.
So
in
that
case
again
by
having
the
fixed
approach
back
up,
I
think
that
this
reduces
the
need
to
go
back
and
forth
and
scroll
up
and
down
a
lot
again.
A
The
other
piece
that
I
didn't
show
here
was
this
little
piece
here
so
having
the
ability
potentially
to
select
a
portion
of
a
comment,
and
then
this
little
tooltip
feature
we
currently
have
in
the
handbook.
So
you
can
select
a
line
in
the
handbook
and
a
little
feature
pops
up
that
lets
you
tweet
that
line
or
share
it
in
some
way.
But
maybe
in
this
case
we
would
have
the
ability
to
click,
add
to
description
and
they
could
potentially
have
a
prompt.
That
says,
would
you
like
to
add
a
title
to
this?
A
Like
here's
proposal
or
hear
solution-
and
interestingly,
I
heard
an
almost
identical
request
from
an
engineer
earlier
today
that
while
we
were
reviewing
an
mr,
he
said
I
wish
I
could
just
take
your
comment
and
just
throw
it
in
the
description
really
quickly
and
not
have
to
like
copy
and
paste
and
update
it.
So
this
was
another
way
to
try
to
address
that
particular
need.
A
Would
you
just
see
that
popping
in
at
the
bottom
of
the
current
text,
in
the
description
see
what's
specifically
popping
in
at
the
bottom,
the
tooltip
or
something
else,
this
sentence
that
tori
wrote?
If
I
were
to
say,
add
to
description?
Would
it
just
drop
it
in
as
the
last
line
in
the
current
description,
or
would
you
select
where
that's
what
I
would
imagine
probably
for
an
mvc,
and
maybe
there
would
be
some
way
visually?
We
could
highlight
it
or
denote
that
it
was
added
in
from
a
comment.
A
Eventually,
it
might
be
great
if
we
could
have
them
kind
of
have
a
way
to
choose
where
it
goes
in
the
description.
Obviously,
some
of
our
descriptions
get
really
long,
but
I
think
a
little
bit
more
exploration
would
probably
be
beneficial
in
terms
of
functionality
for
that,
but
for
high
level
discovery.
That's
kind
of
what
I'm
thinking
the.
A
Like
selecting
almost
like
a
list
of
sections
that
are
in
the
description,
just
drop
it
into
one
of
the
sections.
Well,
we
did
have
someone
ask
about
that
in
the
jobs
to
be
done,
research
they
had
said.
I
wish
there
was
a
way
that
I
could
just
choose.
This
is
going
to
be
the
proposed
problem.
This
is
the
proposed
solution
and
you
know
be
able
to
just
kind
of
fill
in
the
blanks
which
I
think
we
try
to
accomplish
with
templates,
but
the
templates
to
me
feel
even
still
a
bit
messy
to
interact
with.
B
D
Me:
okay,
yeah,
okay,
weird
it's
just
my
computer,
just
really
slow
yeah
I'll
skip
over
some
of
this
stuff
just
playing
around
with
like
how
to
create
the
thing
first
and
then
kind
of
like
the
different
ways.
You
might
view
this
thing
and
thinking
about
like
the
different
flows
like
so
slide
out,
like
holly,
was
talking
about
like
what
might
be
in-line
creation.
D
What
might
need
like
either
a
full
screen
or
maybe
like
a
full
screen
modal
right
and
then
what
might
be
included
in
each
of
those
things.
So
that's
kind
of
like
thinking
about
this
create
new
and
then
also
like,
what's
in
view
and
then
thinking
about
like
okay.
What
when,
when
you
need
each
of
these
kind
of
views,
so
you
know
you
might
need
a
full
screen
when
you're
like
really
just
creating
a
whole
new
object
with
you
want,
like
all
the
metadata
attached.
D
You
know
exactly
what
you
want
to
do,
maybe
in
boards,
when
you're
refining,
breaking
things
down,
maybe
in
the
list
view
when
you're
actually
navigating
to
an
item
you
might
maybe,
instead
of
a
full
screen
like
it's
actually
not
navigating
to
the
screen.
Maybe
it's
like
a
full
screen:
modal!
That's
easy
to
just
like
exit
out
of.
D
Maybe
when,
like
I
said,
you're
like
refining,
attaching
heavily,
maybe
the
slide
out
could
be
like
a
backlog
management
view
right,
you're
going
through
a
list
and
you're
kind
of
like
clicking
around
and
just
adding
things
quickly
which
people
do
currently
in
the
boards.
But
if
we
improve
boards
and
if
we
add
a
backlog
like
a
true
backlog
whatever
that
means-
maybe
we
don't
need
this.
D
Maybe
the
slide
up
view
isn't
quite
as
important
on
boards,
but
I
would
think
it
might
be
now
the
when
you're
looking
at
like
parent
or
hierarchy
view,
so
maybe
in
the
future,
when
we
have
test
cases
like
a
little
more
mature
and
requirements
more
mature,
you
might
want
to
be
looking
at
an
issue
and
then
looking
at
all
the
test
cases
or
looking
at
a
requirement.
Looking
at
all
the
you
know,
just
any
kind
of
parented
view
you
might
want
to
be
kind
of
like
clicking
around
comparing
road
maps.
D
Probably
right,
it
would
probably
be
a
combination,
but
I
would
think,
like
a
slide-out
view,
would
probably
be
helpful.
Inline,
I
don't
know
exactly
again,
probably
if
we
have
a
backlog
management
tool,
like
our
list
view,
is
more
backlogged,
so
you're
just
like
creating
things
and
all
you
care
about.
Maybe
is
the
title
right
or
like
in
the
board
where
you
might
want
to
create
something,
and
you
only
really
care
about
the
title.
D
So
I
have
a
bunch
of
questions
here.
We
can
get
to
them
later,
but
I
try
to
think
kind
of
small
with
the
what
we're,
including
and
like
what
that
could
look
like
so
maybe
like
the
full
screen,
like
maybe
I'm
creating
something
new,
and
I
know
I
want
to
like
attach
quite
a
lot
of
things
right
now.
You
know
full
screen
model
here,
but
it's
not
maybe
navigating
me
to
another
screen.
I
could
like
exit
out
at
any
time.
Maybe
just
press
escape,
maybe
return.
D
I
don't
know
we
could
play
around
with
that.
Maybe
there's
the
default
template
here
and
again.
I
didn't
go
deep
into
this,
but,
like
maybe
it's
a
drop
down,
and
I
have
different
templates
that
maybe
I
can
create
my
own
template.
Maybe
I
can
access
save
templates
here.
Maybe
if
I
change
like,
if
I
add
a
new
field
to
this
as
I'm
creating
it,
it
changes
to
like
new
template
unsaved,
and
then
you
save
it.
D
I
don't
know
what
it
looks
like
right,
we'll
play
with
that
and
then
I'm
just
kind
of
what
could
this
include
status,
title
description,
labels
and
due
date
or
what
was
important
to
users
to
see
like
the
most
important.
So
I
included
those
and
then
thinking
about
like
keeping
it
small.
What
might
also
be
important
attachments
may
be
right.
Maybe
we
could
better
link
those
with
description
at
some
point.
D
So
if
I
could
save
it
as
a
draft
and
true
draft
management,
what
if
maybe
I'm
collaborating
on
a
on
this
thing
with
someone
else
and
I'm
like
like
hey
becca
like
what
do
you
think
about
this,
and
then
I
save
it
as
a
draft,
and
then
she
takes
it.
You
know,
however,
that
looks
like
before
creating
it.
D
So
maybe
it
wouldn't
even
be
a
creation
flow,
maybe
something
else,
but
who
knows-
and
then
I
saw
this
a
few
times-
and
I
like
it
so
thinking
about
okay,
this
is
our
prescribed
view,
but
maybe
the
user
is
like.
No,
I
just
want
it
to
be
a
slide
out,
or
I
want
it
to
be
like
this
little
like
a
little
chew
modal
that
I
could
like
drag
around
my
screen,
so
this
might
be
like
cool.
D
I
want
to
switch
to
slide
out
view,
or
I
want
to
switch
to
like
inline
or
just
like
little
pop
out
that
I
can
you
know,
move
around
so
then
slide
out
would
be
something
like
this.
I
think
it
would
include
pretty
much
the
same
stuff,
maybe
less
right,
maybe
because
it's
more
about
like
that.
Like
refining,
creating
comparing
and
then
again,
maybe
you
can
switch
back
to
that
view
and
then
inline
like,
let's
say
a
board
or
a
backlog
which
is
like
just
a
title,
maybe
even
or
maybe
title
due
date.
D
Who
knows
I'd
have
to
think
about
that
in
research
a
little
bit
but
and
then
you
wouldn't
really
be
like
switching
views
here,
because
it's
like
no
like
you're
doing
it
in
line.
That's
that's
what
we're
prescribing
so
playing
around
with
that.
Like
I
said,
I
have
a
lot
of
questions
and
things
I
might
want
to
explore.
D
A
B
B
C
Switching,
that's
that's
why
I
get
fatigued
at
the
end
of
the
day
when
I
work
at
gitlab,
because
of
that,
so
it's
a
real
real
thing,
I'll
only
take
30
seconds,
because
I
only
had
20
minutes
to
do
this,
but
I
just
I'm
literally
starting
with
the
title
and
discussions
in
the
description,
and
I
was
thinking
about
it,
and
I
don't
think
that
I
want
there
to
be
any
difference
between
creating
the
thing
and
editing
the
thing
or
really
even
reading
the
thing.
I
just
want
it
to
be.
C
Like
one
thing,
so
I
don't
have
to
context
which
right
so
when
I
create
start
more
or
less
click
the
button,
wherever
I
click
the
button
to
create
a
new
object.
This
is
sort
of
what
I
see.
This
is
like
blank
slate
that
has
a
title,
a
place
for
description,
just
comment,
and
I
can
click
inside
the
title
to
start
editing
it.
C
I
can
click
it
inside
the
description
to
start
editing
it
and
then
once
I
sort
of
do
that,
then
I
I
was
playing
around
the
side
by
side
view
largely
because
you
could
either
have
two-thirds,
be
the
conversations
or
put
the
conversation
on
the
left
in
the
description
on
the
right.
But
I
want
to
start
exploring
some
of
the
things
where,
if
I
click
on,
let's
say
a
linked
comment
or
whatever
in
a
discussion,
it
sort
of
overlays
somewhere
that
context
over
the
left
or
like
switches
that
out
with
some
different
kind
of
content.
C
So
that
way,
I
don't
have
to
leave
the
thread
to
kind
of
get
that
relevant
information
still
playing
around.
But
the
idea
of
having
the
description
side
by
side
with
the
conversation
is
also
appealing
to
me
as
a
product
manager
because
then
like
as
I'm
going
through
here,
that
the
holly's
idea
of
copying
something
in
the
description
would
be
great.
C
I
could
even
drag
and
drop
a
comment
in
the
description
to
create
a
reference
to
it
automatically
with
like
a
title,
there's
all
sorts
of
different
things
you
can
do,
especially
if
these
they
can
scroll
independently
of
each
other.
So
that's
all.
I
have
right
now
I'll
keep
playing
her
outfit,
definitely
not
as
cool
as
the
people
who
get
paid
to
design
for
a
living.
But
let's.
A
Issues
are
where
I
spend
a
lot
of
time
doing
that
deep
focus
work,
and
I
would
imagine
it's
true
for
a
lot
of
our
customers
as
well-
maybe
not
everybody,
but
I
love
the
thought
of
having
like
a
very
simplified
view
of
an
issuable
oracle
object
that
doesn't
even
have
maybe
the
navigation
or
any
of
that
stuff.
It's
just
kind
of
like
that,
medium
page.
That's
just
white
space
and
the
details
you
need,
but
you
can
toggle
everything
else
on
or
off
in
terms
of.
A
I
pulled
mine,
I'm
frustrated
by
the
flow
here,
because
I
wanted
to
talk
more
about
the
other
part
at
the
beginning,
but
I'll
I'll
think
about
it.
Async.
I
wanted
to
just
mention
that
the
side-by-side
view,
I
think,
would
be
really
cool
like
when
I'm
plugged
into
a
monitor,
but
like
the
majority
of
what
I
do
is
usually
on
my
13-inch
mac.
So
I
can't
stand
like
the
sidebars
eating
up
my
real
estate
as
it
is
so
just
something
to
think
about.
B
B
So
next
item
shall
I
set
up
two
more
of
these
for
tuesday,
thursday
next
week,
two
more
so
this
is
the
last
one
in
this
series,
but
I
think
we're
we
just
started
doing
what
I
intended
for
us
to
do,
which
is
to
share
visual
things,
and
so
I'd
love
it
if
we
could
set
up
two
more
for
next
week
unless
someone
is
like
no
do
not
want
to
anyone
feel
strongly
about
it.
It's
okay!
If
you
do.
B
You
know
I
threw
all
the
effort
to
make
a
retro
board
during
this
conversation,
so
I'm
just
getting
used
to
template,
but
yeah.
If
you
want
to
do
a
retro,
let's
do
it
async
and
you
just
remember
to
mention
each
other
so
that
we're
we're
getting
notified
and
we
go
to
the
go
back
to
the
mural
and
that's
about
it.