►
From YouTube: Plan stage weekly - 2023-02-23
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
All
right
welcome
plan
stage,
weekly
February,
25th
or
a
third
looks
like
Julian
has
the
first.
A
C
Yeah
I'm
in
like
five
seconds
so
for
my
screen.
C
C
C
So
one
thing
is:
if
you
go
to
the
production
like
and
then
type
some
quick
action,
it
will
work,
but
that
goes
through
like
actually
the
quick
action
service
for
issues
like
locally.
Actually,
this
goes
through
the
work
item
service,
so
it
correctly
auto-complates
the
available
creactions
and
Etc
yeah.
C
E
E
It
was
an
error.
Was
it
an
error
message.
E
C
C
Only
if
I
only
type
like
no,
it
doesn't
so,
let's
say
bluebar,
so
there's
only
quick
action
here
right.
So
there's
no
note
that's
being
generated
for
this
particular
scenario.
Yes,
when
I
hit
comment,
it
just
warns
you
that
you
just
change
the
title
to
something,
but
there.
D
C
C
Right,
that's
because
in
the
back
then
well
yeah,
so
the
quick
actions,
it
kind
of
gets
processed
by
two
different
services
for
notes
like
it
actually
correctly
embeds.
All
the
you
know,
extra
messages
that
get
generated
in
the
process-
and
you
know
on
the
front
end
it
gets
displaced
for
some
reason.
For
this
note
alone
here,
okay
Let
me
show,
let
me
add
something.
E
A
Okay,
sorry
so
you're
saying
in
where
it
says:
where's,
there's
a
system
note
around
changing
the
title:
we're
not
sending
a
system
note
when
we
do
that
in
work
items
I
didn't
say
that.
Oh
sorry,
that
was
me
being
confused.
Then.
C
No,
it's
it's
just
simply
a
message,
that's
embedded
in
the
in
the
in
the
response.
There's
four,
you
know
FYI.
You
know
this.
You.
D
C
As
you
can
see,
there
is
a
system
note
right,
but
it
also
in
the
graphical
response.
There
is
an
extra
message
that
says
you
know
simply.
You
know
just
friendly
telling
you
that
you
know
your
node
only
contained
a
quick
action,
so
we
know
no
new
note
was
generally
in
the
process.
We
only
apply
the
creaction
that
was
in
the
present
that
was
present
in
the
request.
Yeah,
okay,.
A
C
C
A
Okay,
so
yeah
we're
probably
just
going
to
want
to
change
that
within
work
items
to
match
what
we're
doing
with
issues
around
the
copy
and
the
color.
E
C
F
And
I
think
that
is
the
reason
that
the
the
real
time
is
also
not
updated.
I'm,
not
sure,
maybe
because
the
system
node
should
also
be
generated,
that
the
administrator
assigned.
F
If
you
see
when
we
refresh
the
system,
node
of
administrator
change,
title
from
Hello
to
fuba
was
generated,
but
earlier
it
was
not
with
planner.
But
yes,
this
is
something
that
should
have
happened.
B
B
Responses
we
just
get
back
in
an
error
from
the
back
end
and
it's
just
the
current
one
is
styled
in
blue.
The
one
above
like
issue
notes,
is
in
an
info
box
and
we
just
take
the
contents
out
of
Errors
for
our
Command
names
or
the
command
responses
in
style.
We're
doing.
F
B
F
B
B
In
their
areas
objects
do
they
get
back
whatever
the
current
quick
actions.
Endpoint
is
the
one-on
issues.
B
F
B
C
So
let
me
look
at
that
because
I
didn't
touch
this
part
yeah,
so
my
main
work
was
around
you're.
F
C
F
A
Cool
yeah,
nice
job
and
then
so.
The
next
I
don't
know
if
we'll
work
on
it
in
1510
or
15
11.
But
the
next
iteration
of
applications
and
work
items
are
the
other.
The
remaining
quick
actions
in
both
description
and
notes.
So
just
a
little
preview
of
what's
to
come.
Yeah.
There
are
some
like
added
everything
that
we
have
currently
in
issues
to
the
issue,
to
add
the
other
quick
actions
to
to
work
items.
A
But
there
are
some
that
I
think
we'll
have
to
we'll
have
to
think
about
like
promote
and
see
how
we
handle
that,
because
of
how
closely
that's
going
to
be
related
to
to
change
type
and
to
change
type
change,
work,
item,
type
location,
but.
F
E
All
right
so
I've
been
making
some
improvements
to
work
items
UI
mostly
tasks,
but
this
one
impacts
any
work
item,
so
it
works
for
objectives
and
key
results
which
is
adding
the
IID
in
the
breadcrumb
here,
and
in
this
case
it
also
displays
in
the
model.
So
if
we
open
okay,
it
was
opening
models
when
I
was
not
sharing
my
screen
and
no
it's
not
it's
fascinating.
E
So,
if
we're
in
a
model
as
well,
so
it
works
on
the
detail
bed
page
and
on
the
model
page.
There
is
something
I've
noticed,
though,
after
the
fact
is
that
it
only
works
if
I
mean
in
the
it
was
like
that
in
the
requirements.
But
basically,
if
it's
a
parent
work
item
like
the
color
is
different
and
we
there's
no
IID.
E
So
maybe
we
might
need
a
follow-up
and
I'm
not
sure
why
the
color
is
different,
like
I
didn't
really
work
on
that
at
all,
but
it
could
also,
even
when
there's
no
parent,
we
should
probably
display
the
ID
anyway,
and
we
should
probably
match
the
color
as
well.
I
find
that
a
little
bit
confusing,
but
I
was
doing
that
when
we
didn't
have
any
ux
counterparts
so
might
have
to
chat
with
Amanda
and
Nick
about
it.
We'll
see
any
thoughts
or
questions
on
this.
A
Do
you
also
fix
the
the
modal
Focus
thingy
that
was
going
on
before.
E
E
Yeah
it
looks
like
it's
fixed
now,
so
there
was
a
combination
of
things
happening,
I
guess
in
the
end
it
looks
it
looks
fixed
so
yeah,
but
there
was
some
changes
required
directly
into
the
model
component
and
GitHub
UI.
So
it's
not
focusing
this
breadcrumb
by
default
when
we
open
the
model
anymore,
good.
A
B
E
E
A
For
sure,
do
we
know
what
the
plan
is
for
the
like
the
rest
of
the
iterations
of
the
UI
of
breadcrumbs
within
work
items
because
I
don't
know
it
still
looks
kind
of
weird
having
multiple
breadcrumbs
in
the
work
item,
detail
View
and.
E
D
So
we
we
do
have
an
issue
which
is
proposing
unifying
both
the
breadcrumbs
with
some
of
the
initial
designs.
Also
present
I
I
can
try
finding
it
and
facing
it
into
the
agenda,
because
I
I
did
see
an
active
conversation
there
from
Marshall
as
well.
Now
that
Marshall
will
be
the
ux
leadership
counterpart
for
plan
stage,
along
with
Nick
helping
the
product
planning
itself.
So
I
saw
some
comments
from
him
in
that
issue.
I'll
find
and
paste
it
in
the
agenda.
B
E
B
B
A
It's
it's
going
to
be
a
bit
confusing
when
we
combine
the
concepts
of
hierarchy
within
the
work
item
along
with
hierarchy
within
our
group
project
structure.
E
Yeah,
so
that's
actually
something
that
I
sort
of
started
talking
to
Amanda
about
was
that
currently
the
where
hierarchy,
navigation
works
is
mostly
for
breadcrumbs.
E
But
what
I
was
thinking
in
terms
of
like
when
it
comes
to
like
building
trees
of
children
and
maybe
one
day
we'll
have
siblings,
and
there
will
be
many
types
of
white
Cadence
and
such
we
should
probably
just
have
a
dedicated
widget
for
that
similar,
maybe
to
the
ancestor
widget
in
epics,
when
it's
like,
seeing
all
the
parents
and
maybe
have
a
more
visual
way
of
looking
at
it,
that
wouldn't
maybe
clutter
and
confuse
the
breadcrumb
I.
Think
that
might
be
a
good,
a
good
way
to
handle
it.
B
E
I'll
move
on
then,
so
the
other
thing
I
worked
on
related
to
tusks
is
adding
metadata
in
the
tree
on
issue
page.
So
now
we
can
see
Milestone
a
signee
and
labels
on
tasks
linked
inside
issues.
B
E
D
Variables
so,
regarding
that
key
result
showing
up
in
the
auto
completion,
can
you
confirm
if
newly
created
key
results
are
showing
up
or
not?
Because
when
we
started
working
on
adding
support
for
key
results?
Back
in
mid-December,
there
was
a
bug
where
creating
new
key
results
for
setting
its
type
as
issue
instead
of
key
result
and
that
ended
up
creating.
D
D
Yeah
I
don't
know
like
if
you
create
new
key
result,
the
type
of
that
key
result
would
be
correct,
and
in
that
case
it
may
not
show
up
in
the
auto
completion.
E
Okay,
I'll
verify
that
it
doesn't
happen
again
later
on
or
credit
occurs,
key
result
and
make
sure
it
doesn't
happen,
yeah
fair
enough,
but
we
don't
display
labels
in
relates
to
in
the
linked
items
we
display
assigning,
but
we
don't
display
labels
actually
to
answer
Donald's
question.
A
Gotcha
cool
we
have
one
of
the
widgets,
have
the
ability
to
hide
the
labels
or
is.
F
E
Yeah
I
don't
know
it
would
make
sense
to
like
sort
of
have
that,
because
the
thing
is
when
we
migrate
epics
to
work
items
we'll
be
using
the
work
item,
trees
or
the
same
as
tasks
here.
So
if
we
want
to
maintain
that
functionality
on
epic
tree
we'll
have
to
build
it.
D
Yeah
for
okrs
it
was
asked
as
a
follow-up
that
hierarchy
widget
should
have
an
ability
to
toggle
labels,
even
if
it
doesn't
persist
in
the
database
like
right
now.
If
you
look
at
child
issues
and
epics,
you
can
hide
labels,
but
it
doesn't
persist
across
page
reloads.
It
is
just
front-end
only
toggle.
A
How
do
we
pull
in
the
labels,
information
and
all
the
other
information
on
those
tasks?
Are
we
pulling
in
all
of
the
widgets
for
all
of
the
yeah.
E
So
yeah,
but
yeah
yeah,
we
are,
we
use,
fragments
it's
a
big
query,
but
now
it's
a
single
request:
it's
etching
it
on
its
own
yeah.
Maybe
we
should
have
more
to
let
up
fragments
defined,
like
maybe
one
per
widget,
and
then
we
only
pull
the
ones
we
actually
need
potentially
but
yeah.
When
there's
a
lot
of
tasks,
it
could
be
a
bit
heavy
yeah.
It's
a
good
point.
A
Yeah
tests
and
like
I'm
thinking,
if
we
do
add
the
ability
to
remove
labels
from
the
UI
or
anything
from
the
UI
here.
E
Yeah,
so
that's
also
something
when
so,
because
it's
a
front-end
only
toggle
like
it's
something
that
I
looked
into
for
roadmap.
We
fetch
the
labels,
even
when
we
don't
show
them,
because
otherwise
we
require
like
some
kind
of
full
page,
reload
or
re-request,
and
it
looks
weird
at
like
the
UI
flashes.
So
we
need
to
work
out
how
to
do
it
more
elegantly,
so
that
it's
kind
of
more
seamless
to
the
user.
A
Gotcha
makes
sense
cool,
although
I'm
glad
yeah
I
think
it's
a
good
ad
having
labels
show
up
there.
Yeah
looks
good.
E
Yeah,
it's
it
was
just
merged
this
morning,
so
we'll
hate
production
in
the
next
24
hours,
probably
all
right,
I'm
gonna,
move
on
to
conversations
instead
of
demo,
if
that's
okay,
so
this
is
pretty
early
on
I
just
started
really
diving
into
this
yesterday,
even
though
I've
been
thinking
about
it
for
a
long
time,
working
on
filtering,
like
working
on
filters
currently
is
quite
complex,
like
we
have
different
implementations
for
doing
very
similar
things,
particularly
on
issues
and
epics,
and
focusing
on
the
plan
issuables
for
now
and
so
I'm,
going
through
a
big
analysis
of
like
what's
available
on
the
back
end,
which
tokens
are
actually
implemented.
E
What's
in
common
between
all
those
things,
so
we
can
start
like
grouping
things
together,
see
what's
missing
on
the
back
end
as
well,
to
have
it
like
more
consistent
across
these
objects
so
that
we
stop
having
all
those
like
different
implementations
that
really
they
do
the
same
thing
but
they're
built
very
differently,
so
I'm
gonna
start
working
on
Spike
to
like
see
what
we're
getting
grouped
together
and
like
so
the
reason
as
well
like
what
Spike
this
really
like.
E
What
made
me
really
start
on
it,
even
though
I've
been
thinking
about
it
for
a
while
was
working
on
all
the
oil
filter?
First
of
all,
which
brings
a
whole
lot
of
new
problems
like
multi-select.
Should
it
be
unique
or
not?
It's
like
creating
problems,
which
is
the
the
Epic
that
was
linked
there,
which
is
the
undesired
behavior.
E
When
you
combine
certain
criterias,
like
some
filters
that
aren't
compatible
like
so,
we
need
to
it
needs
to
be
smarter,
but
currently
it's
such
a
mess
that
it's
very,
very
complicated
to
implement
those
like
exclusive
things
between
different
criteria
within
filter
tokens,
so
I
just
want
to
like
simplify
the
code
group.
E
Things
together,
create
utils
and
make
them
more
flexible,
easier
to
maintain
easier
to
build
upon,
like
add
new
filters,
instead
of
having
to
add,
like
we
had
to
do
it
once
they're
big
balls,
one
first
year
was
a
big
system,
so
you
have
to
do
it
like
four
times.
I
want
to
have
to
do
it
only
once
and
it's
available
everywhere
as
long
as
it's
available
on
the
back
end.
That's
that's
the
gist
of
it.
I
feel
like
I,
went
into
some
depth
in
there,
but
that's
that's
roughly
the
idea.
E
It's
kind
of
the
first
step
towards
like
a
unified,
filtered
search
for
the
products
baby
steps
So
like
feedback,
is
welcome
ideas.
Whatever
like
thoughts,
you
can
comment
on
the
Epic.
Add
things
whatever
anything's
welcome.
G
Just
to
clarify
Flory:
are
you
only
looking
at
ethics
and
issues
and
I
suppose
maybe
merge
requests.
E
As
a
result,
so
now
for
now,
but
I
know
there's
way
more
to
it.
I
have
to
start
somewhere
and
currently
in
plan
epics
and
issues
like
lists
and
Boards.
Epics
and
issues
are
already
very
Divergent,
even
though
they
basically
do
the
same
thing,
but
down
the
line.
I'm
hoping
we
can
yeah
like
extend
it
to
merge,
request
cycle
analytics
like
whatever,
so
we
could
like
I'm
happy
to
like.
E
But
the
logic
should
be
similar,
a
lot
of
things
like
or
not,
for
example
like
they
should
be
equivalent
just
building
the
the
top
layer
objects
for
those,
hopefully
is
the
same.
Implementation
on
the
back
end
can't
even
guarantee
that,
but
it
should
be
but
yeah
like
whatever
you
think
we
should
include
in
there
please,
like
add
stuff,
if
you
want
to,
if
you're
interested
in
really
unifying
it
like
Beyond,
epics
and
issues
yeah.
G
Actually
exclude
a
lot
of
the
like
currently
I,
don't
think
we
ever
filtered
by
weight
and
confidentiality,
and
things
like
that,
so
yeah
I
guess
I'll
keep
an
eye
out
on
this,
or
if
you
see
opportunity
that
you
think
you
want
to
test
something
in
possibly
a
different
area.
We
have
a
relatively
shared
set
of
filters
across
a
lot
of
analytics
pages.
G
Okay,
so
that
could
be
a
good
option
and
just
to
throw
him
under
the
bus
a
bit
I
think
kashal
and
I
both
worked
on
the
shared
filter
bar
a
little
bit
in
the
past,
but
that
was
a
couple
years
ago.
So
there
might
be
some
knowledge
you
can
throw
in
as
well.
D
Yeah,
so
filtered
search
bar
shared
app
that
we
have
is
currently
only
used
on
roadmap
and
epics
list.
Page
and
Flor
is
aware
of
it.
We
aren't
using
it
at
least
in
the
product
planning
side
of
things.
We
aren't
using
it
anywhere
else
besides
those
two
areas,
but
even
that's
itself
is
a
separate
implementation.
E
Roughly,
if
I
really
simplify
on
that
cycle,
analytics
stuff
Ezekiel,
if
you
could
send
me
some
information,
because
if,
if
there's
already
a
unified
implementation
of
it,
I
should
probably
take
a
look
before
I
even
get
started
on
issues
and
epics
like
if
I
can
just
nuke
everything
and
replace
it
by
something
already
existing.
That's
ideal.
G
Yeah
sure
I'll
dig
around
and
yeah.
Let
you
know
thanks.
A
I
wonder
if
we
should,
because
the
other
problem
we
have
with
with
the
different
filtering
is
that
we
still
have
some
tokens
that
are
like
we're
still
using
our
rest,
apis
or
other
apis
like
the
API.
Oh.
E
So
the
other
thing
that
could
be
part
of
this
unification
is
the
way
we
populate
the
suggestions
for
the
tokens,
absolutely
like
some
of
them
like
we
have
different
ways
of
fetching
labels
and
Milestones
and
such
we
should
just
have
one
and
it
should
be
graphql
and
used
it
everywhere
across
all
of
our
filter
bars.
So
that
will
be
one
of
the
things
I'll
be
looking
into.
Yes,.
A
Okay,
cool
awesome.
That
sounds
good.
Just
a
couple,
quick
notes
around
project
Management's
work
within
filtered
search
right
now,
because
we
have
a
couple
things
going
on,
but
I
know
you
know,
because
you
were
part
of
or
filtering
for
epics,
but
pong
is
working
on
multi-select
within
GL,
filtered
search
around
that
component.
So
that'll
have
some
implications.
I
think
on
this.
E
A
Then
Heinrich
is
running
a
spike
right
now
around
around
essentially
saved
filters.
A
The
concept
of
say
filters
that
we've
talked
about
for
a
while
and
that
will
also
involve
how
we
manage
or
how
we
handle
our
query
params
within
search.
So.
A
E
Definitely
things
to
be
I
was
already
aware
of
the
multi-select,
which
needs
to
happen
anyway.
So,
yes,
I,
wasn't
aware
of
the
saved
search
program,
which
is
also
interesting
and
I,
should
take
it
into
account
during
this
initiative,
the
search
the
saved
search
param
does
that
relate
to
board
scope,
or
is
that
a
new
thing.
D
So
Flory,
if
you
recall,
we
did
discuss
it
a
couple
of
days
ago
like
so
basically
serial
parents
is
nothing
but
the
concept
of
views
where
you
would
essentially
create
a
bunch
of
filters
preserve
it
and
that
view
will
be
will
be
able
to
visualize
in
different
ways
like
you.
You
can
have
same
set
of
filters
showing
up
as
a
list
of
items
or
roadmap
or
boards
Etc.
So
that's.
E
How
it
is
going
to
really
cool
so
I
should
probably
work
with
Heinrich
on
that
to
make
sure
that,
because,
like
for
example
like
in
my
initial
audit
for
this,
like
I've,
highlighted
some
gaps
in
like
certain
endpoints,
so
we
want
to
make
sure
that
that
will
all
work
together
and
that,
of
course,
the
front-end
implementation
will
work
both
with
like
existing
filters
in
the
new
unified.
Like
view
that
we
just
talked
about
so
yeah.
Like
it
I
know,
this
will
involve
many
people
across
different
teams
and
such
but
yeah
I.
A
E
Yeah
I
saw
that
thank
you,
I'll
I'll
dig
into
it
later
changes
anything
else
about
filters.
F
E
Cool,
so
next
point
is
still
online.
I
have
a
lot
to
talk
about
today.
I
just
wanted
to
quickly
mention
the
CSS
optimization
Pro
project,
because
that's
still
going
and
there's
not
much
left
but
there's
a
quite
a
few
things
that
are
related
to
project
management
that
are
left
to
do
like
some
issue,
stuff,
I'm,
not
sure,
there's
much
left
in
the
issues
here.
Some
of
them
have
been
done
actually
and
there
should
be
notes
and
projects,
and
so
I
thought
I'd
mention
it
here,
because
it
falls
under
plan
responsibilities.
E
Anyone
can
pick
anything
technically,
but
it
helps
to
have
the
domain.
Knowledge
I've
also
been
thinking
like
some
of
them,
don't
really
make
sense
to
page
ones.
Like
labels
was
initially
highlighted
when
we
started
that
years
ago
and
I'm
thinking,
it
should
just
be
moved
to
components.
Probably
so
maybe
notes
as
well.
I
don't
know,
nodes
are
across
a
lot
of
things,
so
that
could
be
a
thing
that
could
also
be
a
component
potentially,
but
there's
a
lot
like
there's
still.
E
E
Yeah
that
was
my
last
last
thing:
I
wanted
to
talk
about.
A
Awesome
am
I
next.
F
Okay,
so
this
is
already
on
production,
but
this
is
behind
the
feature
flag.
It's
the
real-time
update
for
notes,
and
let
me
just
put
it
to
newest
first,
because
then
it
will
make
more
sense
so
that
foreign.
A
At
some
point
show
your
Network
tab
too.
So
we
can
see
no
polling
calls
at
all.
F
F
So
the
comment
when
we
were
writing
a
new
comment:
there
was
what
we
would
we
did
was
we
wrote
it
to
the
cache
because
the
subscriptions
were
not
there,
so
that
has
been
removed
for
now
and
it
is
working
purely
on
subscriptions.
So
let
me
just
try
to
update
the
weight
here
and
you
can
see
that
it's
okay
yeah,
it
does
make
sense
to
show
the
network
tabs.
We
make
sure
that
there's
no
other
API
call.
F
F
So
if
I
go
to
the
application,
sorry
the
web
socket.
So
this
is
a
subscription
if
I
just
edit.
The
comment
also
here,
let
me
just
edit.
F
It's
edit
it
here
as
well.
Let
me
just
try
to
delete
one,
let's,
let's
just
ring
deleted
from
here
as
well,
and
let
me
just
update
and
label.
F
So
everything
is
real
time.
If
you
see
the
common
threads
are
closed
for
now,
but
after
that,
once
the
ux
threads
thing
is
updated.
After
that
it
will
be,
they
will
be
open
by
default,
and
then
you
can
see
their
real
time
update
here
as
well.
F
So
yeah
I
mean
editing
updating,
deleting
comments,
real-time
update
of
activities
that
you're
doing.
Let
me
just
I,
don't
know.
F
F
F
Literally,
like
pitched
in
to
make
sure
that
the
data
that
we
are
getting
for
subscriptions
in
the
same
way
that
Apollo
wanted.
So
it
was
for
me
also
a
quite
a
learning
experience
to
understand
how
this
magic
works
and
when
do
we
want
to
handle
it
manually
but
yeah,
it's
collaboration.
It's
not
me.
Yeah
foreign.
A
We
spent
our
101,
which
we
just
had
just
playing
around
with
it
and
conversing
with
each
other
in
real
time
on
a
work
item,
you.
A
C
A
Okay,
so
then
it
is
available
for
everywhere
for
everywhere,
internally,
meaning
gitlab,
org
and
gitlab.com
so
test
it
out
everywhere,
not
just
point
stage.
Please.
D
So
just
a
quick
question:
I
think
description
are
also
covered
in
in
the
real-time
updates.
Right,
like
one
can
update
a
description
in
one
page
and
someone
else.
D
Yeah
so
I'll
just
open
in
a
new
issue
to
basically
propose
support
for
multiple
cursors.
A
Oh
there's
plenty
of
issues
around
that
and
plenty
of
yeah
investigations.
That's
been
done
around
that
Simon
remind
me.
A
We
have
Conflict
Management
on
real
time
for
descriptions
in
work
items,
or
did
we
not
get
there
yet.
B
A
But
there
are
definitely
issues
around
that.
Where
Nick
has
yes
some
proposals
and
they
can
say
if
yeah.
C
A
Some
proposals
on
what
to
do
there:
okay,
cool
all
right,
any
other
questions
on
real-time
notes.
A
Okay,
let
me
do
some
a
couple
demos
here
and
I
am
definitely
just
the
messenger
here,
because
I
had
I
was
not
involved
at
all
in
the
work.
This
first
one
was
by
Kong,
which
was
just
a
if
you
recall
when
we
first
released
Tess.
We
had
the
concept
of
because
we
didn't
have
the
widget
at
the
time.
So
we
created
tasks
from
markdown
checklist.
A
We
decided
to
switch
to
the
to
the
widget
on
the
task
widget
and
created
Created
tasks
through
their
only
and
then
we
did
a
bunch
of
ux
research
on
on
the
addition
of
tasks
within
descriptions
and
we've
made
some
updates
now,
and
that
is
ready
to
we're
ready
to
be.
D
A
Okay.
So
previously
there
was
a
icon
that
showed
up
next
to
the
task
you
clicked
on
it
and
showed
the
menu
to
convert
it
to
a
task.
Now
we've
got
the
menu
on
the
far
right
side.
That's
added
there
and
there's
two
options
in
there.
One
is
to
delete
which
just
deletes
the
I
believe
it
just
deletes
the
text
from
the
or
just
deletes
the
markdown
and
then
updates
the
description.
A
And
yeah
so
just
an
easy
way
to
delete
your
tests.
That
way,
then
the
other
one
is
convert
the
task,
so
we're
gonna
do
that,
and
that
also
deletes
it
and
then
add
it
as
a
test.
E
A
Yeah,
it's
a
I've
used
it
a
couple
times
already
to
because
normally
when
I
create
tasks,
I'm
creating
a
number
of
tests
at
a
time-
and
it's
still
pretty
quick
to
do
it
this
way,
just
because
we
don't
like
when
we
create
more
and
we
don't
close
it
out,
so
I
can
just
type
it
all
there.
A
A
But
the
next
step
I
think,
will
be
a
more
efficient
way
of
bulk,
adding
tests,
whether
that
be
like
comma
separated
here
or
just
being
able
to
like
highlight
all
of
the
all
of
your
tasks
here
and
maybe
like
an
option
just
to
turn
them
all
into
directly
into
tests,
but
all
stuff
we're
talking
about.
A
Okay,
I,
didn't
put
this
in
the
agenda,
but
I
also
wanted
to
demo
something
for
Brett.
That
I
think
is
in
production.
A
Yes,
it
definitely
is
in
production,
because
Amanda
just
updated
the
org
that
it's
available,
but
on
a
we
copy.
This
issue
I
have
some
stuff
here.
Okay,
so.
B
A
Okay,
so
we
have
a
gitlab
URL
to
an
issue
there.
We
all
know
yeah
the
plus,
and
it
shows
the
title
now
I
think
we
were
calling
it
or
no,
that's
called
the
enhanced
popover
I,
don't
remember
what
this
was
called,
but
as
opposed
to
without
that,
where
we
just
showed
the
the
IID
there,
with
a
with
a
reference.
Okay
so
plus
adds
the
title.
A
Now
we
have
the
option
of
plus
s
which
stands
for
summary,
which
shows
a
bit
more
details
to
that
to
the
to
the
to
the
issue
or
to
the
URL
to
the
link
there.
So
it's
the
title:
The
assignee,
the
Milestone
and
the
health
status,
and
then,
if
something
is
not
there,.
A
I
wonder
if
the
cash
is
gonna
I'm
like
wow
instantly
removed
but
yeah
that
if
it's
not
there
just
doesn't
show
up.
A
E
E
Maybe
we
should
have
a
little
like
help
icon
on
the
text
area
or
something
and
when
you
click
it
lists,
like
maybe
the
quick
actions
and
the
little
shortcuts
and
a
few
things
like
this,
because
there
is
no
way
to
there
is
no
discoverability
for
it
at
all.
I
feel
like
we
should
add
something
to
the
text
area
I.
C
Think,
like
as
you
type
in
the
markdown,
if
we
can
detect
this
is
a
link
to
an
issue
or
something
like
that.
We
can
probably
show
a
pop
over
and
then,
if
you
want
to
type
one
plus
or
s,
it's
possible
yeah.
G
C
Or
you
can,
it
doesn't
even
have
to
pop
over
but,
like
you
can,
like
you
know,
right
above
the
markdown
field
or
below
the
subject
line,
something
like
that.
Yeah.
A
Yeah
or
like,
when
slack,
does
it
on
like
Google
Docs?
How
they'll
continue
sending
the
like
message
around?
Do
you
want
to
install
the
Google
Docs
app.
C
A
Will
add
some
nice
metadata
or
something
like
that
to
it?
So
we
could
do
something
like
that
with
the,
because
we
have
a
onboarding
or
like
a
like
a
guide
thingy
in
the
app
for
certain
features,
I've
seen
on
the
bottom
right
corner
when
we're
advertising
stuff.
A
So
we
can
do
something
like
that
like
if
we
like
you
were
saying
if
we
sense
that
they
are
or
if
we
detect
that
they
were
using
a
issue
link
saying
just
like
a
hey:
did
you
know
you
can
add
the
you
can
add
a
plus
we're
also
discussing
if
it
should
just
be
the
like.
A
We
should
show
the
title
by
default,
because
I
think
most
of
the
most
people,
if
they
knew
the
plus
existed,
would
rather
send
the
the
title
would
rather
have
the
title
shown
in
the
link,
as
opposed
to
the
the
reference
and
the
ID.
D
A
D
Installed
tried
it
for
a
while,
but
then
it
was
hard
to
adjust
my
mental
model
of
seeing
tabs
on
the
sidebar
so
abandoned.
C
I,
don't
want
to
discourage
anyone,
but
I
would
be
really
careful
like
trusting
a
new
browser.
It's
basically
another
operating
system
and
I've,
seen
scary
things
when
I
took
a
security
course
back
in
college,
like
I.
Had
this
really
smart
Professor
like
he
became
a
professor
in
like
around
like
30.,
you
know.
So
it's
like
a
genius,
and
basically
he
told
me,
like
he
told
the
class
like
the
like.
A
Like
yeah
or
browser,
though,
browser.