GitLab / Product Planning

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!

Linked Work Items https://gitlab.com/groups/gitlab-org/-/epics/7459

How a GitLab Product Manager uses GitLab in product planning tasks - Using a "Now-Next-Future" epic board to create a product roadmap.

How a GitLab Product Manager uses GitLab in product planning tasks - When you need to update the metadata associated with issues under a single epic, don't open each issue in its own tab, use the issues list filtered by the epic to accomplish your task in fewer clicks!

How a GitLab Product Manager uses GitLab in product planning tasks - how epic dates work, what's the difference between "inherited" and "fixed", and which do I use?

Here's the issue I referenced in the video: https://gitlab.com/gitlab-org/gitlab/-/issues/231511

How a GitLab Product Manager uses GitLab in product planning tasks - In this video, I walk through converting an idea which has been discussed in an issue to a feature via epic promotion. Then I decompose that epic into individual issues which I can schedule in upcoming milestones.

How a GitLab Product Manager uses GitLab in product planning tasks - Breaking down an Initiative using GitLab epics and issues

No description provided.

How a GitLab Product Manager uses GitLab - Reviewing issue progress in the current milestone.

How a GitLab Product Manager uses GitLab in product planning tasks - Finding features to schedule for my team for the next 1-3 milestones in GitLab

How a GitLab Product Manager uses GitLab in product planning tasks - Planning the next milestone.

Related issue: https://gitlab.com/gitlab-org/gitlab/-/issues/392889

See more information: https://gitlab.com/groups/gitlab-org/-/epics/8294

Read more about using health status on issues:
https://docs.gitlab.com/ee/user/project/issues/managing_issues.html#health-status