►
From YouTube: GitLab Epics and Epic Template Tip
Description
Epics and Epic Templates (tip)
How strategic marketing organizes big projects and uses issue import as a way to create 'epic templates'. Effectively repeatable patterns of issues with the right labels, epics, milestones, and other key elements.
Get in touch with Sales: http://bit.ly/2IygR7z
A
Hello,
John
Jeremiah
here
with
the
get
lab
strategic
marketing
with
another
update
and
I,
want
to
share
a
tip
that
we've
been
using
around
how
we
manage
big
projects
epics.
We
have
effectively
an
epic
template
approach
that
we
can
use
to
create
repeated
epics
that
have
similar
sets
of
issues.
It's
challenging.
We've
been
wrestling
with,
we've,
been
building
out
a
series
of
efforts
to
around
go
to
market
and
we
want
to
create
epics
to
manage
related
work,
and
let
me
show
you
what
we
were
doing.
A
A
We
needed
to
do
it
over
and
over
it's
similar
kind
of
work
and
epics
are
a
great
way
of
managing
and
structuring
work,
and
you
can
have
an
epic
in
this
case.
You
know
I'm
in
the
parent
level.
Epic
of
this
the
use
case
go
to
market
one
I
even
have
a
link
in
here
that
points
to
the
epic
templates,
which
I'm
going
to
show
you
how
we
do
that,
and
we
then
can
see
that
within
this
epic,
there
are
four
sub
epics
at
the
moment.
A
There's
get
ops
source
code
management,
continuous
integration,
dev
sack
ops.
Each
of
these
then,
has
more,
you
know,
epics
under
them
to
break
down
the
work
and
we
broke
it
down.
We
chose
to
break
it
down
on
on
a
month-to-month
basis
as
a
way
to
pilot
it.
A
try
working
this
way,
and
so,
if
we
look
at
continuous
integration,
we
broke
each
of
these
then
down,
and
so
we
could
then
see
how
that
work
compressed
down.
So
in
the
first
epic
of
this
we
worked
on,
they
built
a
resource
page.
A
They
had
developed
a
look
at
that
issue
which
went
into
creating
that
where
William
and
Parker
worked
on
it
together
and
we
get
double
click
into
that
issue
will
go
down
to
the
to
look
at
that
now,
just
as
a
two
level
set,
we
that
was
the
MVC
I
want
to
go
to
the
template
view.
This
is
that
was
the
second
one
they
did
on
that.
A
So,
let's
go
back
to
that
first
epoch
and
here
was
the
first
epoch
of
creating
the
sales
resource
page
or
the
resource
page,
and
we
had
a
set
of
tasks
in
there
here.
We
wanted
to
attach
it
to
this
to
this
epoch
and
there's
the
associated
merge
request.
So
we
have
traceability
from
the
initiative
all
the
way
down
to
the
actual
work
down
to
the
merge
request
where
the
change
was
app
actually
implemented,
along
with
any
discussion
that
went
into
it.
A
So
we
have
complete
traceability
and
in
but
the
beauty
of
this
and
the
power
of
this
is
that
in
this
issue
to
create
the
sales
resource
page,
we
have
a
similar
issue
for
creating
the
source
source
code
management
resource
page,
and
so
we
have
consistency,
but
it's
different
based
upon
the
use
case.
So
how
did
we
do
that?
How
did
we
create
a
series
of
related
issues
that
all
roll
up
into
an
epoch
that
have
the
similar
structure
and
discussion
right?
A
So
how
did
we
create
this
model
without
doing
lots
and
lots
of
little
manual
work
of
changing
things
and
the
cool
really
powerful
thing
and
get
lab
that
we
can
do?
Is
you
can
import
issues
and
when
you
import
issues,
you
can
import
lots
of
detail
about
those
issues
and,
and
we've
and
I've
documented
how
you
can
do
it
as
an
epic
template.
A
So
in
this
handbook
page
we
described
how
you
can
go
through
this
process
and
and
if
you
I'll
give
you
the
link
to
this
page
at
the
end
which
walks
you
through
it
I'm
gonna.
Summarize
it
the
rest
of
this
video
of
how
it
works,
but
effectively
you
basically
go
to
issue
import.
You
use
this
guidance
of
importing
issues
from
a
comma
delimited
file
which
shows
you
how
to
do
it
and
it's
very
straightforward.
A
It's
very
straightforward
and
it's
also
very
very
powerful
and
we're
using
it
and
we're
using
it
as
a
way
to
do
this.
So
this
describes
the
process
of
doing
it
of
how
you
set
it
up
and
that
you
can
add
labels
due
dates
milestones.
You
can
attach
things
and
add
them
to
epics.
You
can
set
the
weights,
you
can
even
assign
it
to
individuals.
All
of
that
can
be
done
from
a
comma
delimited
file
of
the
input.
A
If
we
scroll
down
a
little
bit,
does
the
next
set
of
steps
of
saying,
let's
find
customer
references
and
the
specific
tasks
that
would
go
into
that
with
links
all
of
that
gets
built
into
the
issue?
So
that
way,
when
we
say,
let's
do
another
use
case,
the
set
of
tasks
are
there
and
we
can
quickly
update
this
format
and
import
it
in
without
you
know
having
to
do
it
all
manually
and
it
works
remarkably
well.
So
this
was
the
input
from
there
and
and
basically
the
steps
are
quite
straightforward.
A
You
create
a
spreadsheet
that
has
the
details
of
how
you're
going
to
do
it.
The
way
I
did
this
because
I
was
going
to
do
it.
Multiple
times
is
I
used
addition
and
concatenation
when
this
describes
how
I
concatenated
elements
and
so
I
basically
have
a
spreadsheet
that
has
all
the
raw
elements
and
it
assembles
the
two
columns.
You
need
the
title
and
the
description
and
that's
what
this
worksheet
describes.
How
I
did
that
and
if,
if
anybody
wants
to
see
the
raw
spreadsheet
I
can
I'd
be
happy
to
share
that
with
someone.
A
If
you
reach
out
to
me
right
now,
it's
but
it
is,
it
is
a
little
bit
there's
a
little
bit
of
things
going
on
to
it,
where
it's
a
bit
fragile
I've
got
to
make
sure
I,
don't
change
anything
to
break
it.
I
do
think,
there's
some
important
tips
and
hints
before
you
do
this
test
it
in
get
lab.
You
know
we
don't
really
delete
issues,
you
can
do
it
from
the
API,
but
as
a
user,
you
just
don't
delete
issues,
you
can
close
them,
but
they'll
still
be
there.
A
So
before
you
import
a
hundred
or
200
or
lots
and
lots
of
issues
and
make
a
mistake,
create
a
project
off
the
side
and
practice
and
make
sure
it's
going
to
work.
The
way
you
want
it
to
do.
The
other
thing
is
use
a
real
issue
to
draft
any
quick
action
codes.
You're
going
to
use,
make
sure
that
they
would
work
can
real-life
and
then
paste
them
into
your
spreadsheet.
A
That
way,
your
quick
actions
will
work
and
you'll,
make
sure
that
you
don't
have
typos
in
them,
and
so
you
just
create
one
issue
and
open
a
comment
and
start
to
write
your
quick
actions
and
then
the
last
one
is
the
order.
When
the
spreadsheet
runs,
it
will
run
and
import
from
the
first
one
to
the
last
one.
A
We
can
get
a
sense
as
to
where
we're
at
on
the
different
status
of
these
epics,
and
then
we
can
drill
into
the
related
issues
associated
with
them,
so
powerful,
powerful
capability
by
using
comma
delimited,
import
and
thinking
about
and
planning
in
advance
how
you
want
things
to
be
structured
and
how
you
want
things
to
be
related.
You
can
build
out
very
powerful
sets
of
epics
of
related
work.
If
you
want
to
learn
more
about
this,
the
page
I
was
referencing
where
I
showed
how
we
set
up.
A
The
epic
templates
for
strategic
marketing
is
bitly
GL,
epic
templates
notice
the
uppercase,
and
then,
if
you
want
to
read
the
documentation,
this
link
will
take
you
to
the
issue:
import,
documentation,
bitly
issue
import,
that's
it!
If
you
have
feedback,
please
feel
free
to
open
a
merge
request
and
contribute.
Add
to
these
handbook
pages
help
make
them
better,
be
glad
to
answer
questions.
If
you
have
them,
you
can
catch
me
on
twitter.
You
can
ping
me
any
way
you
like,
but
with
that
good
luck
and
please
contribute
please
share
and
thank
you
very,
very
much.