Add Start and End Quarter Columns for All Date-Range Record Types

What is the challenge?

Aha! only provides a “Quarter” column based on the end date for certain record types (e.g., Initiatives, Epics, and Features). There is no equivalent quarter value based on the start date, and other record types with date ranges do not consistently expose quarter-based fields at all. Because of this, our nearly 200 product managers are manually adding quarter information to records using a mix of custom tag fields and the standard tags field. This creates inconsistency and extra work, and makes it difficult to use time-based quarters reliably in reports.

What is the impact?

The lack of standardized quarter fields tied to both start and end dates makes it hard to build consistent, reusable reports across products and teams. Work often spans multiple quarters, and we need to see and filter that work by both start quarter and end quarter in a reliable way. Today, quarter information is scattered across various custom and tag-based implementations, which leads to:

• Time-consuming manual data entry and ongoing maintenance for hundreds of users

• Inconsistent quarter definitions and values across teams

• Difficulty creating standard portfolio-level reports and dashboards that rely on time buckets

• Increased risk of errors and misalignment when planning and communicating timelines

Describe your idea.

Add standard quarter-based columns for all record types that have a date range field, derived directly from the record’s start and end dates that also factor in the account's fiscal year settings.
Specifically:

• For each applicable record type (e.g., Initiative, Epic, Feature, and any others with start/end date fields), provide:

  • {Record Type} Start Quarter – calculated from the start date

  • {Record Type} End Quarter – calculated from the end date

These fields should behave like the existing “Quarter” column (currently based on end date for some record types), so they can be:

• Used as columns in reports and roadmaps

• Used as filters and group-by fields

• Available consistently across relevant record types

This would eliminate the need for manual quarter tagging, standardize how quarters are represented in Aha!, and make it much easier to build consistent, cross-team reports showing work that starts in, ends in, or spans specific quarters.