Product teams rely on various timeframes to plan, prioritize, and align their roadmaps. Previously, Craft.io offered for these purposes only two system fields - quarters and sprints - configured separately on each workspace. However, in many cases, teams required additional time cadences, such as program increments (PIs). Furthermore, companies often preferred defining timeframes at the portfolio level for consistent application across all workspaces, as such timeframes are frequently standardized at the leadership level.

This new release introduces a powerful and flexible custom field: Timeframe. We've addressed key user needs and added several significant enhancements. In essence, the Timeframe field is a multi-select custom field that can be added without limitation and can be also configured from the portfolio level. As a result, your product team can build new types of time cadences and associate them with all relevant work items and OKRs. This provides greater clarity on the duration and scope of initiatives across multiple planning cycles. Moreover, to allow full flexibility, the Timeframe field is a custom field, so you can build several different Timeframe fields for various purposes in your organization.

From now on, users can add custom Timeframe fields and use them in their views for grouping, filtering, or sorting. Additionally, it is compatible with the Date Alignment automation rule, allowing teams to automatically sync start and end dates based on the selected timeframes. Further, integration with Jira and Azure DevOps (ADO) ensures that Timeframe values are preserved and managed across systems, enabling consistent planning and tracking regardless of platform. Also, the Timeframe field is fully supported by our public API.

The Timeframe field is multi-select based, enabling a single item to be linked with several timeframes simultaneously. This is especially valuable when a feature, epic, or objective is associated with more than one planning cycle, such as a quarter or a sprint.

For instance, an initiative might be planned for several time cadences, depending on how your teams structure their planning cycles. Rather than forcing teams to choose a single dimension, this field allows users to apply both, offering a more accurate and flexible view of work.

The Timeframe field can be configured globally as a portfolio field or individually as a custom field per workspace, depending on the level of coordination required. Portfolio timeframe fields also support initiatives and portfolio OKRs. This dual capability supports both centralized governance and local flexibility. For portfolio-level planning, defining Timeframes such as “H2 Roadmap” or “Global Launch Phase 1", allows all connected workspaces to reference and use the same planning cycles. This alignment supports enterprise-wide transparency, especially in organizations operating with multiple workspaces under a single strategic portfolio.

However, teams preferring different attributes as workspace-specific timeframes can also use an additional Timeframe custom field, maintaining planning independence while still benefiting from the portfolio field structure.

Capacity Planning is now enhanced with full support for the Timeframe field, enabling teams to allocate and manage resources in alignment with the customized Timeframe fields. Users can choose the Timeframe fields to group-by on the Capacity Planning view and start basing the planning on them.

Likewise, as a result of the multi-select functionality, planning based on timeframe fields allows for associating work items over several cadences to reflect ongoing processes.

To ensure that you can use the Timeframe field for Capacity Planning, verify on the Timeframe properties screen that the dedicated toggle that enables the Timeframe field for Capacity Planning is on.

The icing on the cake: From now on, you can add the Capacity Planning View to your Portfolio. Following the creation of the timeframe field at the portfolio level, it is now possible to base a capacity planning view on it.

Therefore, portfolio leaders are now able to:

Eventually, portfolio-level users can also drill down into how capacity is distributed across the portfolios' associated workspaces, using the shared Timeframe definitions to ensure alignment across all levels of planning.