►
From YouTube: Demo Systems Demo Data Designer/Generator Alpha Release
Description
This video provides a walk-through of the demo data designer/generator that is now available on 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.
* Get Started - https://gitlabdemo.com/designer
* Step-by-Step Docs - https://docs.gitlabdemo.com/tutorials/getting-started/using-demo-designer/
* Bugs and Tweaks - https://gitlab.com/gitlab-com/customer-success/demo-systems/demo-feature-requests/demo-data-projects/-/issues/7
* Virtual Contribute Challenge - https://gitlab.slack.com/archives/CPCKP4Y4R/p1587131624173100
* Slack Discussion - #demo-systems or #demo-systems-designer-users
A
To
get
started,
you're
gonna
want
to
visit
our
get
lab
demo
portal
by
going
to
get
lab
demo
calm,
if
you
haven't
been
here
before,
feel
free
to
use
the
team
member
registration
to
create
your
account.
If
you
have,
please
enter
your
email
address
and
password
to
get
started
on
the
get
lepton
portal.
Dashboard,
you're
gonna
see
the
existing
sandbox
environment
that
we
have
available.
If
you
look
in
the
top
navigation
you're
also
going
to
see
the
catalog
and
the
new
demo
data
designer,
let's
go
ahead
and
click
on
the
designer.
A
The
first
thing
you're
going
to
see
is
that
this
is
a
work
in
progress.
This
is
our
alpha
release,
so
there
might
be
some
things
that
are
a
little
bit
off
or
maybe
not
completely
baked
as
much
as
we
want
them
to
be,
but
it's
perfectly
functional
and
you
should
be
able
to
use
it
with
just
fine.
So
there's
three
elements
that
we
see
here.
The
first
is
the
environment.
The
environment
simply
lets
us
know.
A
What
are
your
get
lab
instance
is
or
if
you
want
to
connect
to
get
lab
calm
or,
if
you're,
using
the
demo
portal.
The
URL
of
the
demo
cloud
instance,
the
other
thing
that
we
have
to
ask
is
what
your
API
key
is
and
the
way
that
you
do.
This
is
by
creating
a
personal
access
token
for
your
user
account
on
the
respective
get
lab
instance
or
up
in
our
SAS
environment.
So
let's
go
ahead
and
do
that
now
we
click
on
view.
A
Environments,
you're,
gonna,
see
that
we
haven't
added
one
yet
so
go
ahead
and
click
on
add
environment.
Now
the
environment
name
is
whatever
you
want
to
refer
to
it,
as
so,
what
I'm
going
to
do
is
I'm
just
going
to
call
this
demo
cloud
Jeff,
just
in
case
I
happen
to
use
my
admin
account.
You
could
just
call
it
demo
cloud
if
you
wanted
to
and
then
you're
gonna
want
to
put
whatever
the
base
URL
is
now
I.
Don't
know,
we
know
what
the
base
URL
is
right.
A
Now,
let's
see
if
we
can
figure
that
out,
one
of
the
things
you'll
notice
is
that
this
is
part
of
a
modal
window
to
get
out
of
this,
when
you
click
out
it's
going
to
disappear.
However,
if
you
come
back
to
it,
it
should
all
you
stay
on
the
same
page.
It
should
keep
all
the
form
fields
filled
in.
So
let's
click
out
of
this
for
a
second
and
I'm,
going
to
pull
that
dashboard,
I'm
just
gonna
doing
a
new
tab,
so
I
go
to
new
town.
A
We're
gonna,
see
here's
the
URL
of
the
gate
lab
on
the
bus
instance
that
we
use
for
as
the
demo
cloud
I'll
right,
click
copy
link
address,
I
go
back
here,
go
to
add
environment.
Here's
the
base,
URL
I'll,
simply
paste
it
in
great.
That's
what
we
want.
One
thing
you'll
note
here
is
that
we
do
not
want
to
edit
the
slash,
so
we'll
simply
remove
that.
If
you
try
to
save
it
with
a
slash,
it
will
throw
an
error
message,
letting
you
know.
A
We
don't
want
that
in
there
on
the
personal
access
token,
these
are
the
instructions
that
are
part
of
the
gait
lab
documentation.
So
we
can
see
what
do
we
need
to
do
to
create
an
access
token?
Here's
the
steps
we're
done
login
to
get
lab
we're
to
go
up
into
our
account,
go
to
settings
user
settings,
select
the
access
tokens
go
ahead
and
create
it
and
to
make
it
work
within
the
demo
designer
you're
just
going
to
want
the
API
scope
enabled
so
let's
go
ahead
and
do
that
now
so
I
look
at
here!
A
Here's
the
Omnibus
instance
for
the
demo
cloud
right!
Click
new
tab
bring
this
up
here.
These
are
going
to
be
the
credentials
that
you
have
when
you
first
created
your
account.
We
also
use
that
to
create
your
account
on
the
demo
code
instance.
So,
whatever
get
up
handle
that
you
chose
or
email
address,
both
will
work.
A
You
have,
in
general,
I
have
a
little
bit
more
access
because
of
what
I've
been
dealing
with,
but
if
I
just
search
for
my
name,
I'll
find
my
group,
you
notice
that
was
a
little
bit
painstaking,
there's
also
a
bookmark
in
here.
So
if
we
go
back
to
here
and
you
click
on
the
my
career
but
in',
that's
actually
going
to
take
you
right
to
where
you
want
to
be
so
a
little
bit
of
a
shortcut
without
having
to
navigate
to
it.
Inside
of
your
group,
you
can
see
the
projects
that
you've
already
created.
A
We're
gonna
come
back
to
this
in
a
minute,
but
we'll
want
to
look
at
first
is
over
here
in
the
profile
or
the
settings.
I
think
settings
is
where
we
want
to
go.
If
we
recall,
but
on
the
left
hand
side,
you
see
access
tokens
when
creating
your
personal
access
token,
you
just
want
to
give
it
a
friendly
name,
I'm
gonna
say
get
web
demo
designer.
It
sounds
like
a
good
enough
name
for
this.
A
You
can
also
set
an
expiration
date
if
you'd,
like
you,
don't
need
to
I
know
that
Mikey's
gonna
be
revealed
in
this
video
I'm
gonna
revoke
that
key
right
after
the
video
is
completed.
So
you
don't
need
to
worry
about
the
vulnerability
of
the
key
being
exposed,
but
it'll
give
you
the
full
sense
of
how
to
add
things
in
here.
So
really
the
expiration
alone
on
the
scopes
make
sure
you
choose
API,
we
don't
need
any
of
the
others.
What
we're
doing
today
go
ahead
and
click
create
personal
access.
Token,
you
notice.
A
The
token
gets
added
here.
You
probably
gonna
want
to
add
this
to
your
1,
password,
vault
or
other
password
manager.
It's
only
going
to
appear
this
one
time
so
I'm
gonna
go
ahead
and
copy
that
add
it
to
my
password
manager
and
then
I'm
going
to
take
this
personal
access
token
and
go
ahead
and
add
it
on
to
the
get
web
demo
cloud
or
wherever
omnibus,
or
get
lab.
Comm
instance
that
you're
working
off
of
now
that
we've
added
our
key.
We
can
go
ahead
and
click
on
save
environment.
A
This
is
going
to
save
the
environment.
To
the
database,
and
the
first
thing
that
you're
going
to
see
is
we've
done
an
API
call
to
the
get
lab
instance
with
your
token,
to
see
what
you
can
access,
specifically
we're
looking
at
your
namespaces.
So
these
are
the
groups
in
which
you
can
store
new
projects
in
or
the
existing
projects
that
you
have,
I'm
not
going
to
scroll
down
and
muddy
up
the
screen,
because
I
had
a
lot
of
tests
that
I
was
working
off
of,
but
you
get
the
kind
of
the
idea
right.
A
So
what
we're
going
to
want
to
do
is
go
to
my
play
books
now,
when
you're
looking
at
creating
a
play
book.
The
first
thing
you
want
to
do
is:
give
it
a
name.
This
is
a
friendly
name
that
you
recognize
it,
as
none
of
this
is
going
to
appear
to
a
user
or
in
your
github
instance.
However,
the
play
book
description
is
going
to
be
used
as
the
project
description
when
you're
creating
a
new
project.
So
just
keep
that
in
mind.
A
A
Excellent
once
we
click
Save
play
book,
you're
going
to
see
that
the
left
side
is
going
to
populate
with
several
menu
items,
we're
going
to
ignore
runs
right
now
we
want
to
have
a
look
at,
though,
is
labels
and
milestones?
These
are
the
elements
that
you
need
in
order
to
create
issues,
because
when
you
create
an
issue,
you're
going
to
want
to
choose
an
existing
label
or
milestone,
so
it's
going
to
click
on
labels
right
now.
We
don't
have
any
labels
here.
A
We
can
go
ahead
and
add
some
we're
gonna,
add
the
generate
labels
ability
in
the
near
future.
So
for
right
now,
let's
do
a
typical
thing
where
we
create
a
backlog
column.
We
have
a
up
next
we're
going
to
do
a
in
progress
and
then
we're
going
to
do
it
done
so
we're
great
for
columns
today.
So
the
first
one
are
crates
called
backlog.
If
you
want
to
give
it
a
color
feel
free
I'm
not
going
to
worry
about
it
for
the
sake
of
this
demo.
A
These
are
issues
in
the
backlog,
excellent,
go
ahead
and
save
that
and
you
notice
that
backlog
label
is
now
listed
here.
This
is
not
going
to
have
the
exact
styling
that
you're
going
to
see
in
your
gait
lab
instance.
However,
it
is
going
to
give
you
a
very
good
representation
of
what
you're
going
to
see
it
once
this
runs.
Nextly
label
is
going
to
be
up
next.
A
Awesome
now
we've
got
our
four
labels
that
we
want.
We
can
add
additional
labels
in
here
as
well
and
let's
go
ahead
and
do
that
because
I'll
show
you
a
couple
tags
that
you
can
do
so
we're
going
to
say
that
this
is
going
to
relate
to
engineering
buck,
not
going
to
worry
about
a
description,
and
then,
let's
add
one
that
has
another
one.
That's
going
to
relate
to
new
feature
and
just
for
distinguishing
this
I'm
going
to
give
this
a
new
color.
A
A
The
idea
is
to
work
around
the
challenge
of
when
you
try
to
import
a
project
that
you
exported
a
long
time
ago
is
those
dates,
abuse
tale,
then
I'd
be
three
months
old,
so
doesn't
really
show
the
relevance
of
milestones
and
issue
tracking
and
progress
in
the
current
moment
when
you're
looking
at
dates
in
the
past
and
dates
in
the
future.
So
what
we've
done
is
come
up
with
the
idea
of
using
January
1st
2020
as
the
today
value
whenever
you're
running
an
import.
A
A
It's
going
to
show
relevance!
So
we
worked
around
and
we've
solved
that
challenge.
So
you
can
use
some
of
the
examples
in
this
table
as
a
basis
to
start
creating
it.
What
we're
going
to
do
is
I'm
just
going
to
create
three
milestones:
I'm
going
to
use
these
dates
and
as
an
example,
so
you
can
see
this
after
we've
imported
it,
so
we're
gonna
create
one
with
October,
10th,
2019
and
November
30th.
This
is
a
due
date,
so
when
I
click
create
milestone,
let's
give
this
the
milestone.
A
A
And
on
the
start
date,
this
is
where
that
relative
date
comes
in
so
2019
1001
and
the
due
date
of
2019
11:30,
and
you
can
put
whatever
dates
that
you
want
in
here.
You
can
go
as
far
back
as
far
the
future
as
you
want.
The
key
to
remember
is
that
2019
will
be
a
date
in
the
past,
20
20
or
20
21
or
any
date
in
the
future,
based
on
this
right.
A
So
we're
going
to
click
on
save
milestone
that
first
milestones
been
added
and
you'll
see
that
calculation
down
here
that
matches
the
documentation,
if
we
were
to
add
in
our
own
custom
dates
it's
going
to
show
whatever
value
based
on
what
you've
entered.
So,
let's
create
the
next
one
and
we're
going
to
say
version
2.0.
This
is
our
current
sprint.
If
you
will
for
the
what
we're
doing.
A
And
I'm
going
to
go
away
from
the
start
date,
just
because
I'm
looking
at
this
window,
it's
blocked
my
date.
I
forgot
what
it
was.
That's
okay.
This
gives
a
good
example
to
see.
What's
going
on
so
I'm
gonna
say
that
this
thing
started:
let's
see
if
today's
January
first
I'm
gonna
say
it
started
a
week
ago,
so
we're
gonna
go
back
and
say
around
Christmas
no
23rd
make
that
that's
a
good
number,
because
we
don't
want
sorting
on
Christmas,
so
we
go
2020
into
the
future.
We're
gonna
say
that
this
should
end.
A
Let's
say
three
months
from
now
so
I'm
gonna
say
331.
Okay,
that
makes
good
sense
go
in
to
hit
save
milestone,
so
you
notice
that
it
calculated
back
one
week
in
two
days
and
it
calculated
forward
two
months
in
four
weeks,
if
you're
looking
at
this
and
you're
like.
Why
is
that
not
three
months,
because
some
months
actually
calculate
as
five
weeks
on
the
computer
side
of
things?
So
that's
why
it
does
that
on
a
relative
dating
when
I
go
in
to
add
the
furture
one
for
version
3.0.
A
This
is
a
future
release,
we'll
go
ahead
and
add
this
and
we'll
say
this
is
going
to
start.
We
just
created
our
thing
for
331
s,
we're
just
create
a
new
one
that
starts
on
401,
and
this
is
going
to
end
at
the
end
of
June
relative
to
this.
This
will
obviously
add
dates
in
when
we
work
on
this
right,
so
save
the
milestone.
Now,
if
you
have
something
that
starts
in
three
months
and
something
that
ends
five
to
six
months
away,
so
that's
the
way
we
do
relative
dating
and
at
any
given
time.
A
I
can
go
ahead
and
this
so,
if
I
had
this
state
that
I
actually
wanted
to
use,
I
could
go
in
edit.
It
update
it.
Remember
that
anything
you
edit
or
update
will
only
affect
future
playbook
runs
it's
not
going
to
affect
anything.
You've
already
run
against
the
current
or
a
new
project.
All
right.
We
have
three
milestones:
version,
1
version,
2
and
version
3.
Let's
create
some
issues.
So
now
we
get
to
the
issues.
A
A
The
description
here
is
where
you
normally
see
the
markdown
field
for
the
alpha
release.
This
is
simply
a
text
field.
It's
not
going
to
render
the
right
markdown
that
you
want
to
see
so
I'm
gonna
keep
this
pretty
simple
with
just
a
sentence
description.
This
issue
is
tracking
all
of
our
scoping
activities
and
leave
it
a
doctor
right
now.
The
created
ax
is
the
relative
date.
You
are
required
to
put
a
creator
that
data
in
you
are
not
required
to
put
a
due
date
in
so
for
creator
that
I'm
going
to
say
that
we
are.
A
We
created
this
it's
to
be
used
at
October,
first,
as
the
first
1.0
milestone
and
we
used
1130
as
the
backup.
What
we're
going
to
do
is
we're
to
say
we
created
this
on
12:01
all
right
for
the
what
we're
doing
right
now,
and
you
understand
why,
in
just
a
second
when
I
do
this
so
the
due
date,
I'm
gonna
leave
this
alone
for
right
now.
A
I'll,
add
it
on
the
next
issue:
I'm
not
going
to
worry
about
it
for
right
now,
because
we
don't
really
know
the
due
date
for
of
this
project
scoping
the
weight.
If
you'd
like
you,
can
put
any
of
the
integer
values
that
are
allowed
for
that,
we're
going
to
add
the
user
assignment
values
in
the
next
release.
So
don't
worry
about
that
right
now
same
goes
for
the
group
level
epics.
So
the
milestones
you'll
see
the
milestones
that
we
have
here.
A
They
are
going
to
be
sorted
by
the
due
date
in
reverse,
chronological
order
for
you.
So
we're
going
to
say
this
is
for
version
2.0
and
we're
going
to
say
that
this
is
currently
a
doing
operate
or
a
doing
label,
as
well
as
where
it's
a
new
feature,
and
that
looks
like
it's
about
right.
You
are
free
to
use
scope
labels
if
you'd
like,
however,
we've
not
fully
tested
it,
so
you
may
run
into
mixed
results
but
feel
free
to
give
it
a
try.
A
Now
that
you've
got
your
first
issue,
we
can
go
ahead
and
add
additional.
If
we
choose
let's
go
ahead
and
do
a
version
2.0
proof-of-concept.
That
sounds
like
a
good
idea.
Add
this
in
awesome.
You
can
add
any
description.
You
like
not
going
to
worry
about
it.
We've
already
done
been
through
that
you
can
go
in
and
edit
descriptions
after
they're
added,
if
you'd
like
so
go
ahead
and
create
this.
What
day,
do
you
think
we
should
put
in
you
know?
A
Well
perfect
concept
today
is
January
1st,
let's
say
we're
going
to
start
it
next
week,
so
we're
gonna
say:
20
2001,
0
8.
That
sounds
like
a
good
time.
We're
gonna,
say
this
prayer
the
concepts
going
to
take
about
two
weeks,
so
we'll
do
0-124
best
guess
right
way
to
for
what
milestone
do
we
want
to
put
it
to
version?
2.0
sounds
right
and
we're
going
to
say
that
this
is
going
to
be
up
next.
You
notice
the
date
here
of
1/8
that
should
be
a
week
away.
A
Up
next
seems
like
the
right
place
to
put
it
go
ahead
and
save
that
issue.
Awesome,
we've
now
added
a
second
issue
feel
free
to
add
additional
issues
if
you
like,
but
we're
gonna
move
on
for
the
sake
of
this
demo.
So
let's
have
a
look
at
issue
boards
now
that
you've
created
your
board.
Let's
add
a
couple
lists
to
it.
So
when
you
go
to
a
list
you
can
choose
between
the
project
label.
Milestone
are
assigned
to
user,
the
milestone
assigned
to
user
becoming.
A
Certainly
we
have
a
couple
limitations
with
the
SDK,
we're
still
adding
on
the
project
label,
go
ahead
and
choose
any
of
the
different
labels
that
you've
added
store
credit
Kanban
board.
Let's
add
the
backlog
doing
done
and
up
next
we're
purposely
going
to
add
them
out
of
order.
So
I
can
show
you
how
to
rearrange
them
so
go
ahead
and
save
that
list.
A
When
you
go
to
backlog
doing
and
what
add
now
we
can
end
up
doing
is
we
can
move
from
left
to
right?
So,
let's
take
backlog
over
to
the
left
up.
Next
is
right:
doings
there
and
Dunn's
they're
perfect
we're
all
good
ready
to
go
so
what'll
end
up
happening
is
when
we
create
the
wedge.
You
run
the
playbook
it'll,
take
the
issues
that
we've
created
and
the
labels
that
we've
attached
those
issues
and
add
them
to
the
appropriate
columns.
The
same
way
it
works
on
the
gate,
lab
instance
itself.
A
So
now
that
we
have
all
those
pieces
in,
let's
go
back
and
review
it
all
go
ahead
and
run
this
way,
look
and
see
what
it
looks
like
so
issues.
We've
got
two
issues
doing
and
up
next.
This
should
show
up
on
the
first
board
that
we
created
in
two
different
columns.
That's
what
we're
looking
for
on
the
milestones.
We're
gonna
see
those
three
milestones,
all
the
ones
that
we're
working
off
over
in
version
2.0.
A
Now,
since
this
video
is
just
a
sample
you're
not
going
to
see
a
ton
of
depth
in
the
data
as
we
evolve,
our
as
you
take
the
ownership
of
creating
a
much
richer
data
set,
you
can
do
quite
a
bit
more
with
it.
So
let's
go
ahead
and
click
on
playbook
runs
you'll
notice,
you
have
not
run
a
playbook
I'm
gonna
go
to
run
what
you're
gonna
see
is
which
play
what
would
you
like
to
run
as
you
create
more
play
books?
This
list
is
going
to
get
a
little
bit
longer
on
the
environment.
A
A
You
can
put
this
in
an
existing
project,
keep
in
mind
that
if
you
try
to
run
it
against
the
existing
project,
if
there's
something
with
the
same
name,
the
error,
validation
and
the
alpha
release
is
probably
going
to
spend
an
error
that
may
not
be
as
friendly
as
you
like.
So
it's
not
going
to
break
your
environment
or
your
project.
However,
it
will
cancel
the
run
and
it
will
not
go
any
further.
A
Fantastic
now
and
click
run
playbook.
This
is
where
the
spinning
wheel
is
going
to
take
a
minute
just
to
run
everything
so
just
to
clean
things
up
what
I'm
going
to
do
is,
let's
have
a
look
back
at
the
demo
cloud.
Bring
up
the
dashboard,
I
haven't,
run
the
PlayBook
yet,
but
I
want
to
show
you
where
this
load
lives,
that
and
I'm
going
to
do
that.
My
group
thing
again
just
to
make
a
little
bit
easier
to
get
there.
So
we're
expecting
a
new
project
to
be
created
here.
A
A
You
noticed
in
the
top
left
corner
is
spinning
wheel.
It
took
a
couple
seconds
there
and
now
what's
happened,
is
you
see
the
playbook
runs?
We
see
a
link
that
has
the
full
name
space
of
this
project.
This
is
a
link
as
well.
I
can
click
this
it'll.
Take
it
over
there's
no
code
in
this
repository,
but
you
see
over
the
left
sidebar
there
are
issues.
So
what
we
want
to
look
at
is
finding
all
the
records
that
we
have
in
this
playbook,
so
we're
looking
for
labels,
our
issues,
our
milestones
and
our
issue
boards.
A
So
in
the
issues
here,
let's
go
to
the
list
we
can
see.
These
are
those
two
issues
that
we
created:
pull
up
the
proof-of-concept
and
you
can
see
there's
the
title,
there's
a
description
and
the
things
that
were
affected
so
here's
the
version
release
that
was
added
here
is
the
label
that
we
added
and
here's
that
weight
of
four
that
we
set
and
the
due
date
that
you
notice
got
populated
as
well.
So
that's
what
the
issues
look
like
great,
that
all
looks
good.
A
What's
up
like
a
project
scoping
same
sort
of
thing
here,
it's
got
multiple
labels,
fantastic.
Now,
let's
go
ahead
and
look
and
see
if
we
can
see
if
our
labels
are
there
great,
there's
all
the
labels.
That
was
easy.
So
look
at
milestones
and
there's
the
three
milestones
that
we
created.
You
know
notice
that
the
dates
here
are
all
relative.
So
based
on
running
this
today
on
April
28,
we
can
see
that
version.
2.0
was
in
the
midst
of
happening.
This
one
happened
back
in
January
to
March.
A
Remember,
even
though
the
dates
were
set
back
starting
in
October.
First
of
2019.
Everything
is
relative
to
the
date
of
today
right
so
three
months
before
April
28th
is
January
27th
in
the
relative
date
scheme,
as
well
as
here's,
the
upcoming
version,
3.0
great
that'll,
looks
fantastic.
Let's
have
a
look
at
the
board
so
up
in
the
left
hand
corner.
A
Remember
if
you
create
multiple
boards,
you're
gonna
have
to
choose
them
from
the
drop-down
list,
sprint
boards,
the
one
that
we
created
and
you
notice
that
we
have
these
different
columns
with
all
the
things
that
we
created.
So
this
is
what
the
display
are
that
we
chose
when
doing
it
in
the
designer
and
that's
the
columns
that
have
been
created
based
on
those
labels.
So
we
have
backlog
up
next
doing
and
done
and
there's
those
two
issues
that
we
had
created.
So
there
you
have
it.
A
That's
the
alpha
release
of
how
we
can
use
the
demo
designer
to
go
ahead
and
run
this
playbook
and,
if
you're
trying
to
do,
if
you
try
to
create
a
playbook
and
then
use
it
with
multiple
customers
during
a
demo
or
you
just
want
different
sandbox
environments,
you
can
run
it
again
with
a
different
name.
So
we'll
run
this
one
more
time
just
so
you
can
see
that
is
here's
the
run
book.
Here's
the
play
book!
A
Here's
the
environment
next
step,
a
fantastic
new
project,
I'd
put
in
the
same
namespace
I'm,
just
gonna
call
it
something
different
I'm
going
to
say
this
is
my
test
sandbox
for
April
28
and
there
we
have
it
and,
let's
hit,
run
playbook
again.
Wait.
Two
three
five
ten
seconds
depending
on
the
environment,
the
API
connection,
speed
and
you'll
see
the
second
one's
been
created.
So
there's
this
new
project,
there's
those
same
things.
If
I
make
any
modifications
to
that
playbook,
you
can
then
have
run
it
again
against
a
new
project.
A
Now,
against
the
same
project
and
you'll
see
the
additional
changes
that
you've
made
and
now,
when
I
go
and
look
at
the
group
here,
you'll
see
those
two
projects
now
appear
in
the
group.
So
there
you
have
it.
That's
the
new
demo
designer
and
the
easy
way
to
go
ahead
and
create
all
the
templates
that
you
want
with
dynamic
dates
and
then
populate
it
in
as
we
work
toward
the
beta
and
future
iterations,
we're
gonna
be
adding
a
lot
more
functionality
if
you're
curious.
A
A
Adding
we're
not
gonna,
be
able
to
add
everything
just
because
of
the
inherent
nature
of
how
some
of
the
resources
work,
but
it
gives
you
a
full
idea,
especially
around
groups
when
you're
looking
at,
can
I
get
xscape
multiple
projects
and
tie
the
issues
in
these
projects
to
group
level
epics
and
milestones.
The
answer
is
eventually,
yes,
so
that's
what
we're
working
towards,
but
this
gives
you
a
starting
point
to
see
how
we're
going
to
get
there.