►
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
Hey
y'all
shane
rice
here,
following
up
on
a
conversation
from
data
studio.
So
a
couple
days
ago
I
added
a
video
where
we
talked
about
how.
If
an
owner
of
a
dashboard
is
no
longer
with
gitlab,
then
we
can
copy
that
dashboard
to
create
a
new
copy
of
that
and
then
update
the
data
sources
so
that
we
recreate
that
that
report
without
a
lot
of
extra
work.
A
People
in
the
issue
pointed
out
that
they
can
copy
a
dashboard,
but
when
they
copy
the
dashboard,
the
data
sources
aren't
available,
and
so
that
led
me
to
some
investigation
and
what
I
discovered
is
that
so
when
you're
I'm
just
going
to
go
to
data
studio
now
when
you're
in
data
studio-
and
you
click
on
either
owned
by
me
or
shared
by
me,
there
are
three
options
you
have
up
top
here,
so
you
have
reports,
data
sources
and
explorer.
A
So
if
you
go
to
data
sources
like
for
me,
these
are
all
the
data
sources
that
I've
added
a
different
report
during
my
time
with
this
gitlab
account
in
data
studio.
So
what
we
can
do,
though,
so
I
can't
make
someone
else:
the
owner
of
the
data
sources
that
I've
created,
but
what
I
can
do
is
I
can
share
them,
and
so
I'm
going
through
and
sharing
you
know
some
of
the
key
reports.
I
know
I
have
and
making
those
so
that
they're
available
to
anyone
with
a
gitlab
email
address.
A
They
can
view
them.
If
you
can
view
them.
That
also
means
you
can
copy
them.
You
can
add
them
to
reports.
So,
for
you
know,
I
think
before
we
finish
up
my
transition
period.
I
think
one
of
the
things
I'm
going
to
try
to
work
with
danielle
on
is
copying
as
many
of
these
data
sources
over
to
her
account,
and
then
we
can,
you
know,
kind
of
you
know
spread
those
out
from
there,
but
I
think
this
is
proven
to
be
one
of
the
major
limitations
of
data
studio.
A
Just
it's
you
know
anytime
there's,
you
know
someone
leaves
or
there's
any
kind
of
turnover.
It
can
be
a
bit
of
a
headache.
So
we
may
one
of
the
things
we
may
want
to
do
is
consider
like
a
a
dedicated
data,
studio
user
that
will
be
permanent
and
that
people
can
log
into
or
share
access
with,
just
to
prevent
this
from
happening
and
being
kind
of
a
scramble
in
the
future.
So
I
just
wanted
to
excuse
me.
A
I
just
want
to
talk
about
that
share
kind
of
what
I'm
learning
and
keep
everybody
up
to
date
with
the
best
practice,
for
you
know
getting
this
data
set
up
correctly
in
these
dashboards.
So
that's
it
thanks.
Y'all
talk
soon,
bye.