►
From YouTube: Scan Execution Policy workflow UX enhancements
Description
A breakdown of the UX enhancements that are coming to the Scan Execution Policy workflow in %16.2.
For more information or feedback, see the epic (https://gitlab.com/groups/gitlab-org/-/epics/8695)
A
Hello,
my
name
is
Alexander
charinsky
I
am
a
senior
Frontline
engineer
on
the
security
policies.
Team
and
I
am
here
to
present
the
ux
enhancements.
We've
made
to
scan
execution
policy
workflow
for
milestone,
16-2
Pages
have
been
updated.
First,
the
policy
editor
page.
This
is
what
it
used
to
look
like.
This
is
what
it
looks
like
now.
A
Second,
we've
added
additional
wording
to
signify
that
all
actions
will
be
run
if
any
condition
are
met
and
not
either
or
third.
The
runner
input
box
has
been
updated
to
a
drop
down,
so
a
user
can
see
which
Runner
tags
are
available
to
them
for
each
scan
and
finally,
the
scanner
profile
and
site
profile
input
boxes
have
been
updated
on
the
project
level
to
use
the
same
drawer,
the
user
will
recognize
from
the
on-demand
scan
configuration
page.
This
adds
continuity
to
gitlab.
A
The
changes
to
the
rules
section
is
that
rules
are
now
called
conditions,
so
a
user
can
think
about
which
conditions
need
to
be
met
for
the
actions
to
run.
We
added
additional
wording
in
between
the
conditions
to
to
clarify
that
only
one
condition
needs
to
be
met
for
all
the
actions
to
run,
and
then
we've
updated
the
schedule
scans
to
allow
for
greater
specificity
by
allowing
for
a
time
zone
drop
down
page
those
updated
was
the
policy
draw
on
the
policy
list
page
previously,
all
the
actions
were
compiled
into
a
single
paragraph.