Digital.ai Agility 26.2：連接 Release 從規劃到交付

Digital.ai Agility 26.2 focuses on making that connection easier. The release expands visibility into release scope and progress, brings release and OKR information into the Data Mart, and strengthens Agility Sync for organizations coordinating work across multiple systems. 

The result is a more connected planning experience that helps teams spend less time reconstructing status and more time understanding whether planned work is aligned, progressing, and ready to deliver. 

The release planning gap is a visibility gap 

Product and delivery leaders need to understand what is included, how much work is complete, who owns the remaining work, and how that release relates to broader plans and objectives. Agility 26.2 brings more of that information directly into the planning experience. 

Release Planning now provides at-a-glance release details directly from board column headers, including target dates, time remaining, and progress against the work assigned to the release. A new List view also gives users access to active and closed releases so historical release information remains available alongside current planning. 

Teams can also group work by release on planning boards, while Release Details organizes associated Portfolio Items, Stories, and Defects to provide a clearer picture of release scope. Instead of treating release status, scope, and execution as separate views of the business, 26.2 brings them closer together. 

五種方法 Digital.ai Agility 26.2 improves enterprise planning

See release health without leaving the planning board

Release Planning Board column headers now provide a tooltip with important release information such as the target date, time remaining, and completed work compared with total work. Overdue releases and progress indicators make schedule risk easier to identify while teams are actively planning. Planners can now evaluate release health in context instead of interrupting planning to search for status elsewhere.

Understand exactly what is inside a release

Release Details now makes associated work easier to inspect across both Agility Core and Rooms 2. Portfolio Items, Stories, and Defects are organized by type, while the Child Items view consolidates release work into a grid with information including owner and status. That gives teams a more direct way to answer three important questions: What is included in this release? Who owns it? Is it complete?

Plan across releases without losing the work context

Teams can now group work items by Release directly on several planning boards, including Portfolio Kanban, Storyboard, Sprint Planning, and Dependency views, with corresponding support across Rooms 2 experiences. 

Unassigned work remains visible rather than disappearing from the planning picture. This helps teams examine how work is distributed across releases and spot imbalances in scope while remaining in the planning context they already use.

Connect release execution and OKRs to broader analytics

Agility 26.2 makes Release Planning 2.0 information available through the Data Mart. Release metadata and associated work can therefore become part of custom analysis and reporting. 

OKR information is also now available in the Data Mart, including Objectives, Key Results, and their relationships to work items. Product and program leaders can use that information to create reporting that brings strategic objectives and execution data closer together. The Objectives list also adds Excel export for Objectives and associated Key Results, giving stakeholders another way to share or analyze OKR information outside Agility.

Keep work aligned across the tools teams already use

Large organizations rarely execute all work in a single system. Agility Sync exists to help maintain alignment when teams use different tools, and 26.2 introduces several improvements to that experience. Agility Sync now supports Epic synchronization from GitLab to Agility 以及來自 Agility to GitLab, and adds support for Jira Data Center 10.3.x. 

Operational improvements also make synchronization easier to manage at scale. Status-based log tabs reduce the amount of information loaded at once, manual refresh lets administrators work through multiple events without repeated page reloads, and configurable Auto Resync gives teams more control over how failed events are retried. 

The release also includes fixes designed to preserve parent relationships, prevent duplicate work items when events arrive out of sequence, reduce synchronization slowdowns, and improve log reliability. 

現在要採取的四個步驟 

Use release health during planning, not just during status reviews. Take advantage of release progress, target-date indicators, and in-context scope views to identify risk while teams can still respond to it. 

Bring release and OKR information into your reporting model. With both data sets now available through the Data Mart, review where reporting can connect execution progress with strategic objectives rather than treating them as separate conversations. 

Review cross-tool synchronization. If GitLab, Jira Data Center, Azure Boards, or other connected systems are part of your operating model, evaluate the Sync improvements and determine where they can reduce manual reconciliation and administration. 

Prepare for deprecated features before 27.0. Guest Collaborator, Team Scheduling, and Classic Portfolio Tree are disabled by default in 26.2 and are scheduled for permanent removal in version 27.0. Organizations still relying on these capabilities should identify transition plans before upgrading. 

外賣 

Enterprise planning becomes more useful when leaders and teams can connect strategy, release scope, progress, ownership, and execution without assembling the picture manually. 

Digital.ai Agility 26.2 advances that goal by providing richer release context directly in planning workflows, extending release and OKR information into analytics, and improving the reliability of synchronization across the tools enterprises already use. 

The direction is important: planning should not produce a static picture that immediately begins to age. It should remain connected to execution so teams can see change, understand its impact, and adapt while there is still time to act. 

Digital.ai Agility helps organizations turn enterprise planning into that continuous feedback loop—connecting strategic intent with the reality of work as it moves toward delivery.