Agile planning gets a boost from new features in GitLab 18.10
GitLab 18.10 introduces a unified work items list and saved views to improve Agile planning. Teams can now manage epics, issues, and other work items in one place while saving filters, sorting, and display settings for repeated workflows. These changes reduce context switching and establish the foundation for broader planning views and customizable work item types. ## Unified Work Items List - Combines epics, issues, and other work item types into a single list. - Replaces the need to navigate between separate epic and issue pages. - Provides a foundation for future hierarchy and table views that show relationships between work items. - GitLab plans to bring additional planning workflows, including Boards, into the same unified experience. - The term “work items” supports future customization of item types and names instead of limiting the system to traditional “issues.” ## Why GitLab Is Making the Change - GitLab’s 2024 Agile planning vision identified separate epic and issue experiences as a source of friction. - The work items framework provides a shared architecture for consistent functionality across planning objects. - The new list and saved views represent progress toward that unified planning model. ## Saved Views - Save customized list configurations for future use. - Configurations can include: - Filters - Sort order - Display options - Help teams avoid repeatedly setting up common workflows. - Support consistent reporting, status checks, iteration planning, backlog refinement, and portfolio planning. - Saved views can be shared with teammates to standardize how work is reviewed. ## Future Planning Experience - Users will be able to move between list, board, table, and other views while retaining the same filter scope. - Planned hierarchy and nested table views will improve portfolio-level planning. - Future board capabilities may include swimlanes based on any work item attribute. - The unified framework is intended to make planning views more flexible and interconnected. ## Transition and Feedback - Existing workflows based on separate epic and issue pages may require adjustment. - GitLab acknowledges the change could be disruptive but says it reflects years of feedback and substantial investment in the work items framework. - Users are encouraged to try the new capabilities and provide feedback through GitLab’s feedback issue. Teams should begin testing the unified work items list and saved views in their everyday planning workflows, while offering feedback to help GitLab refine the transition.
Read original(opens in new tab)