►
Description
Conversation between Jackie Gragnola and Eric Brinkman regarding event support processes and optimization requests that would help us be more efficient in epic and issue management within GitLab.
Related issues:
Ideas to make GitLab more marketing-friendly - https://gitlab.com/gitlab-org/gitlab-ce/issues/54163
Calendar view (ideal state brainstorm) - https://gitlab.com/gitlab-org/gitlab-ce/issues/55629
Canned responses in issue comments - https://gitlab.com/gitlab-org/gitlab-ce/issues/62555
Issue titles within issue templates - https://gitlab.com/gitlab-org/gitlab-ce/issues/62553
Calendar of issues - https://gitlab.com/gitlab-org/gitlab-ce/issues/54134
A
They
starting
over
from
where
I
began.
So
this
is
the
list
of
all
the
events
that
were
approved
to
go
to
I
need
to
start
actioning
on
all
the
tasks
related
to
marketing
programs.
So
I'm
gonna
show
an
example
of
DevOps.
Today's
Portland,
since
I
haven't
created
the
epic
yet
so
from
here.
I
have
all
the
details:
I
need
from
Emily
Lear's
I
have
that
we
will
need
a
follow-up
email.
A
A
Yep
'ok
and
then
I
need
to
drop
in
all
of
the
details.
So
there's
no
epic
templates,
which
is
another
request
if
you're
not
able
to
do
cloning,
but
I
will
I
have
a
little
sticky
note
on
my
computer.
That
has
the
code
and
I
need
to
put
into
this
epic
section
description
section
and
it's
mainly
to
make
sure
that
we're
able
to
link
back
on
everything
and
that
anybody
who's
looking
at
the
epic
can
find
what
they
need
and
so
that
the
field
marketers
can
work
off
of
this.
A
And
then
I'm
gonna
add
the
labels
later
as
like
a
bulk
steps
that
I
do
because
otherwise
takes
me
too
long,
but
she
said
we
won't
need
a
landing
page.
So
I
can
remove.
This
I
will
need
an
invitation.
We
will
have
a
follow-up
email
and
we
will
need
to
create
the
Salesforce
campaign
and
the
Marketo
pro
girls,
so
I,
Save,
Changes
and
now
I
have
to
go
and
create
all
of
these
issues
so
that
we
can
have
separate
due
dates
and
separate
er
eyes
for
each.
A
A
Another
request
is
like
I,
don't
know
why
issues
can't
have
titles
already
included
in
the
template
part,
but
I
have
to
type
in
each
issue,
I
create
and
then
I'll
do
a
couple
of
new
things,
but
for
the
sake
of
time,
I
won't
do
it
here.
Actually,
we
might
have
a
speaking
session,
and
this
is
all
really
just
webcasts
and
I'll
assign
it
to
me
I'm
just
going
to
say,
I
need
to
have
it
done
by
the
end
of
the
week
whenever
we
go
to
move
to
work
in
progress
and
I'll
submit
the
issue.
A
Add
the
epic
link
that
everything
links
back
a
little
bit
easier
and
then
create
the
due
dates
which
I
have
tracked
in
a
separate
Google
Doc,
because
we
don't
really
do
like.
We
can't
do
can't
charts
as
much
so
I
work
off
of
the
Google
sheet
with
a
bunch
of
formulas
in
it.
But
we
leaders
needs
to
give
me
the
copy,
so
she'll
be
here
and
I'll
need
the
two
days.
A
Copy
all
the
issue
leaks
and
put
them
back
into
the
epoch
as
related
issues,
okay,
yep
and
then
that
way
everything
is
linking
appropriately
and
the
main
issue.
And
then
we
have
an
invitation.
I'm
just
gonna
create
these
three.
For
now,
but
I'll,
say:
okay,
I've
done
that
one
I've
done
that
one
and
then
marketing,
opps,
I'll
ping
JJ
to
say,
remember,
to
pay
Phyllis
clean
issue
in
projects
and
Link
it
back
to
this
issue.
So
I
got
like
a
piece.
A
This
is
a
more
simple
event,
because
we
don't
have
a
landing
page,
but
sometimes
we
will
have
multiple
landing
pages
for
a
corporate
event.
It
can
take
a
lot
of
time
to
just
create
all
the
issues
cradle.
The
epic
drop
in
all
the
coffee
everywhere
and
right
now,
I'm
gonna
have
to
do
this.
I
mean
today
for
probably
11
events,
and
we
also
have
Agnes
and
Jenny
doing
the
like.
A
B
What
it
makes
sense,
all
of
these
already
documented
it.
You
know
some
of
these
are
I,
think
relatively
easy
improvements,
one
of
the
things
that
you
kind
of
mentioned,
or
at
least
that
I
kind
of
gleaned
through
your
workflow
here-
was
it'd,
be
nice
to
I
just
copy
or
clone
an
epoch,
but
an
entire
epoch
and
issue
tree
and
kind
of
call
that,
like
it
like
a
project-
maybe
maybe
it's-
maybe
it's
a
like,
even
at
the
project
level
that
you
could
potentially
clone
a
project,
it
would
include.
B
A
A
That's
what
I've
documented
in
that
first
section
is
basically
that
step
by
step
process,
I'm
in
training
up
a
new
marketing
programs
manager,
so
I
need
to
need
its
document,
everything
a
little
bit
clearer
anyway,
and
then
these
were
like
kind
of
requests.
If
we
can't
get
to
like
that,
bigger
ideal
state
and
then
if
we
could
have
templates
for
epics
that
can
save
a
little
bit
of
times
having
issue
titles
related
to
their
templates
and
I,
don't
know:
did
you
have
any
other
questions
about
the
cross?
That's
the
general
first,
just.
B
A
When
I
say
cloning,
epics
I
guess
I
need
both
cloning,
the
epic
and
the
related
issues,
which
is
what
you
were
just
describing
doctrine,
but
also
epic
templates,
would
be
essentially
function
the
same
way
as
epic.
Creating
an
issue
template
right
now,
I
think
it's
a
little
wonky
that
and
maybe
there's
a
way
that
I
don't.
This
is
all
I
know.
Is
that
create
an
epoch?
A
You
have
to
create
new
epoch
over
here
from
the
epic
list,
and
then
you
can
edit
the
epic,
but
in
the
way
that
you
can
create
a
new
issue
right
here.
It
seems
odd
that
you
can't
create
an
epic
with
a
template
so
including
the
description
that
you
and
the
tagging
that
you
have
in
an
issue:
cloning
situation
or
issue
there.
B
There
is
one
piece
of
functionality:
that's
maybe
not
super
explicit
that
might
be
able
to
help
you
in
the
meantime,
which
is
you
could
the
information
you
desire
to
put
into
an
epic
template?
You
could
put
that
into
an
issue
template
and
just
create
an
issue
and
then
quickly
promote
it
to
an
epic.
Did
you
know
that
we
have
promote
functionality,
yeah.
A
When
we
were
starting
to
use
epics
in
December,
we
had
the
field.
Marketing
managers
try
to
promote
issues
to
epics,
and
we
found
that
I
think
that
labels
for
breaking-
and
there
are
some
other
things
that
were
falling
off
as
they
did
that
so
they
started
they
kept
their
own
process
of
creating
issues
so
that
maybe,
if,
if
those
problems
were
fixed,
maybe
we'd
be
able
to
use
that
in
some
manner
where
one
submits
to
web.
You
promote
it,
not
your
third
I'm,
not
sure.
A
B
A
And
it's
because
of
the
broken
piece:
that's
the
promotion,
because
originally
our
plan
was
once
an
issues
flip,
promote
it
to
epoch
that
wasn't
working
and
field
marketing
was
moving
so
fast.
They
needed
to
just
stay
with
the
same
process
they
already
had,
so
my
adjustment
still
be
able
to
use.
Epochs
was
to
like
take
on
creating
epochs
and
creating
the
issues.
Is.
B
A
Possibly
I
would
need
to
pull
in
field
marketing,
like
Leslie
or
Emily
leaders
and
Emily
Kyle,
to
see
what
what
that,
like,
what
problems
that
might
create
because
they
work
off
of
this
and
I,
don't
know
if
this
is
just
like
a
sieve
process
like
they
didn't
want
to
change
process,
so
they
just
kept
on
doing
issues
but
I
first
see
that
as
a
possible
solution,
and
then
they
have
all
the
information
I
need
here.
I
would
just
edit
the
description.
A
A
And
it
might
look
a
little
bit
confusing
since
right
now.
If
anybody
in
the
organization
wants
to
see
the
event
we're
going
to,
they
can
look
right
here
and
then
they
can
click
to
the
main
issue
for
more
details.
And
if
you
have
that
long
of
an
epic
description,
then
you
can't
see
the
related
issues
as
easily
because
it's
it
falls
down
the
page.
But
there's
potentially
is
a
solution.
How.
B
About
for
your,
how
about
for
your
own
workflow,
though
so
like?
Let's,
let's
assume,
I'm,
not
going
to
make
any
changes
to
your
workflow
and
you're
gonna,
see
an
issue
that
gets
a
whip
label
and
you're
assigned
to
it
and
you're
gonna
go
make
your
own
epic
and
your
own
issues
and
do
all
the
things
that
you're
currently
doing
today.
Could
you
start
with
an
issue
like
a
brand
new
issue
with
an
issue
template?
That
is
what
the
information
you
need
in
the
epic
and
then
as
soon
as
you
make,
that
issue
like
promoted
immediately.
A
And
because
the
issues
all
have
different
dris
and
due
dates,
I
have
to
create
them
separately
and
to
show
you
how
it
now
visually
appears
like
the
way
I
work
out,
and
it's
document
at
the
bottom
is
like
a
calendar
of
views.
I
can't
see
like
if
I
could
just
look
at
this
week.
Let's
do
what
day
I
can
easily
prioritize
what
I
need
to
work
on,
because
I
can't
see
a
calendar
of
my
upcoming
issues.
A
Yeah
I
work
out
of
these
issue
views
in
my
calendar,
where
on
Mondays
I
focus
on
managing
all
the
epics.
So
what
I
already
described
for
you
that
creating
that
makes
creating
supporting
issues
but
then
comes
the
actual
execution
piece,
so
it
on
Tuesday
I'm
looking
at
what
are
all
of
the
follow-up
emails
that
need
to
take
place
by
due
date
in
ascending
order,
so
the
next
email
up
I
need
to
have
DevOps
is
easy,
Toronto
and
Chicago
done
as
of
this
week.
A
Right
now,
I'm
waiting
on
coffee,
so
I'm
kind
of
like
struggling
with
that
and
then
I
can
look
forward
and
say:
okay,
this
copy
is
due
May
31st,
which
is
tomorrow.
So
I'll
go
in
and
if
I
haven't
gotten
the
copy
from
the
Field
Marketing
Manager
I'll
ping
them
in
the
issue,
comments
and
just
say
just
a
reminder:
I
need
this
by
tomorrow.
Just
remaining
lie
and
I'll.
Do
that
to
make
sure
we're
on
track
to
have
the
emails
go
out
in
a
timely
manner,
but
right
now,
I
have
all
of
these
coming
up.
A
That
I
need
to
keep
organized,
and
so
it's
kind
of
bringing
those
like
similar
tasks
into
certain
blocks
of
time.
It's
what
makes
me
not
have
to
shift
gears
from
like
creating
epics
to
working
on
Marketo
and
creating
issues
or
creating
emails,
going
back
to
salesforce,
creating
campaigns
just
trying
to
manage.