►
From YouTube: UX Scorecard Fulfillment Utilization FY23 Q4 Determining where my storage is high in order to re
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
So
purchasing
storage
is
one
way
to
fix
storage
issues,
but
they
can
also
reduce
their
storage.
So
this
user
is
probably
thinking.
How
did
this
happen
and
the
email
doesn't
give
an
indication
of
what
happened
instead
of
just
purchasing
storage,
the
user
is
going
to
investigate
and
they're
going
to
go
to
the
usage
quotas
page
where
they
can
see
their
storage
usage,
and
the
first
thought
here
is
what's
causing.
What's
causing
me
to
use.
117
megabytes
of
storage.
I
know,
there's
not
a
lot.
These
are
just
example:
numbers.
A
On
this
part
of
the
UI,
there's
no
indication
of
what
has
changed,
there's
no
historical
View
and
it's
a
little
bit
difficult
to
know
where
to
start
your
investigation,
but
one
place
to
start
would
be
the
table
because
there's
lots
of
columns
that
break
down
the
small
multiples
for
each
project,
and
so
this
user
is
going
to
go
in
and
just
start
sorting
on
different
columns
to
see
if
they
can
identify
a
problem
with
one
of
their
projects.
A
And
the
thought
here
is
nothing
stands
out
in
particular,
the
problems
with
this
page
is
there's
no
way
to
dig
into
into
a
storage
subtype
to
see.
What's
going
on,
you
can
go
into
different
projects
and
visit
their
repos
and
check
their
container
Registries
and
things
like
that.
But
there's
no
breakdown
within
this
View
and
there's
no
guarantee
that
what
the
user
finds
is
actually
causing
the
problem.
So
storage
usage
is
super
complex.
A
So
there's
there's
really
not
a
way
in
this
view
to
determine
what
exactly
is
the
problem,
and
so
some
suggestions.
Suggestions
here
are
to
link
to
some
kind
of
historical
view
or
breakdown
of
storage
subtypes
and
allow
the
historical
view
to
identify
spikes
in
different
storage
types.
So
that
way,
you
could
determine
whether
your
problem
was
due
to
like,
for
example,
committing
a
large
file
where
your
storage
would
spike,
or
you
might
just
see,
like
gradual
growth
over
time.
A
A
My
artifact
storage,
so
big
problems
on
this
page
is
there's
no
onboarding
for
users
to
prevent
problems
before
they
happen,
so
this
artifacts
problem
could
be
because
they
don't
have
cleanup
policies
in
place
or
they
don't
know
they
don't
understand
how
git
lab
works
with
artifacts
and
how
long
they're
kept
and
there's
also
no
indication
of
how
your
your
projects
are
configured
from
this
page,
and
so
my
suggestion
here
was
a
guide
or
documentation
to
get
all
your
settings
in
order
from
the
get-go.
A
This
user,
clicked
on
the
question
mark
icon,
to
learn
a
little
bit
more
about
artifacts
and
found
this
page.
This
page
suggests
that
some
artifacts
can
be
like
the
the
preservation
of
the
latest
artifacts
can
be
disabled.
A
These
instructions
in
the
documentations
are
for
one
and
not
the
other,
and
so
this
user
will
eventually
realize
that
the
other
type
is
kept
forever
and
they'll
need
to
do
other
things
to
clean
those
up
versus
just
changing
the
settings.
So
the
documentation
here
is
really
insufficient,
and
so
my
suggestions
here
are
clarified
job
versus
pipeline
artifacts
and
how
to
clean
up
and
potentially
looking
at
a
breakdown
of
artifact
types
within
the
artifact
storage
numbers.