►
Description
This video provides an early preview of the demo data designer/generator that is being added to the GitLab Demo Portal. We cover the basics of creating issue boards with labels, milestones and issues. We also discuss how our new relative date system works to ensure the demo data shows current dates.
Please see the #demo-systems channel on Slack to learn more.
A
Hey
everyone
I
want
to
give
you
a
sneak
peek
of
a
new
demo
data
generator
that
I've
been
building.
That's
going
to
allow
everyone
to
contribute
different
data
and
really
solve
some
of
the
project.
Import
challenges
and
I
want
to
show
you
in
a
pre-release
alpha,
just
to
kind
of
give
you
a
taste
of.
What's
coming
so
on
our
demo
systems
portal.
There's
a
new
tab.
That's
appear
at
the
top
navigation
called
demo
data
designer
and
the
designer
has
three
elements
to
it.
A
You
have
your
environments,
which
is
where
you're
going
to
say
what
the
URL
of
your
get
live
instances
as
well
as
the
API
key
to
access
it.
The
playbooks
is
where
we're
going
to
have
all
of
our
templates
set
and
the
runs
are
going
to
be
where
you
actually
going
to
run
your
playbook
against
the
environment
and
kind
of
see
the
the
import
process.
If
you
will
right.
A
So,
let's
have
a
look
at
our
environments,
real
quick
just
so
you
can
see
this
so
on
our
environment,
I've
already
pre-configured
mine,
but
I'll
show
you
what
it
looks
like
is
essentially
give
it
a
nickname.
Whatever
you
want
to
call
it
what's
the
URL,
this
could
be
an
omnibus
instance.
This
gonna
be
Caleb
comm.
This
could
be
the
gate,
love
demo
cloud,
whatever
you'd
like
it
to
be,
and
then
the
access
token
and
there's
instructions
for
creating
the
personal
access
token.
A
Nothing
special
about
this
one
thing
to
keep
in
mind
is
what
we're
going
to
give
access
to
is
any
project
or
group
that
you
have
owner
privileges
to
so
it
will
not
be
able
to
see
everything.
That's
going
on.
It's
only
the
stuff.
You
have
ownership
of
once.
You've
added
it
in
what
you're
going
to
end
up
seeing
is
all
of
the
groups
that
you
have
owners
access
to
and
the
project.
So
here's
an
example
where
it's
doing
a
live,
API
pull
bringing
that
data
down,
so
we
can
see
what
can
you
choose?
A
The
reason
this
is
important
is
because
we're
going
to
want
to
run
our
play
books
against
either
creating
a
new
project
in
one
of
these
groups
or
against
one
of
the
existing
projects.
So
that's
what
we're
going
to
be
working
off
of
right
so
from
the
top
here.
Let's
have
a
look
at
the
Play
books,
let's
create
one
together.
So
what
the
playbook
is.
Let's
just
call
this
issue
management
and
sample
description.
A
The
playbook
is
going
to
give
you
essentially
it's
like
building
a
project
template
tutor
for
export,
but
it
gives
a
lot
more
dynamic
flexibility
in
terms
of
what
gets
attached,
how
it's
managed
and
everything
else,
and
what
we
want
to
have
a
look
at
is,
on
the
left
hand,
sidebar
here
see
the
project
configuration.
These
are
all
the
things
you
want
to
configure.
A
First
after
those
pieces
are
in
look
under
project
activity
and
configure
issues,
and
then
what
you
can
do
is
add
milestones
and
labels
to
the
issue
board
and
it'll
automatically
capture
and
bring
in
what
those
issues
are.
So
for
our
you
know,
minimum
viable
change
and
seeing
what's
possible.
The
sample
here
is
we're
gonna
create
issue
boards
right.
A
So
if
I
go
down
to
labels,
I've
already,
given
everything
a
name
here
is
there's
no
labels
listed
here,
we're
gonna
add
the
ability
to
generate
labels,
so
it'll
generate
anything
from
give
me
ten
sample
keywords
to
give
me
the
normal
Kanban.
You
know
feature
set
right
going
from
backlog.
You
know
image
to
do
all
the
way
to
finished
so
well,
it's
a
create
a
label
here,
we're
gonna
add
those
in
just
manually
for
ourselves.
A
If
you
want
to
change
the
color
feel
free
here,
I'm
not
going
to
bother
with
it
for
right
now
and
on
the
label
description.
This
is
exactly
what
you
see
in
the
API,
so
you
notice
up
here.
There
are
documentation
links
and
if
you
can
open
up
in
a
new
tab,
you
can
learn
more
about
what
those
fields
are,
what
you're
looking
to
do
and
then
the
API,
what
we're
actually
importing
when
we're
creating
a
new
label.
A
So
if
you're
looking
for
the
parameters
there
here,
we
haven't
brought
them
fully
into
our
documentation
yet,
but
those
do
exist
right,
so
we'll
go
ahead
and
just
save
label.
So
now
we
have
a
backlog
label
will
create
two
more
here.
One's
gonna
be
to
do
fantastic,
maybe
three
more
we'll
do
one
for
doing,
and
let's
create
one
for
done
now
that
we
have
these
in.
Here
we
have
these
four
labels.
We
can
give
them
different
colors.
A
If
you
choose
I'm
not
going
to
worry
about
that
for
the
moment,
we
can
also
go
in
and
add
milestones.
This
is
where
the
real
bread
and
butter
is
going
to
come
in
instead
of
doing
project,
import
and
export.
This
allows
us
to
do
dynamic
relative
dates.
The
idea
here
is
that
we're
going
to
use
January
1st
2020
as
our
whatever
today
is
and
what'll
end
up
happening
is,
when
you
add
your
milestones
in
here,
you
can
add
milestones
there
in
the
past.
A
You
can
have
milestones
there
in
the
future
and
what
we
want
to
do
is
make
it
so
that
you
can
anyway,
give
them
time
you're
not
going
to
end
up
with
stagnant
data
when
you
bring
this
stuff
in.
So
if
you
were
import
a
project
that
you
built
four
months
ago,
all
the
timestamps
are
from
four
months
ago,
and
we
can
do
certain
database
crawls
and
things
to
try
to
import
that,
but
there's
a
lot
of
legwork
that
goes
into
it
and
don't
think
it's
worth
the
effort
for
the
benefit
we
actually
get.
A
So,
instead
going
to
use
the
API
to
add
things
in
dynamically
when
it
starts
so
what
you're
doing
in
your
PlayBook
is
setting
it
up
for
if
today
is
January,
1st
did
my
milestone
start
in
the
past,
or
does
it
start
in
the
future,
and
you
can
see
some
examples
in
here-
I'm
just
going
to
paste
these
in,
so
you
can
see
how
this
works.
So,
if
I
go
to,
you
know
past
milestone,
we're
going
to
start
this
on
2019,
ten,
twelve
and
dude.
It's
going
to
be
2019
actually
a
little
bit.
A
What
was
due
yeah
this'll
work
all
right,
so
we're
going
to
add
that
in
there
and
you'll
see
it
dynamically
tells
you
when
this
happens
right
and
so
based
on
when
you
import
it
in
everything
will
be
dynamic
based
on
those
numbers.
So
you
don't
have
to
worry
about
thinking
too
hard
about
it.
Just
try
to
think:
let's
go
back
a
month
from
January.
First,
let's
go
three
months
ahead:
I
mid-quarter!
Think
about
it
from
that
perspective,
and
you
can
use
these
samples
to
kind
of
help
you
get
started.
So
that's.
A
What
we're
trying
to
do
is
give
you
the
ability
to
do
a
lot
of
dynamic
data
generation.
You
can
also
edit
this
change
that
due
date
and
if
we
change
this
to
a
one
now
you're
going
to
see
hey,
there
is
the
one
month
after
so
that's
how
it
kind
of
maps
itself
out
right
all
right.
All
that
in
mind,
we've
done
our
labels.
We've
created
a
milestone.
We
can
create
more
milestones,
but
I
just
want
to
give
you
the
quick
and
dirty
here
can
I
show
you
what's
going
on.
A
We
also
go
in
and
create
the
issues,
and
the
issues
are
right
now:
they're
relatively
bare-bones,
it's
more
about
the
metadata
fields
than
it
is
about
formatting
right
now,
so
there's
no
markdown
formatting
in
the
description
box
and
some
of
the
fancier
things
that
we
can
do.
However,
they
are
all
functional.
So
if
we
want
to,
we
can
say
you
know,
here's
problem
number
one
need
markdown.
A
This
should
have
markdown
on
the
Creator
update,
go
ahead
and
put
whatever
data
is
relative
to
January
first.
So
if
I
created
this
issue
two
weeks
ago,
let's
assume
that
that's
going
to
be
2019,
twelve
fifteen
or
let's
do
twelve
ten,
and
if
you
know
the
secret
of
that
date,
it's
actually
the
date
back
in
2011
that
the
first
commit
of
get
labs
began.
So
that's
the
magic
of
1210
and
due
date,
relative
date.
A
Again,
let's
go
in
the
future,
so
we'll
go
Oh
2:15,
that's
going
to
be
six
weeks
from
today
relative
to
when
we
import
it.
We
want
to
add
any
weight
in
there,
we'll
give
it
a
weight
of
three
and
we're
going
to
add
in
the
user
and
assignment
this
is
a
pre-alpha,
so
know
how
that
feature
in
there
at
the
moment,
and
then
you
can
choose
that
milestone
that
you
created
and
so
we'll
support,
project
and
group
milestones
right
now.
We
only
have
project
milestones
in
go
ahead
and
save
that
issue.
Okay.
A
That
issue
is
now
there
now
when
I
go
to
issue
boards.
I
can
create
a
new
issue
board
here
and
I'm
going
to
say
my
tests.
Whatever
else
you
want
to
call
it
again.
This
is
very
primitive
as
we're.
You
know.
Just
getting
started
moving
this,
but
now
this
little
icon
here
is
looking
at
the
columns
of
this
board.
A
So
we're
going
to
say
that
we're
going
to
create
a
the
four
elements
here
and
it
will
also
create
another
one
with
the
milestone
just
so
you
can
see
the
difference
of
how
this
works,
and
then
project
label
add
these
in
here
and
you'll
notice
that
I
have
the
to
do
and
done,
and
the
the
doing
are
all
out
of
order.
We're
going
to
fix
that
a
second
here.
A
So
all
of
these
that
are
here,
we've
added
these
little
left
and
right
arrow
buttons,
they're,
pretty
simple
they're,
not
fancy,
there's
no
drag-and-drop
here,
but
I
can
click
this
to
move
it
left
and
right
and
make
sure
it
gets
in
the
order
that
needs
to
be
done.
If
I
add
something
in
that
I,
don't
like.
Let's
add
in
this
milestone,
be
sure
to
choose
which
one
it's
supposed
to
be.
It
will
throw
the
type
error
if
it's
not
there.
I
have
this
milestone
in
I.
A
Don't
want
that
column
just
deleted
off
the
board
when
you
go
to
import
and
run
this
playbook
what'll
end
up
happening
is
it'll
create
all
these
issue
boards.
If
you
make
a
change
here
on
the
demo
portal,
only
future
runs
will
be
affected.
It's
not
going
to
go
back
and
look
at
it.
Previous
one
runs
that
you've
done
right.
So
keep
that
in
mind
all
that
being
said,
we've
now
got
our
playbook
we've
added
some
data
to
it.
A
What
I
want
to
show
you
I
haven't
completely
finished
this,
so
I
want
to
show
you
what
happens
as
a
starting
point
and
give
you
an
idea
here.
So
I'm
gonna
close
out
a
couple
things
right
now
we
don't
have
the
new
object
on
that
are
probably
on
the
next
couple
days,
but
again,
I
want
to
give
you
a
sneak
peak.
Is
so
I'm
going
to
go
to
my
group
on
the
demo
cloud
and
I'm
going
to
create
a
new
project
and
I'm
going
to
call
this
video
project
one
fantastic,
create
project.
A
Now,
if
I
go
and
look
at
the
environments
that
I
have
in
here
go
to
my
environments,
demo
cloud
I
should
see
this
project
in
here
and
there
it
is
right.
So
what
we're
gonna
end
up
doing
is
running
our
playbook
against
that
project.
It's
an
empty
project.
You
don't
want
to
do
this
because
I
don't
have
all
the
error
checks
in
right
now
to
see
if
the
label
already
exists.
If
an
issue
already
exists
with
that
name,
it's
going
to
throw
a
500
error.
A
It's
not
going
to
be
gracefully
handled
at
the
moment,
so
just
keep
that
in
mind
right
great.
Let's
look
at
that
playbook
again.
Here's
that
issue
management
playbook
that
we
just
built
go
to
playbook,
runs
and
we'll
run
this
playbook,
so
issue
management.
What
environment
do
I
want
to
run
on
I'm
going
to
run
the
demo
cloud
click
on
next
step.
Now
what
we
can
do
here,
as
you
can
see,
do
I
want
to
create
a
new
project
in
my
group.
A
This
isn't
enabled
yet
it
will
be
soon
or
do
I
want
to
run
an
existing
project,
so
here's
an
existing
project,
I've
just
created
and
when
I
hit
run.
This
is
going
to
spit
out
right.
Now,
it's
going
to
give
you
a
kill
out
or
a
die
with
the
array,
so
I'm
just
gonna
spit
out
the
array.
That's
out
put
it
to
give
you
an
idea
of
what's
going
in
and
then
show
you
what
it
looks
like
we're.
A
Gonna
add
a
lot
more
of
the
job
status,
see
which
issues
failed,
we're
adding
those
pieces
in,
but
as
a
starting
point,
it's
gonna
be
ugly
for
just
this.
This
little
video
here
so
when
I
hit
run,
it
just
did
API
calls
out
and
it
added
the
labels
that
I
was
looking
for
right.
So
these
are
the
four
labels
that
I
created.
That's
all
good
and
dandy,
and
if
I
go
over
to
my
project,
I
go
to
issues.
Labels
I
will
now
see
those
four
labels
have
been
created
on
this
project.
A
So
that's
what
the
import
process
is
really
looking
like,
I'm,
adding
in
the
rest
of
the
functionality.
You
see,
there's
a
couple
more
things
to
finesse
and
smooth
over
for
our
you
know,
1.0
or
0.1.
You
know
getting
things
out
the
doors
and
them
viable,
but
I
want
you
to
see
the
value
and,
as
you
create
things
on
the
portal,
you
can
then
easily
see
what
ran.
What
does
it
look
like?
A
What
are
the
options
that
I
have
and,
as
we
add
the
rest
of
the
API
functionality
and
we're
going
to
see
a
lot
more
benefits
here?
So,
on
the
my
playbook
going,
you
playbook,
what
are
the
other
API
options
that
we
have
I'm
shortcutting
myself
to
the
API
from
here,
and
you
look
at
all
the
different
resources
that
we
have
in
the
API
or
if
you
go
up
to
the
top,
sometimes
is
a
little
bit
easier
to
navigate
from
here.
Let's
go
to
the
resources
and
you'll
see
on
a
project
level.
A
So
those
are
just
some
of
the
things
that
we're
working
on
I
just
wanted
to
give
you
a
sneak
peak
of
it
will
be
adding
group
resources
at
a
later
point,
not
too
far
out
weeks,
or
you
know
just
a
couple
weeks
out
of
them.
Suspecting
right
now
and
that'll
allow
us
to
create
a
group
with
multiple
projects
underneath
of
it.
So
all
the
functionalities
there
we're
just
trying
to
figure
out
what
we
can
do.
So
we
look
at
demo
data.
This
is
the
art
of
the
possible.
It's
perfect
concept.
So
why
don't
I?
A
Let
you
poke
around
see
what
you
think
see
what
you'll
like?
Let
us
know
and
go
from
there
so
yeah
there
you
go
there,
you
have
it!
That's
our
new
demo
data
designer
point:
zero
zero
one
alpha
pre-release,
whatever
we're
going
to
call
it
haven't,
decided
yet,
but
I
want
to
give
you
a
sneak
peak
as
a
nice.
Everyone
can
contribute
on
virtual
contribute
day,
thanks
for
watching.