►
Description
I'm thrilled to share a sneak peek into our upcoming plans for the next year with our community.
📋 Epic Migration to Work Items: We're dedicated to ensuring a seamless transition as we migrate epics to work items, preserving your familiar mental model while unlocking new possibilities. Expect epic assignees, milestones, rollups, and more!
🔄 Unified Saved Views and Queries: Once epics are settled, we're focusing on simplifying your experience in Plan. Get ready for a unified hub where you can effortlessly create, save, and visualize queries tailored to your needs.
🔍 Consistent Filtering Across Plan Features: We're harmonizing filtering across all Plan features, making your life easier and streamlining our codebase.
🗺️ Enhanced Roadmaps Experience: Say goodbye to limitations! Our revamped roadmap experience will bring you reactive interactions, dependency tracking, 'group by' segmentation, and more.
📊 Improved Boards Experience: We're taking our boards to the next level with features like saved views, board templates, enhanced visibility, and more.
Stay tuned for these exciting updates that will make your GitLab experience even better. Don't forget to hit the subscribe button to stay in the loop.
You can find our public Now-Next-Future here:
https://gitlab.com/groups/gitlab-org/-/epic_boards/41528?label_name[]=devops%3A%3Aplan&label_name[]=group%3A%3Aproduct%20planning
Please mention @amandarueda with any questions on GitLab issues or epics!
A
Hello,
everybody
I'm,
Amanda,
ruida
I,
am
the
senior
product
manager
with
product
planning
here
at
gitlab
and
I
want
to
walk
you
through
our
fiscal
year.
24
roadmap
for
the
product,
Planning
Group,
so
I've
broken
this
down
by
kind
of
what
we're
working
on
now
and
what
we're
working
on
in
the
future.
A
So
while
you
might
see
the
same
labels
widget,
for
example,
on
epics-
and
you
see
the
labels
widget
on
issues,
those
are
two
separate
implementations
with
the
work
items
framework
that
we're
going
to
be
migrating
to
we're,
creating
a
single
object,
which
is
a
work
item
and
the
widgets
on
top
of
those
for
labels
and
assignee
and
weight.
And
all
these
things
are
extendable.
So
when
we
have
a
work
item
object,
we
can
then
create
work,
item
types
and
different
types
will
be
epics
issues,
tasks,
okrs
objectives
and
key
results
in
the
future.
A
We
could
extend
this
to
potentially
tickets
for
service
desk
as
an
example,
incidents
and
so
forth.
So
the
first
thing
that
we
plan
to
migrate
to
the
work
items
framework
will
be
epics
and
we
are
currently
focused
on
creating
feature
parity
between
the
existing
ethics
record
and
the
future
work
items.
A
Ethics
record
so
as
an
example
currently
work
items
which
you
might
be
interacting
with
today
through
tasks,
do
not
have
the
linked
items
widget
at
the
time
of
this
recording,
so
we're
building
that
in
work
items
so
that
when
we
migrate
the
data
from
the
current
framework
to
the
new
work
items
framework,
all
of
the
data
is
captured
and
finds
its
place
in
the
new
work
item.
When
we
do
the
migration,
you
will
not
see
much
change
on
the
front
end.
A
This
is
a
a
design
example
of
what
it
may
look
like
we're
still
working
on
that
detailed
design.
But
what
you
will
see
in
terms
of
change
will
be
additional
features
so
in
in
this
case,
I'm
demonstrating
an
epic
which
has
a
Siamese
and
that's
not
something
that
we
have
today.
I
have
a
weight
and
a
milestone
and
an
iteration.
These
may
not
be
things
that
we
include
in
the
future,
but
these
are
things
that
will
certainly
be
possible
because
it's
very
Plug
and
Play
once
we've
migrated
to
work
items.
A
So
not
only
does
this
become
a
better
experience
for
you
from
a
visual
perspective,
we
can
offer
much
more
robust
features.
The
health
status,
for
example,
of
the
child
items
will
be
very
easily
rolled
up
because
they
will
all
be
on
the
same
back
end
database
structure
from
the
very
top
to
the
very
bottom
record,
so
FX
into
nested
epics
into
issues
into
tasks,
for
example.
A
We'll
be
able
to
do
things
once
everything
is
migrated
to
work
items
like
display,
different
work
item
types
like
tasks
on
different
views,
That,
You,
Don't,
See
today,
for
example,
boards
having
tasks
road
maps
having
issues
things
like
that.
So
this
is
a
really
big,
a
big
project
for
us.
In
terms
of
just
this
year,
amount
of
work,
but
the
payoff
is
equally
as
big
for
both
customers
and
for
gitlab,
because
we
are
able
to
reduce
a
lot
of
Legacy
Tech
debt,
maintenance
and
complication
in
the
code
with
this
new
simplistic
model.
A
Once
we're
finished
with
the
migration
of
the
issuables
to
the
work
items
framework,
the
product
lighting
team
will
be
focused
on
two
efforts
to
unify
inconsistency
in
your
your
front-end
experience
with
some
of
our
features,
so
unified
saving,
save
views
and
queries
is
an
attempt
to
take
all
of
the
existing
views.
You
have
issue
list.
Epic
list
issue
board,
epic
board
road
maps,
and
you
have
them
in
in
a
way
that
you
have
to
navigate
to
all
these
different
areas.
A
It's
not
very
easy
to
find,
depending
upon
where
you're
starting
in
the
application,
so
we're
looking
to
create
a
single
and
I'm
going
to
go
ahead
for
a
second,
so
I
can
show
you
the
example
to
create
a
single
page
where
you
can
kind
of
launch
your
query
and
then
once
you've
configured
your
query.
You
can
then
say
and
I
want
to
see
it
as
a
backlog.
I
want
to
see
it
as
a
Sprint
planning
board.
A
I
want
to
see
it
as
a
Gantt
chart
so
that
you
don't
have
to
navigate
all
of
the
different
paths
in
gitlab
to
get
to
where
you
want
to
go.
You
stay
in
one
place
and
a
lot
of
modern
tools
are
doing
this
sort
of
thing
where
you
stay
in
one
place
and
you
render
the
visualization
right
on
that
page.
The
other
thing
that
we
are
going
to
be
focused
on
is
consistent,
filtering
across
plan
Futures.
A
So
today,
if
I,
if
I
come
to
the
filter
bar
in
the
Epic
list
or
issue
list
or
I
go
to
the
roadmap,
filter
bar
or
I
go
to
the
boards
filter
bar
those
are
all
different
experiences.
You
may
have
different
options
available.
The
data
that's
returned
based
on
your
filters
might
be
slightly
different
and
that's
because
each
of
those
pages
are
using
different
filter
engines
and
different
query
logic,
and
so,
as
part
of
this
overall
kind
of
efficiency
in
views
we
are
also
going
to
include
is
standardization
and
efficiency
in
filtering
experience.
A
So
this
whole
experience
with
accessing
your
data
and
viewing
your
data
we're
attempting
to
make
a
lot
more
efficient,
intuitive
and
delightful,
and
the
other
thing
that
I
want
to
highlight
is
I
mentioned
here.
Unified
saved
views
right.
We
are
looking
to
improve
that
saving
process
as
well.
Today,
if
you
go
to
boards,
you
just
have
this
big
long
list
and
depending
upon
how
many
boards
you
have
it's
a
you-
know,
infinite
scrolling
in
lists.
You
cannot
save
in
in
road
maps.
A
But
we
understand
that
the
road
maps
today
are
are
are
usable,
but
they
definitely
can
be
elevated.
So
what
we're
looking
to
do
is
launch
a
number
of
of
improvements
visually
from
just
an
aesthetic
perspective,
but
really
the
meat
and
potatoes
of
what
we
want
to
ship
are
efficiency,
Improvement,
so
reactive
and
real-time,
inter
Integrations,
so
or
I'm.
Sorry
interactions.
A
So
when
you're
viewing
that
that
road
map-
and
you
see
that
something
is
you
know
it's
going
to
come
in
late
or
you
need
to
modify
that
timeline
rather
than
having
to
launch
a
new
tab
to
edit
the
start
and
due
date
of
that
epic
being
able
to
kind
of
drag
and
drop
and
move
that
around
the
roadmap
to
automatically
update
that
metadata.
Also,
so
we
want
to
really
get
into
providing
more
visualizations
and
information
about
dependencies.
So
today
we
do
give
you
the
little
kind
of
blocked
icon
for
that
epic.
A
But
we
don't
give
you
much
more
information.
You
can
hover
and
see
a
little
bit
but
having
some
visual
understanding
about
those
dependencies.
So
at
a
glance
you
can
get
a
very
quick
understanding
of.
Is
this
thing
blocked
if
it's
blocked
what's
the
status
of
the
blocker?
And
how
does
this
affect
my
timeline?
A
A
You
know
if
we
imagine
that
we're
going
to
get
the
road
map
to
a
state
where
you
can
very
easily
gauge
the
temperature
of
your
initiatives
and
when
they
might
be
off
track,
be
able
to
very
easily
understand
when
why
how-
and
so
that
becomes
a
very
valuable
tool
that
you
can
then
share
with
your
stakeholders.
That
leaves
little
questions
to
follow
questions
after
sharing
so
improving
the
shareability
of
that
roadmap
and
then
really
optimizing
for
efficiency.
A
Workflow
efficiency
I
mentioned
the
ability
to
kind
of
change
the
dates
on
the
actual
roadmap
itself,
without
opening
a
new
page,
but
really
for
any
metadata
today
that
you
want
to
change
on
an
epic
while
you're
viewing
the
roadmap.
You
have
to
open
a
new
page,
so
our
goal
will
be
to
allow
you
to
edit
that
stuff
right
from
within
the
roadmap,
without
having
to
open
a
new
page
or
a
new
tab
every
time
and
then
just
additional
kind
of
configuration
enhancements
so
being
able
to
sort
or
reorder
saving
a
configuration.
A
A
I'm
very
excited
after
road
maps
were
coming
to
boards.
Boards
are
have
very
good
adoption
today
and
they
really
get
the
job
done.
They're
excellent
tool
to
have
in
your
daily
stand-up
or
review
sessions,
but
if
they
can
benefit
from
some
additional
love
as
well.
So
things
that
we're
going
to
be
looking
at
in
terms
of
improving
boards
will
be
those
save
views,
including
the
personal
save
views,
as
I
mentioned.
A
So
group
grouping
by
assigning
grouping
by
Milestone
grouping
by
label
introducing
board
templates,
improved
visibility
into
parent
and
related
records.
So
knowing
that
an
issue
is
part
of
a
certain
initiative
or
a
feature
and
I
don't
have
it
here,
but
also
improved
visibility
into
dependent
records
right
so
again,
on
this
board,
we
show
you
a
little
blocking
icon
or
something's
blocked.