►
From YouTube: Secure Team: Group-level Security Dashboard - Part I
Description
Kickoff of the Security Dashboard at the group level with the Secure Team (including backend, frontend, and UX members).
This meeting was to discuss and validate the Final “incremental” design. More info: https://gitlab.com/gitlab-org/gitlab-ee/issues/6709
A
B
B
Okay,
so
thank
you
for
joining
everyone.
This
discussion
about
the
group
level
dashboard
I
put
in
the
in
the
calendar,
invite
a
link
to
the
document.
That
was
the
one
already
used
to
discuss
about
the
dashboard
in
general
and
I'd
like
to
add
a
new
section
today
about
our
discussion
and
the
group
level
security
dashboard.
The
discussion
is
not
just
about
the
dashboard,
but
also
on
the
data
model
and
the
artifact
parsing.
B
So
if
we
have
all
the
information
from
one
point
to
this
to
the
other
one,
the
the
person
is
the
final
incremental
design
incremental
it's
just
because,
even
if
you
are
very
very
confident
that
we
can
have
everything
done
by
next,
iteration
I
still
like
to
have.
You
know
incremental
development.
So
if
we
cannot
do
all
the
features
that
we
are
considering
as
part
of
this
first
iteration
MVC,
we
can
still
get
something.
So
my
proposal
is
that
the
very
first
thing
to
do
is
the
top
summary
with
the
with
the
big
numbers.
B
B
Then
we
have
the
action
items
in
the
list,
so
the
ability
to
create
an
issue
from
there
to
dismiss
the
issue
from
there
and
then
filters
that
still
need
some
no
discussion
and
out
to
figure
out
exactly
what
we
want
to
filter
what
the
filters
will
affect.
So
I
really
suppose
this
is
the
the
right
sequence
of
things.
B
All
of
them
are
intended
to
be
part
of
this
iteration,
but
just
in
case
this
is
the
priority
order
inside
the
same
iteration,
I'll
I
think
that
the
graphics
are
completely
out
of
this
iteration,
so
we
don't
even
have
to
discuss
I
know
that
there
is
already
an
issue
and
a
possible
design
for
them,
but
we
don't
have
to
be
take
time
to
implement
it
in
this
iteration.
It's
absolutely
too
much
otherwise.
B
The
second
point
is
the
source
of
the
information,
so
the
database,
we
still
need
to
completely
figure
out
the
structure
or
maybe
probably
the
end
for
the
and
already
have
a
very
good
understanding
of
that.
I
like
them
to
share
with
us.
So
we
know
exactly
which
are
the
the
numbers
information
available,
and
the
second
point
is
how
to
put
data
into
these
tables
so
how
to
parse
artifacts
how
to
store
the
artifacts
that
are
coming
via
the
CHD
pipeline
into
the
database
itself.
B
It
is
something
very
very
similar,
probably
to
what
the
unit
is
doing
up
to
the
parsing,
but
the
unit
as
far
as
I
know,
is
not
storing
data
into
the
the
database
itself.
They're,
just
parsing
and
consuming
artifacts,
you
know
live
at
the
moment
case
by
case,
so
it's
still
something
that
they
need
to
figure
out,
and
even
here
is
totally
fine.
B
If
we
can
just
start
with
one
of
the
types
categories
that
I
remember,
which
was
the
the
final
name
agreed,
so
dependency
scanning,
probably
or
SAS,
could
could
be
a
very
good
good,
but
obviously
everything
will
adapt.
So
as
soon
as
we
are
able
to
add
more
parsers
for
artifacts,
it
should
be
absolutely
transparent
for
users
and
we
don't
have
to
change.
Obviously
everything
again.
The
third
point
that
the
last
one
is
the
API,
the
interaction
between
the
front
end
and
the
back
end
I
consider
two
main
points
for
them.
B
The
first
one
is
the
page
load.
What
you
need
to
build
up
the
insert
page
and
then
the
second
point
is
user
interactions,
for
example,
and
you
want
to
create
an
issue
and
want
to
dismiss
something
if
you
click
on
a
filter
and
want
to
filter
on
something
these
are,
in
my
opinion,
the
points
we
have
to
address
today
in
order
to
get
the
final
design.
B
They
are
almost
done
all
of
them,
but
just
to
finalize
so
we
can
also
discuss
you
know
the
technical
possible
solution,
implementation
and
probably
the
front
end
and
the
back
end
I
have
to
line,
for
example.
If
you
want
to
do
it
dynamically
with
dgs
or
if
the
filters
and
the
lists
that
could
be
partly
a
reuse
from
existing
code,
and
so
it
means
that
you
have
some
constraint
coming
from
the
existing
code
that
you
have
to
take
in
the
intercom,
and
thank
you
Lucas
or
for
being
here.
C
Standard
additionally,
now
that
UX
is
not
done,
it's
fine
and
I
really
agree
with
the
strategy
you
like
outlined
and
I
think
you
know,
I
probably
finished
the
other
deliverables
first
and
so
I
think
I
also
can
support
them
because,
for
example,
take
creating
the
top
thing
and
creating
the
list
can
be
done
separately
right.
So
yeah.
B
Problem
absolutely
as
already
remember
that
in
a
very
multiple
places,
this
is
the
top
feature
for
11.4.
So
I
will
push
everyone
a
little.
You
know
in
the
in
the
fear,
in
the
polite
way,
just
because
I
really
think
that
we
shipping
dishing
11.4
is
a
very
important
thing
for
the
company
for
the
product
for
our
team.
So
let's
start
with
the
you
know,
discussion
and
probably
the
the
first
point
is
exactly
intuitive
about
engineers
talking
so
I,
don't
know
Andy
or
Lucas
and
Fabian.
If
you
want
to
jump
in
and
start
the
talk.
D
B
D
So
at
the
top
we
have
the
big
numbers
color-coded
based
on
G
twos,
new
types
of
nation
for
how
we're
gonna
call
out
critical,
high
medium
low
and
unknown,
and
then
you
start
just
move
down.
You'll
see
how
we
can
start
filtering
by
source
type
and
we
can
even
keep
the
count
of
the
source
in
there
if
we
want
and
then
by
clicking
this,
it
will
change
all
of
this.
The
idea
is
not
to
change
this
at
the
moment,
because
I
know
Phillipe
and
Sarah.
D
D
Okay
with
that,
as
we
move
forward
past,
the
MVC
you'll
start
seeing
how
these
might
become
a
little
more
dynamic,
but
for
now
we're
not
you're,
not
gonna,
make
these
dynamic
leaps
in
my
mind
and
then
we
have
filters
for
severity,
confidence,
project
identifier
and
then
our
boolean
for
dismissed,
and
then
we
have
a
sort
feature.
So
you
can
sort
by
last
detected,
which
is
our
day.
D
You
can
sort
by
severity
level
and
many
other
things.
If
we
decide
there
should
be
more
confidence
rate,
other
things,
vulnerabilities,
name
and
I,
don't
think
so,
and
then
we'll
paginate,
because
loading
this
you
know
long
list
won't
make
sense.
So
maybe
ten,
maybe
a
little
more.
We
if
there's
a
standard
practice
we
want
to
adhere
to,
and
then
you
have
the
ability
to
reset
the
filters
so
thoughts,
questions
comments.
Oh
yes,.
C
D
C
What's
what
what
about
that
column
would
also
be
missing
right
now,
because
if
I
I
don't
know
I
I,
don't
know
all
the
CVS
by
ahead
right
and
now,
I
have
no
way
to
select
one
I
I
would,
for
example,
see
okay,
medium,
insecure
variable
is
CBE
5000,
but
I
don't
know
it
now.
I
would
have
to
open
the
model.
F
Right
and
you
have
to
start
typing,
because
this
is
dynamic-
data
we're
gonna,
have
this
all
day
every
data
we
have
from
the
moon.
Our
ability
is
coming
from
reports,
so
we
don't
have
anything
in
database
except
from
the
sources
and
the
confidence
and
savory
level
which
are
normalized
by
use,
but
everything
else
is
coming
from
the
report.
So
for
the
identifiers,
it
can
be
a
lot
a
lot
of
different
values.
F
Yeah,
the
need
for
the
user
would
be
eventually
you
get
an
email
notification
about.
There
is
a
command
addiction
that
has
just
been
disclosed.
This
is
the
CD
1
2
3
4,
and
you
go
to
your
dashboard
and
you
type.
This
know
which
route
your
project
are
impacted
by
is
like
specific
vulnerabilities.
This
was
an
intended
usage,
but
we
could
eventually
move
it
back
to
to
the
next
iterations.
It's
not
a
big
fun.
Ok,
yes,.
B
C
F
Is
that
currently,
this
feature
is
really
not
readable,
so
I
see
the
value,
just
don't
be
annoyed
and
reviews
remove
some
noise
from
the
view
by
removing
the
dismiss
the
vulnerabilities.
This
is
great,
but
you
have
to
know
that
term.
Please
is
a
alpha
or
beta
feature,
I,
don't
remember,
and
it's
really
not
feasible
and
from
one
mesh
request
to
another.
Some
previously
dismissed
issues
with
inner
history.
We
come
back
so
make
them
back.
So
we,
this
is
not
something
we
want
to
push
really
hard
to
the
user.
B
A
B
D
B
I
really
need
to
know
I
wish
Civello
sorting
by
project
or
by
confidence.
Isn't
the
severity
thing
the
most
important
one
we
want
to.
You
know
just
to
avoid
some.
You
know
option.
You
know
that
we,
like
a
convention
server
configuration.
So
maybe
we
done
it
at
least
not
in
the
first
iteration.
The
take
just
trying
to
cut.
B
But,
as
Lucas
said
said,
we
don't
have
an
indication
of
the
project,
and
this
is
something
that
we
we
should
have
I,
don't
know,
for
example
in
issue
this
issue
boards
at
the
group
level,
Iggy
lab
you
have
near
to
the
title,
if
I
remember
correctly
the
project
name,
so
you
can
easily
get
this
information
from
the
list
without
opening
without
going
deep
or
filter.
So
that
could
be
an
option
and
sorry
just
barrel.
Discussion
about
this
shooter
for
now
at
least,
is
the
drop-down
supposed
to
allow
multiple
values,
or
is
it
just
one
value.
A
D
B
B
Odd
and
in
and
and
here
we
wanted
or
because
all
these
values
just
apply
one
set
for
each
category,
it's
a
for
a
fridge
kind
of
property.
So
you
will
not
never
have
critical
and
high
on
the
same
vulnerability,
but
you
may
be
interested
in
having
a
critical
and
high,
so
okay
by
I
could
be
fine,
having
just
a
one
value
for
each
if
it's
very
challenging
from
you
know
the
API
and
the
backend,
but
just
let's
consider
that
we
should
follow
up
on
this
to
figure
out.
B
If
it's
really,
you
know
important
this
filtering
it
solving
a
problem
to
users,
so
our
users,
using
this
filtering
option
for
something
or
it's
just
something
we
are
adding,
but
there
is
no
value
in
it
because
nobody
will
use
they
will
just
a
scroll
up
to
the
point
they
want.
If
it's
like
that,
we
don't
need
a
filter
in
this
way.
So
it's
it's
just
avoid
putting
a
complexity
into
the
feature
that
users
will
never
benefit
off.
Do.
B
The
sort
I'd
say
yes
yeah,
even
because
we
I
think
we
don't
have
this
nothing
to
do
that
ways
and
the
filtering
we.
We
should
keep
it
and
if
it's
hard
to
have
multiple
values,
because
it's
not
a
standard
pattern,
we
are
having
it
a
lab.
We
can
have
one
selection
for
each
of
them
and
obviously
the
older
or
I
know
no
filter.
I,
don't
know
when
you
go,
and
you
say
any
my
system,
for
example
initially,
but
then
I'd
like
Andy
and
everyone
else,
obviously
to
follow
up
or
and
to
figure
out.
B
D
C
D
F
B
G
B
Have
the
details
you
already
should
have
Adam
when
you
click
on
I,
don't
know
if
the
new
design
is
changing
also
in
the
report,
but
in
the
reports
at
the
moment
you
click
yes
exactly
there
on
the
vulnerability,
title
I,
don't
know
vulnerability,
name
and
you
go
to
the
details.
So
there
is
no
meaning
of
having
a
specific
button
to
open
the
same,
the
same
window
that
that's
my
take
away.
If
I
understand
it
correctly,.
F
B
A
B
Now,
in
the
security
reports
in
the
multi
quest
widget,
for
example,
and
then
you
get
details
from
there
even
because
you're
not
jumping
it
is
not
commit
or
something
you
will
jump
to.
So
you
opened
the
box
and
then
ended.
This
is
the
question
for
you:
I'm
not
pushing
in
one
direction
or
the
other,
but
I
know
because
of
experience
that
sometimes
you
it's
said
that
we
don't
want
to
have
the
same
action
twice
in
the
UI.
B
So
in
this
specific
case
we
can
dismiss
or
create
an
issue
from
the
list
that
the
full
list
itself
or
from
the
details
window
so
I'm
totally
fine
with
it.
I
don't
have
a
strong
opinion
against
having
multiple
times,
because
I
can
feel
that
maybe
you
are
just
seeing
the
list
and
click
all
of
them,
because
you
don't
need
more
details
on
vulnerabilities.
G
B
One
one
by
one
and
click
this
Mesa,
it's
a
little,
you
know
time-consuming,
so
I
feel
the
value
of
this
miss
this
you
from
the
full
list.
I
just
want
to
be
sure
that
from
a
UX,
Direction
I,
don't
know
best
practices.
We
are
not
doing
something
wrong
that
can
create
problems
for
the
future,
but
it's
completely.
You
know
up
to
the
unique,
so
you
can
figure
it
out
and
comment
yeah.
D
I
think
we
want
to
try
to
keep
all
the
actions
in
the
same
area.
That's
why
you
see
d2
going
to
these
three
buttons
here,
as
opposed
to
this
like
clicking
on
a
link
and
then
clicking
on
two
buttons.
I
guess
time
will
tell
if
that
works,
because
I
think
that's
what
might
be
getting
implemented
soon
or
not
11:4,
but
that
he's
been
working
on.
B
C
B
B
A
B
Absolutely
so
is
there
a
strong
reason
behind
having
the
violet
as
the
medium
color,
but
it
feels
to
me
a
little.
You
know
out
of
dab.
I
don't
want
to
see
the
standard,
because
probably
there
is
no
Santa,
but
I
normally
see
from
red
to
green,
with
a
variety
of
orange,
yellow
and
not
violet
and
medium
is
not
so.
B
A
D
D
Went
from
orange
purple
or
I'm
assuming
g2
wins
again.
This
is
based
on
GTS
color,
like
color
scheme
and
I,
like
it
I
like
the
way
that,
like
medium,
it
does
pop
a
little
bit
you're
right.
It
is
also
in
the
center
that
doesn't
help
and
when
you're
looking
between,
yellow
and
red
purple
does
pop
off,
so
we
don't
have
a
good
color,
for
it
is
currently
the
answer.
C
B
Anyway,
so
sorry,
but
just
to
you
know,
I
don't
want
to
get
the
conversation,
but
I
think
that
the
problem
is
it's
clear
that
the
problem
that
the
topic
is
clear
so
Andy
can
dig
a
little
more
on
that
and
I
feel
not
speaking
behalf
of
front-end
people,
but
that
if
we
have
to
adjust
the
colors-
and
we
know
it
in
two
days
or
three
days-
it
will
not
be
a
very
dramatic
change.
So
we
can
allow
Andy
to
do
some
research
and
to
check
if
the
the
color
is
fine.
Okay,
perfect
and
one.
A
A
B
F
Can
be
under
the
name,
I
think
the
the
five
pass
doesn't
bring
any
value
at
the
group
level
who
the
group
will
be
down
to
the
code
itself,
I
mean
if
you
and
if
you
click
on
the
vulnerability,
you
will
have
the
model
and
then
you
will
have
a
lyric
linked
to
the
fire
already
so
I
think
we
could
deliver
edge.
That
line
to
provide
some
more
infuse
information
like
the
project
name.
Maybe
some
identifiers
and
things
like
that.
That's.
B
D
I
saw
that
you
mentioned
that
in
the
issue
too,
as
well
Olivier,
which
is
good
I,
think
just
try
to
think
of
what
happens
when
you
want
to
sort
by
project
now,
you'll
see
it
yeah
I'm,
just
trying
to
think.
If
you
need
a
column
for
project,
because
you're
sorting
by
something
or
sorry
filtering
by
it,
yeah
I,
don't
think
you
do
you.
B
E
B
F
B
F
B
C
B
C
C
B
C
C
B
Just
want
to
avoid
the
problem
we
had
with
labels
at
the
group
level
that
were
not
propagating
to
subgroups,
and
so,
if
we
can
manage
everything
here
is
fine.
If
we
cannot
go
deep
into
a
subgroup
that
will
be
improved
later,
but
if
you
can
doing
them,
you
see
absolutely
fine
with
it
and
then
I
agree.
You
don't
have
to
filter
by
subgroup,
but
that
is
challenging.
Probably
what
you
want
to
visualize
in
the
project
drop
down
so
how
to
render.
B
But
probably
it's
the
same
when
you
move
an
issue
to
a
different
trip
or
you
can
have
you
know
the
group
/
/
of
the
project
name,
so
we
just
remember
to
do
a
lot
of
you
know
visual
testing
with
subgroups
in
order
to
figure
out
if
it's
working
and
if
it's
looking
at
understandable,
at
least,
if
not
nice,
okay,
one
other
thing
is
that
do
we
want
to
have
a
title
for
this
page
just
to
state
that
is
a
security
dashboard
I
know
that
probably
something
we
are
not
doing
anywhere
else.
No.
C
We're
not
doing
with
anywhere
else,
but
I
was
thinking,
because
we
said
that
the
boxes
are
not
dynamic.
Maybe
we
should
have
like
an
horizontal
rule
line
thingy
or
something
or
like
in
like
a
sentence
that
says
these
are
all
the
things
and
you
can
search
them
here
so
just
to
differentiate
all
the
fight
space
or,
however,
that
you
really
because
it's
not
interacting
with
each
other.
Now
at
the
moment,
we
should
probably
have
some
yeah.
C
C
You
have
to
open
the
single
issue
right
and
I
understand
why
we
have
the
models
in
a
merge
request,
but
in
a
previous
endeavor
I
always
found
out
that
modal's
can
be
a
bit
annoying.
Have
you
ever
thought
about
like
opening
a
sec
like
that,
you
can
open
the
whole
thing
and
that
the
instead
of
a
motor,
the
details
are
like
in
a
extensible
row,
mm-hmm
yeah,
just
just
in
general.
We
don't
have
to
do
it
for
MBC,
because
we
have
the
models
already
in
place.
C
But
I
was
wondering
if
this
is
something
your
ex
is
ever
thinking
about.
You
know
I
I
like
instead,
you
know
because
they
open
the
model.
You
have
to
close
it
and
if
you
open,
if
you're
in
front
of
critical,
if
there
would
be
a
small
thing
to
open
close
it,
you
could
open
it
see
odd.
That's
that
vulnerability
and
close
it
right
away.
You
don't
have
to
move
your
cursor
all
the
way
and
stuff
like
that.
You
know
no.
B
C
And
also
takes
away
the
pain
with
dual
controls,
because
then
you
also
already
have
the
controls
in
the
in
the
original
row
and
in
the
details
row
you
don't
have
to
re-edit
the
controls
for
dismissing
and
approving
and
stuff
like
that,
that's
missing
and
yeah.
What's
the
other
thing
creating
issue
also,
it
seems
that's
also
for
yeah,
okay,.
B
Absolutely
that
started
appreciated,
and
now
that
you
have
this
awesome
design,
the
question
is:
how
can
make
it
real
look?
Dude?
Oh
my
just
talking
about
that.
The
question
is:
do
we
have
the
information
available
into
the
database
in
order
to
have
all
of
them
without
parsing
the
artifacts?
And
the
second
question
is:
how
can
front
end
and
back
end?
You
know,
exchange
the
information
in
the
proper
way.
How
that
the
front
end
in
European
Lucas
could
be
structure
or
can
we
reuse
something
existing?
That
is
putting
limitations
into
our
choices.
C
So
I
just
had
a
look
and
basically
the
issues
and
much
requests
because
I
looked
at
the
previous
layout
with
the
search
bar,
but
the
awesome
search
probably
had
there
and
these
lists
are
still
rendered
in
Armour,
so
they
are
not
touched
in
view.
I
mean
Donn's
yeah.
We
have
dropdowns
cell
rule,
so
we
could
reuse
that,
but
I
don't
know
about
the
pagination.
If
we
would
do
and
that's
something
I
have
to
talk
about,
the
front-end
maintain
us.
C
A
G
C
G
C
Vulnerability
is
that
an
endless
scrolling
list
is
the
best
thing,
but
I
have
to
check
out
whether
we
have
pagination
already
available
in
view
so
that
you
can
use
the
API
properly,
because
I
think
we
want
to
go
API
first
and
once
we
put
it
API,
we
should
also
build
it
in
the
public
API,
or
are
you
planning
on
putting
it
in
the
non
public
API
way?
What's
the
plan.
B
Yeah
there
is
no
planet
wrong
with
that.
I,
don't
feel
strong
reasons
to
have
it
not
in
the
public,
API
I,
don't
know
the
latest.
You
know
agreement
between
front
and
and
back
about
the
usage
of
public
API
or
not,
but
I
feel
that
this
feature
could
be
useful.
For
you
know,
building
integrations
with
other
software,
so
someone
else
could
think
here
lab
to
get
this
information.
So
it
you
have
not
a
priority,
obviously
not
in
the
embassy,
but
api's
are
always
welcome.
Okay,.
C
D,
yeah
and
other
than
that
I,
don't
think
we
have
too
much
I
mean
we
can
reuse
the
model.
Obviously
we
already
have
the
model
in
place,
so
we
don't
have
to
deal
with
that.
So
we
basically
have
to
implement
two
things
on
the
front
and
side.
We
have
to
then
implement
the
top,
which
does
one
request
and
just
renders
the
rent
renders
all
the
the
summary.
C
And
then
we
have
to
have
a
paginate
at
a
bi
where
we
can
do
all
the
filtering
I
mean
at
the
moment
I'm
only
seeing
filtering
by
type
like
dependency
scanning
last
and
so
on,
severity,
project
and
confidence
and
whether
a
thing
is
dismissed,
I,
don't
know
if
it's
possible
to
get
around
with
the
dismiss
thing
or
because
it
will
mean
more
work
on
in
the
backend
right,
because
the
dismiss
is
currently
in
a
different
place
in
the
database
or
it's
not
an
issue.
Okay,
no.
F
Yeah
I
just
at
one
morning,
if
you
want
to
do
it
in
the
pubic
API,
it
has
more
constraints
at
just
a
static
controller.
Even
if
you
just
use
a
similar
API
I
mean
we
can.
We
can
provide
the
data
in
the
exact
same
way,
but
putting
it
in
the
public.
Api
would
add
more
work
for
us
because
we
never
did
that
before.
So
we
have
to
check
the
constraint
about
doing
so
the
documentation,
and
we
have
to
keep
in
mind
that
once
we
publish
it
there,
we
have
to
maintain
it.
C
We
have
a
way
to
create
beta
endpoints
I
mean
that
we
say
okay,
we're
creating
that
beta
endpoint
and
the
public
API,
and
we
also
want
you
know:
user
feedback
from
that
new
public,
API
or
whatever,
and
then
three
releases
later
say.
This
is
like
the
version
we
are
hammering
in,
or
do
we
have
other
than
that
I
would
say,
put
it
in
the
private
API,
but
maybe
in
a
way,
so
that
it
can
be
moved
easily
to
the
public
API.
Once
we
stabilized
on
the
on
the
API
itself
on
the
scheme
schema
sorry
yeah.
B
C
A
Just
will
just
rewind
the
bits
I
want
to
to
wrap
it
up
on
the
the
UX
part,
because
I
think
we're
really
close
to
something
unix
ready,
but
that
we're
missing
one
part
in
this
is
the
interactions
it's
not
abused
to
me.
What
this
UI
will
o
do.
This
UI
will
behave
when
I,
for
example,
when
I
click
on
this
mr.
owner
ability.
What
is
going
to
happen?
Are
we
going
to
strike
through
the
vulnerability?
Are
we
going
to
update
two
contours
on
the
top
I.
D
C
B
Can't
or
should
not
have
one
abilities
that
are
that
being
dismissed
like
we
are
changing
if
I
remember
correctly,
Lukas
in
this
iteration
in
the
report,
so
we
are
not
counting
them
anymore
in
the
in
the
math.
We
want
to
show
them
because
people
should
be
aware
of
it
and
it's
the
only
way
to
under
this
mess.
Think
for
now
at
least,
but
I
want
to
see
zero
if
I
dismiss
everything,
because
for
me
they
are
not
valid.
There
are
not
three
out
pruner
abilities,
anymore,
yeah,.
G
A
C
F
G
C
F
C
B
C
Question,
though,
regarding
the
numbers,
do
we
I
mean
we
don't
in
the
summary
in
the
top?
We
don't
count
it
do
we
count
it
in
the
bubble,
it's
behind
the
dependency
scanning
and
such
or
because
for
me
it
will
be
completely
confusing.
If
the
thing
says
you
have
zeros
asked
full
abilities,
but
you
click
on
it,
and
you
see
all
these
missed
ones.
C
C
B
C
B
G
B
A
C
B
B
If
you
put
an
empty
state
or
a
great
I'll
thing,
it
means
that
the
feature
is
existing
and
you
expected
to
have
something-
and
you
have
nothing
for
this
specific
instance-
I'd,
not
to
say
this
dashboard,
but
if
we
know
in
advance
that
you
will
never
see
something
because
the
feature
is
not
even
implemented,
it's
confused,
maybe
confusing
for
users
to
see,
says
that
zero.
No
sorry
sets
would
be
the
one
continuous
scanning
zero
they
may
expect.
Ok
cannot
click,
but
there
are
no
vulnerabilities
for
container
scanning.
C
B
F
E
B
We
really
sorry
we
just
have
seven
minutes
left
so
I
just
want
to
be
sure
that
we
are
covering
almost
everything
so
I
feel
that
maybe
Andy
could
try
to
understand
a
good
uux
to
you
know
manager.
If
you
lack
one
report,
if
you
miss
one
report,
if
you
don't
have
it
because
we
are
not
implementing
it
yet,
though
so
the
mmmm
Andy
I
just
want
to
be
sure,
you
put
a
note
about
empty
state
transition
states
so
that
you
know
they
are
needed
at
some
point.
I.
A
D
B
C
B
Anyway,
Andy
something
probably
you
can
figure
out,
I
think
that
is
a
blocking
the
start
of
the
development,
even
if
it
takes
a
couple
of
days
to
to
be
figured
out
to
be
fine.
So
just
back
on
euphorbia
and
Olivier,
do
you
feel
that
every
think
we
just
agreed
on
is
doable
with
the
the
structure
of
the
database
that
you
worked
on
yeah.
G
What's
like,
we've
got
everything
in
the
database
in
seven
better,
but
it
was
because
the
the
location
has
been
replaced
with
the
name
of
project
which
is
already
in
the
database.
We
were
as
well
the
location,
the
full
location
is
sell,
part
of
adjacent
blob,
so
it's
been
better.
We
got
everything
pretty
sure.
C
E
B
Next
steps
probably
are
for
Andy
to
you
know,
address
old,
that
the
questions
that
we
put
there
sorry
there
are
a
lot,
but
at
least
we
should
be
covering
everything
and
come
with
the
final
proposal.
It's
a
proposal,
but
would
be
probably
the
final
version
as
soon
as
possible,
even
because
we
may
need
the
design,
for
you
know
the
announcement
and
its
kind
of
things.
So
maybe
it's
a
good
idea
to
push
this
one
I
don't
know
whatever.
Is
it
just
update
the
current
one
in
the
issue?
B
That
is
worse
than
that
this
one
and
then
you
can
iterate
on
top
of
the
design.
So
it's
not
week's
ready
yet,
but
at
least
it's
very
near
to
and
then
on.
I
know
that
the
merge
request
about
the
database
structure
is
having
you
know
our
times
two
to
be
finished
and
merge
that
I
already
asked
Camilla
to
work
closely
with
you
I.
We
should
have
an
answer
about
his
availability
later
today,
so
I
hope
that
he
will
help
us
in
this
story.
B
As
part
of
you
know
the
team,
and
if
we
can
agree
an
API
between
front
end
and
back
end
and
just
you
know,
ensure
that
information
in
the
API
will
be
available
by
the
database.
It's
be
awesome
and
the
front
end
could
be
a
little
unrelated.
You
know
unlinked
by
the
back
end,
and
so
development
can
start
as
soon
as
possible.
G
D
G
D
C
B
Okay,
any
other
last
moment
comment.
Otherwise
there
is
an
app
to
you,
starting
in
one
minute
and
I
feel
you're
all
excited
by
this
feature.
A
lot
of
work
to
do
but
and
I
will
push
a
little.
You
know
together
sometimes
updates
and
to
ensure
that
everything
is
working
as
the
as
fine
and
we
are
not
blocking
or
waiting
for
something.
So
I
will
try
to
be.
You
know
a
little
project
management
helper.