►
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
Cool,
so
I
think
nick
had
an
item
that
maybe
got
removed
or
deleted
because
he's
not
present,
but
alexis
did
you
want
to
carry
on
from
your
point
from
last
week
about
boards
experiments
and
small,
a
b
testing.
B
Sure
if
I
sound
like
a
robot,
I
need
to
get
like
a
wi-fi
extender
in
this
room.
It
just
may
not
sound
great
anyway.
Yeah
we're
looking
at
a
little
av
test
to.
B
This
is
a
really
old
board,
but
the
idea
of
creating
a
new
board
and
making
that
a
little
bit
more
discoverable.
So
currently
I
mean
there's
a
lot
of
things
in
boards.
We
need
to
improve,
or
I
want
to
improve,
but
to
create
a
new
board.
You
have
to
go
into
the
board
and
select,
create
new
board,
opens
the
modal
so
making
that
easier.
B
So
a
small
test
is
the
objective
here.
I'm
thinking
that
we
keep
this
within
switcher
and
just
add
in
per
attack,
who
is
using
each
that's,
that's
kind
of
what
we're
thinking
just
as
an
experiment.
B
So
looking
at
this,
it
was
kind
of
actually
really
hard
trying
to
think
of
like
the
very
small
change
here,
but
I'm
thinking
what
we
can
try
on
bc
is
edits
where
it
currently
says,
like
edit
board,
just
move
that
closer
to
the
title
of
the
board
for
now
shorten
it
to
edit
right,
because,
hopefully
they
understand
and
add
in
just
like
a
new
button
as
well
and
see
you
track
those
two
items
see
what
happens
versus
like
again
hard
to
think
very,
very
small.
B
B
The
future,
of
course,
there's
a
lot.
We
would
have
to
overhaul.
I'm
thinking,
probably
at
some
point.
This
could
be
two
rows
just
to
kind
of
give
it
some
breathing
room.
I
would
like
the
picker
to
be
like
an
actual
title
right
and
have
those
like
every
option
be
more
discoverable
in
general,
but
not
for
nbc.
B
Let
me
see
if
I
can
find
oh
and
then
like
another
idea
would
be
within
the
board
or
within
the
new
drop
down
in
projects
and
boards.
Sorry,
I
need
coffee
in
projects
and
groups.
Have
it
either
say
if
you're
in
a
project,
new
issue
board
or
if
you're
in
a
group
say
new
epic
board,
that's
just
like
a
really
quick
idea.
I'm
not
sure
we
can
keep
talking
about
that,
but
keep
thinking
about
like.
B
Is
there
better
ways
to
organize
this
information
in
that
filter
bar
improve
the
filter
bar
overall,
showing
applied
filters
and
a
better
one
if
you're
here,
but
I
don't
want
to
attach
them
here
and
confuse
this
on
dc,
but
anyway,
that's
that's
what
I'm
think
do
you
all
have
thoughts
on
like
this
really
quick.
C
C
I
think
our
filter
bar
is
like
a
challenge.
I've
used
the
filter
bar
a
lot,
and
you
know
it's
it's
nice
in
some
respects
and
it
really
holds
us
back
in
some
others.
Whereas,
like
a
lot
of
more
complicated
filtering,
filtering
interactions
usually
involve
some
sort
of
drop
down,
and
then
you
have
like
other
selectors
within
that
drop
down,
and
basically
our
our
search
filter
pattern
is
quite
unique
and
like
sometimes
I
think
I
don't
know
what.
What
am
I
trying
to
say.
C
Is
it
worthwhile
to
explore
how
our
filtering
could
work
outside
of
the
search
filter
pattern?
Are
we
still
so
tied
to
that
that
it's
impossible
to
move
outside
of
it,
because
I
I
find
similar
constraints
where
you're
like?
Oh
wow?
I
really
need
to
add
a
button
here.
I
really
need
to
like
use
these
drop
downs
in
such
as
in
such
a
small
way,
where
I
can't
read
the
specific
title,
there's
like
so
many
constraints
that
we're
having
to
deal
with
by
just
using
the
search
filter
component.
C
But
it's
it's
a
bit
of
a
nightmare,
so
my
I
know
we're
doing
mvc
and
all
that
sort
of
stuff,
but
sometimes
it's
worthwhile
to
step
outside
the
mvc
mindset
and
think
is
this
a
global,
optimization
versus
a
local
optimization,
and
if
so,
what
should
I
be
considering
that
that
didn't
go
with
your
mvc
comment,
but
hopefully
it
was
useful.
I
don't
know.
B
No,
I
think
that
makes
sense
so
you're
cutting
out.
I
don't
know
if
that
was
for
me,
but
I
think
I
got
this.
It's
just.
B
This
issue,
but
I
did
create
another
issue
and
there's
like
a
few
floating
around
for
boards,
but
I
think
to
your
point.
It
is
think
through
especially
we
want
to
use
saved
filters
as
well
so
like.
How
would
you
build
a
saved
filter
and
how
would
that
display
versus
you
know
even.
D
B
Board,
which
is
basically
just
a
saved
filter,
and
we
don't
really
display
that.
Well,
so
it's
like
how
do
we,
you
know,
justify
like
those
two
ideas
and
so
yeah,
I
think
not
in
this
issue,
but
I
think
that
is
something
we
need
to
figure
out,
saved
queries
and
then,
especially
as
we
think
about
like
building
more
complicated
queries.
What
does
that
look
like
how.
C
B
I
think
becca
you
might
want
to
look
at
it
and
co-working
had
the
like.
The
vulnerabilities
dashboard
do
almost
like
a
query
building.
You
know
the
the
not
filtering
things
like
that
and
or
so
yeah.
I
think
we
need
to
figure
that
out
fairly
soon
and
then
I
have
the
issue
floating
around
for
filtering
versus
just
be
kind
of
simple
builders
like
how
do
we
support
users
that
might
not
be
comfortable
doing
like
the
query,
jql
right,
like
thinking
about
like
jira,
how
you
have
to
build
all.
B
Yeah,
so
how
do
we
avoid
that,
but
also
allow
that
if
users
want
so
I
don't
nick-
I
don't
know
I
haven't
have
I
haven't
figured
it
out,
but
I
think
we
we
should
think
about
searching
and
name
team.
Nick
brandt
has
done
a
lot
of
really
great
work
for
our
universal
search,
actually
really
powerful,
like
it
has
not
and
or
like
it
has
all
the
filters
that
we
need,
but
we
have
our
search
yeah,
like
the
gitlab
specific
thing
to
think
about.
A
A
One
of
the
things
that
I
liked,
especially,
was
their
ability
to
like
share
a
view
or
a
board
with
an
organization
so
like
I
have
a
board
for
like
my
own
issues,
but
I
don't
really
want
to
share
that
with
everybody
at
gitlab,
but
I
kind
of
have
to
save
that
view
in
order
to
like
keep
it
cached
in
the
list,
at
least
so
I
thought
that
was
kind
of
like
a
neat
feature
where
you
can
choose
to
like
share
hide
if
whether
your
organization
could
see
it,
but
just
coming
off
of
a
few
things
that
you
brought
up
like
they
put
like
the
edit
view
or
edit
boards
button
under
you
know,
the
ellipses
button,
similarly
like
theirs
is
just
on
the
list
like
ours
are
as
well.
A
The
one
thing
I
did
like
is
like
their
filter
options,
but
it's
just
you
know.
A
There's
in
this
case
is
like
it's
an
ore,
so
improvement,
or,
if
I
added
another
one,
it's
like
could
be
improvement
or
features,
would
show
up
in
this
list.
So
structurally
there
to
some
things.
We
can't
necessarily
change
but
yeah.
I
kind
of
just
liked
how
they
had
made
some
of
the
things
look
just
pretty
like
simple
and
out
of
the
way
and
let's
the
board
itself
do
most
of
the
the
talking
here
but
yeah.
A
I
was
just
kind
of
playing
around
with
it
and
it
made
me
think
of
the
ideas
that
you
brought
up.
It's
so
hard
to
get
like
some
of
these
mvcs
out
there
to
try
and
like
get
to
a
more
cohesive
vision,
but
you
did
a
really
great
job,
keeping
track
of
everything.
I
think
you
might
have
like
two
million
issues
open
for
improving
boards.
A
B
Yeah,
what
I'm
hearing
I
guess
is-
and
I'm
sorry
I
know
my
internet
is
probably
really
annoying
for
y'all
thinking
future
states
like
thinking
about
that
field.
B
Thinking
about
like
what
to
what
we
can
kind
of
of
that
view,
so
that
users
can
focus
on
really
the
compound
board
that
they
care
about
and
understand
what
they've
applied
like
applied
filters
and
options,
but
not
making
them
so
kind
of
any
quote:
unquote
so
yeah
great
feedback,
and
I
think
we
will
get
there,
but
I
guess
just
not,
but
I
do
feel
the
pain
point
as
well
that
sometimes
mvcs
are
hard
because
it,
I
kind
of
like
put
this
puzzle
piece
into
this,
this
big
old
puzzle.
B
B
Yeah
and
a
lot
of
tools,
even
I
think
like
notion,
is
one
that
I
use
that
are
more
just
like
really
like
text
editors
almost
but
now
they're,
adding
in
all
these
different
views,
like
you
can
add
a
roadmap
or
a
board,
or
you
know
you're
it's
just
like
kind
of
like
this
little
widget
or
like
component
that
you're
adding
into
your
document.
B
So
if
you
think
about
it
that
way,
we
really
don't
want
this,
this
little
module
of
a
board
to
be
too
complex
like
you,
you
need
to
kind
of
set
it
up
and
just
embed
it
perhaps
right
in
the
future,
so
kind
of
thinking
that
way
is
kind
of
interesting
too.
B
Anyway.
I
don't
want
to
hug
all
the
time
blair.
Is
there
anything
you
wanted
to
mention
before
we
move
on
to
austin.
E
No
just
agree
with
nick
as
well.
Instead
of
I
don't
know
the
history
between
our
our
search,
but
I
I
know
traditionally,
with
with
developers
in
particular
our
users
search,
is
so
super
important
and
like
a
powerful
search,
is
so
super
important
and
then
just
knowing
what
I've
experienced
so
far
already
finding
things
and
connecting
things
and
not
reverting
to
an
external
search
engine
when
we
should
just
be
searching
internally
that
it's
super
important
and
also
a
lot
of
times.
E
These
large
universal
components
tend
to
sort
of
just
get
long
in
the
tooth,
where
we
just
keep
slapping
things
on
and
slapping
things
on,
and
it
makes
it
harder
and
harder
for
us
to
go
back
and
rethink
the
original
component,
and
this
is
probably
nothing
new
to
you
guys.
But
it's
just
it's
just
gonna
get
harder
and
harder
and
make
the
tool
possibly
worse
and
worse,
to
use
as
we
go.
B
Yep
and
good
point
and
like
kristen
and
I
at
mypm,
our
vision
is
that
you
could
basically
build
a
search
and
that's
like
your
overall
I
mean
we
haven't
totally
validated
this,
but
you
know
I
build
a
search
and
like
everything
in
gitlab,
responds
to
that
right.
Like
I
go
to
mrs
I
go
to
wherever,
and
I
see
that
that
query
that
I
built
so
like
yeah.
I
think
we
need
to
figure
this
out
fairly
soon.
A
Yeah
I'll
share
my
screen
to
help
walk
through
this
one,
a
little
bit
desktop
two
okay.
So
recently
during
the
explore
card
that
daniel
posca
ran
for
me,
I
observed
that
it
was
challenging
for
him
to
sometimes
interpret
what
is
listed
in
our
audit
events
table
just
based
off
of
the
descriptors
that
we're
using
sometimes
it's
a
little
unclear
like
what
an
object
is
or
a
target
just
purely
off
of
its
data
piece
alone.
A
A
As
an
example,
you
might
get
the
path
to
a
project
as
the
target,
but
it's
really
more
useful
to
know
that
this
was
a
compliance
framework
that
was
modified
in
project
settings.
So
I
was
assuming.
Maybe
the
easiest
thing
to
do
would
be
to
add
to
the
table
like
a
secondary
row
of
information,
underneath
the
target,
like
it's
tight,
just
to
help
provide
more
context
as
to
what
it
is.
A
So
what
that
might
look
like
is
if
this
is
our
current
table
today,
where
you
know
the
tape,
the
target's
just
telling
you
hey
here's
a
project
path
that
doesn't
really
tell
you
anything.
We
just
add
the
target
type
data
in
which
would
be
fine,
but
you
can
kind
of
see
down
here
where,
like
this,
is
this
sucks?
A
It's
like
a
just
jammed
words
together,
so
maybe
I
could
work
with
the
team
to
better
refine
how
we
write
those
descriptors,
so
they
could
be
a
little
bit
more
clear
or
at
least
parsed
clear
in
the
table,
but
I
wasn't
sure
maybe
what
you
all
were
thinking
in
terms
of
do
you
think
maybe
just
providing
the
text
itself
or
like
would
maybe
putting
it
behind
a
tool
tip
be
better.
I
feel
like
putting
it
in
the
table
directly
is
better
for
accessibility
purposes,
but
it
also
creates
a
greater
cognitive
load
on
the
user.
F
My
thought
is
that
it's
always
easier
to
add
it
in
than
to
like
remove
it
later,
I
don't
mind
seeing
the
verbiage
there
personally,
but
it's
also.
I
don't
know
how
much
mobile
is
playing
into
this
for
you
at
all,
but
it's
worth
maybe
considering
that.
Of
course
you
lose
the
hover
in
mobile,
so
you
wouldn't.
A
Yeah,
the
way
that
I
worked
with
my
team
to
do
mobile
was
at
a
certain
break
point.
We
break
each
row
into-
I
guess
a
single
container,
so
I
think
in
that
case
I
would
at
a
minimum,
have
to
advise
like
putting
it
in
the
table,
but
yeah.
That
would
be
an
argument.
I
think
you
could
say
against.
Tooltips
is
they're
not
accessible
on
mobile.
So
on
the
flip
side
of
that
I
mean
honestly,
people
probably
aren't
accessing
audit
events
on
mobile
anyways.
E
E
Holly,
I
know
we've
talked
about
this
before
and
you
know
my
feelings
of
like
oh
well.
Maybe
it's
not
used
very
often
in
mobile.
We
should
probably
just
not
that's
a
pet
peeve
of
mine
just
because
being
at
the
bank,
there
are
a
lot
of
screens
that
internally,
our
our
dev
teams
and
our
product
teams
are
like
whatever.
If
it
doesn't
work
on
mobile,
no
big
deal,
but
wouldn't
it
be
nice
like
if
it
did,
and
you
know
and
there's
a
way
to
approach
it.
E
Mobile
first
holly,
where
you
know,
and
if
tool
tips,
aren't
that
that
useful
you're,
just
sort
of
layering
up
on
the
desktop
and
and
whatever
experiences,
then
it's
cool
get
rid
of
them
on
mobile.
There
is
a
way
to
implement
tooltips
that
are
chat
friendly,
but
they're
kind
of
wonky
and
clunky
and
not
accessible.
E
E
If
the
the
critical
information
is
there
go
ahead
and
and
sort
of
keep
it
and
then
get
rid
of
that
sort
of
layered
stuff
but
yeah,
I
I
very
much
caution
against
throwing
a
screen
out
because
a
lot
of
people
don't
go
here.
A
You
and
I
both
know
blair
some
organizations,
just
don't
even
let
you
access
websites
on
your
own
phone,
so
especially
with
gitlab
being
self-managed
like,
for
example,
I
could
not
access
gitlab
on
a
mobile
device
at
my
last
company.
I
could
just
when
possible.
A
We'll
work
on
that
yeah,
it
was
just
a
firewall
thing,
wouldn't
permit
it,
but
at
the
same
time
I
think
logging
in
general
sometimes
is
a
hard
thing.
It
is
so
data
heavy
that
it
can
be
very
easy
to
overload
that
mobile
screen
with
tons
and
tons
of
data.
A
A
In
this
case,
the
table
implementation
was
done
first
a
long
time
ago,
and
then,
from
there
we
at
least
tried
to
make
it
a
little
bit
more
usable
on
mobile
by
breaking
down
into
each
container,
because
it
was
just
like
scrollable
kind
of
as
it
would
be
now
a
little
bit.
There's
like
a
certain
breakpoint,
where
it's
like
a
little
bit
scrollable,
I'm
not
sure
where
that
happens
at
but
yeah
it
was
to
try
and
make
it.
A
A
I
would
say
probably
the
most
important
bits
of
information
on
this
page,
especially
come
from
like
the
action
message.
Adding
another
column
is
like
possible.
It's
just
you're
we're
just
constrained
on
space
and
the
more
columns
we
add
in
the
harder
it
is
to
read.
So
you
know
it
eventually
just
becomes
an
excel
spreadsheet
that
you
have
to
scroll
on
anyways.
A
So
that's
you
know,
that's
the
trade-off
is
what
all
can
we
display
in
an
in
our
reasonable
width?
Here
we
try
and
keep
it
focused
on
what's
most
important
here,
and
then
we
get
users
access
to
more
data
if
they
really
need
to
get
to
some
of
the
details,
I
think
I
was
just
really
struggling
with
the
fact
that
this
this
in
this
case
is
a
project,
and
this
in
this
case
is
a
compliance
framework
which
is
stated
technically
in
the
message,
but
yeah.
D
I
was
made
a
comment
in
the
agenda
that
wouldn't
make
sense
to
instead
have
customizable
tables
where
you
can
then
add
or
remove
column
data
that
you
want
pulled
out
of
the
csv
and
then
the
csv
is
export
for
audit
tracking
purposes,
whereas
the
ui
is
just
strictly
visual.
A
Yeah,
I
mean,
I
think,
the
concept
of
being
able
to
build
your
own
table
is
awesome
and
probably
would
be
a
really
sweet
feature
that
we
don't
obviously
have
today
in
gitlab.
So
again,
this
goes
back
to
that
tension.
We
have
between,
like
taking
an
mvc
approach
of
hey,
like
users
are
struggling
to
just
read
the
table
as
it
stands
today
like
what
would
be
a
very
flexible
option
in
a
vision
down
the
road
of
being
able
to
build
your
own
tables
for
audit
events.
A
I
would
probably
say
today:
users
probably
wouldn't
benefit
tremendously
from
just
being
able
to
customize
their
own
data
solely
from
the
fact
that
they
can
just
put
it
in
a
csv
and
open
it
up
in
excel
or
google
sheets
and
do
that
themselves
if
they
really
wanted
to
anyways.
Sometimes
they
do
sometimes
that
is
like
the
way
they
deliver
their
artifacts
for
audits,
but
yeah.
I
think
it's
just
one
of
those
things
where
it'd.
D
A
D
Maybe
not
you,
but
other
users
and
other
parts
of
the
organization
definitely
would
have
high
value
for
that.
So
arguably,
like
I
would
say,
yeah
mvc,
probably
not
a
quick
thing
to
do
over
one
milestone,
but
the
idea
of
like
pitching
this
as
a
system-wide
update
to
pajamas
to
help
issues
across
your
organization.
This.
E
D
E
Solutioning
or
anything,
but
like
that,
the
sort
of
show
columns
like
button
right
like
that,
would
be
the
the
quickest
easiest
way
for
us
to
implement
that
and
then
have
just
check
boxes
for
whatever,
like
like.
You
were
sort
of
hinting
at
daniel
like
right.
E
We
could
populate
that
that
the
drop
down
that
comes
out
from
that
button,
depending
on
where
we
are
in
in
the
environment,
it's
sometimes
more
useful
in
others,
maybe
not
as
useful,
to
implement
and
harder
to
implement
in
certain
areas,
in
which
case
we
just
drop
the
button
yeah
and
then
we
we
start
sort
of
testing
around.
Are
these
users
who
are
expecting
this
button
now
like
in
this
area,
want
it
to
come
over,
and
if
so,
we
invest
the
time
and
energy
to
bring
it
over.
A
A
Austin
have
to
keep
like
pulling
bring
up
linear,
but
I
did
see
that
was
like
a
thing
like
you
could
pick
what
you
know
things
you
wanted
to
see
on
your
board.
A
So,
like
attributes
of
like
an
issue
like
you
could
have
it
show
the
labels
or
hide
the
labels
or
show
the
priority
or
hide
the
priority
or
show
the
id
or
hide
the
id,
and
all
it
was
is
a
button
and
then
picking
like
off
of
a
list
of
toggles,
essentially
so
yeah.
I
guess
that.
Could
that
could
also
be
an
option.
A
A
Yeah,
so
just
to
wrap
it
up,
because
I
know
we're
like
right
at
time
and
I'll
be
quick.
So
if
I
only
could
take
one
path
like
in
the
next
milestone,
we
have
like
three
or
four
good
ideas
here.
A
F
B
Okay
I'll
send,
I
think,
like
well,
okay,
and
if
you
add-
and
I
think
this
could
be
like-
maybe
a
step
towards
what
daniel's
saying
like.
If
you
add
a
column,
then
maybe
you
could
also
kind
of
like
add
a
sub
classification
to
the
point
earlier
that
you
were
a
little
worried
about
that
like
oh,
this
one
is
the
setting
and
then
this
one
is
the
project
right
within
the
column.