►
From YouTube: GitLab Iterations MVC Demo
Description
Iterations Roadmap: https://gitlab.com/groups/gitlab-org/-/epics/2422
Feedback Issue: https://gitlab.com/gitlab-org/gitlab/-/issues/221284
A
Hello:
everyone-
this
is
Gabe
Weaver,
I'm,
the
senior
product
manager
for
the
project
management
group.
Within
the
plan
stage
today,
I'm
going
to
be
demoing
our
new
feature
in
the
plan
stage,
which
is
iterations.
We
are
shipping
our
MVC
in
the
next
release
and
I
wanted
to
give
you
a
quick
eye.
Light
iterations
are
at
the
group
level
which
allows
you
to
orchestrate
a
synchronized
cadence
across
all
subgroups
and
projects
in
terms
of
the
iteration
time
box.
A
The
goal
for
iterations
is
to
allow
you
to
associate
issue
to
more
than
one
time
box,
whether
that
your
milestone
is
a
program
increment
or
a
longer
term
goal.
Your
iterations
meant
to
be
a
shorter
term
sprint
or
multi
week,
time
box.
That
eventually
will
allow
you
to
better
understand
your
team's
velocity
over
time.
So
iterations
are
at
the
group
level
to
access
them.
You
hop
over
into
the
iterations
list
from
the
sidebar
inside
of
the
iterations
list,
you're
able
to
create
a
new
iteration
if
you're
familiar
with
milestones
would
be
fairly
familiar
with
this.
A
The
only
caveat
is
you
cannot
have
more
than
one
active
iteration
at
a
time
for
group.
So
if
you
try
to
do
that,
it
will
give
you
an
error
when
scheduling
this
is
intended
to
make
it
so
that
is
easier
to
have
like
size
time
boxes
over
time.
So
we
do
get
to
calculate
velocity
on
the
road.
It
will
be
consistent
over
time,
so
we're
gonna
start
our
iteration
on
July
27th,
we're
gonna
end
it
on
August.
1St,
let's
go
ahead
is
iterations
maiden
voyage.
A
You
can
add
a
description
just
like
you
can
the
other
place
where
you
have
any
markdown
editor
and
our
basic
iteration
overview
has
a
percent
complete
open
count,
closed
count
and
completed
count,
and
right
now
we
have
no
Eurasians,
but
this
is
signaled
to
be
upcoming.
If
you
want
to
edit
your
iteration
title
any
time
you
can
pop
back
over
into
this
view
and
edit
the
title
for
time
periods.
So
now
that
we
have
an
iteration
created,
we
can
hop
over
to
an
issue,
and
here
I
have
an
issue
that
I
had
created
previously.
A
That
was
associated
to
a
different
iteration.
I
want
to
go
in
here
and
add
this,
the
new
one
that
I
created-
and
this
will
save
it
and
associate
it
to
the
two
iteration
two.
So
if
I
refresh
this
page
now,
you'll
see
this
issue
show
up
you'll
see
the
status
is
in
progress
because
I'm
assigned
to
it
already.
If
I
know
there
is
no
signing
in
the
the
status
will
be
up
open
and
that's
it
for
the
MVC,
just
a
quick
overview
of
the
longer
term
roadmap.
A
What
we're
going
you
can
kind
of
see
here's
a
design
view
where
we're
gonna
be
adding
our
burn
down
or
burned
up
charts,
as
well
as
the
ability
to
filter
by
weight
counting
time
across
these
charts
at
all,
as
well
as
show
those
those
attributes
on
the
issue
list
itself.
We're
also
going
to
be
showing
you
the
iteration
report
and
downstream
subgroups
and
project
scope
to
that
specific
project.
So,
right
now,
when
the
problems
in
get
lab,
is
you
can't
have
the
the
milestone
report
view
in
a
subgroup?
A
If
that
subgroup
has
mass
or
issues
associated
to
that
parent
groups
milestone?
So
we
want
to
cascade
to
report
down.
So
it's
easier
for
teams
to
see
the
report
view
for
a
given
iteration
within
their
project,
your
subgroup
and
then
we're
also
going
to
be
extending
the
issues
area
down
below
with
a
group
by
feature
that
lets
you
group
by
label,
assignee
epoch
and
maybe
even
projects
or
groups,
we're
still
exploring
that
a
little
bit.
A
But
this
will
allow
you
to
get
a
better
sense
of
the
progress
for
four
different
kind
of
pivots
of
your
iteration
and
pretty
excited
about
that,
and
those
things
will
be
coming
in
the
future
as
well.
There
is
a
link
to
this
epic,
as
well
as
an
issue
for
feedback
on
the
iterations
NBC,
would
love
to
hear
from
you
and
understand
where
you'd
like
to
see
us
good.
Next,
thanks.