Named Custom Date Ranges for Reporting

Today, users can choose from standard absolute and relative date ranges (Last 7 Days, Month to Date, custom start/end dates, etc.) within each widget's or the UI's Time period selector. This is powerful but introduces friction for organizations whose financial or operational periods don't align cleanly with calendar months and quarters.

Specifically, we'd like the ability to define named custom date ranges (e.g., "Business Quarter", "Fiscal Q1 2026", "Black Friday Peak", "Migration Phase 1") and then reuse those labels anywhere a date range is selectable.

Proposed Capability
Admin-Defined Named Date Ranges

• In a central settings area (e.g., under account or organization settings), allow admins to:
  • Create a new date range
  • Assign a name/label (e.g., "Business Quarter", "Fiscal Q1 2026", "Black Friday Peak", "Migration Phase 1")
  • Define the start and end dates (absolute) or a formula/relative logic, if supported (e.g., "first Monday of the months + 89 days")
• Optionally, tag these as:
  • Reusable across all dashboards/reports
  • Scoped to certain business mappings or teams (if applicable)

Use in Dashboards & Reports

• Anywhere Cloudability currently offers a date picker or Time period field for widgets, reports, and scheduled reports, include a "Named Ranges" section that lists these custom ranges by their label.
• User can simply choose "Business Quarter" instead of manually selecting the same start/end dates each time.
• When copying widgets, cloning dashboards, or scheduling reports, the named date range should be preserved by reference so that updates to the definition propagate automatically.

Support for Fiscal / Non-Standard Calendars

• Many organizations operate on fiscal calendars that differ from calendar quarters
• Named ranges should support:
  • Custom fiscal quarters and years (e.g., Fiscal Year starting August)
  • Irregular periods that align to internal cycles (e.g., product releases, migration waves)

Behavior Over Time (Desired)

• Support a "rolling" flag so a named range can represent a rolling period (e.g., "Rolling Business Quarter" that always shows the last 90 days)
• Allow comparison between two named ranges (e.g., "Business Quarter" vs. "Prior Business Quarter") in components that support comparison

This solves several issues, including:
1) Reduced manual effort and error risk
2) Consistency across communications, reports, dashboards, and stakeholders
3) Improved scheduling and automation