Support Configurable Calendar Systems (Jalali / Islamic / Gregorian)

[aliroayaei]

Feature Request: Configurable Calendar System Support (Jalali / Islamic / Gregorian)

Problem

Currently, Twenty appears to couple:

• UI language
• locale
• date formatting
• calendar system

This makes it difficult or impossible to support alternative calendar systems such as:

• Jalali (Persian/Shamsi)
• Islamic/Hijri
• Other region-specific calendars

At the moment, even if localization is added, the application still renders dates using the Gregorian calendar in many places.

This affects the entire UI experience, including:

• Record lists
• Record detail sidebars
• Activity timelines
• Filters
• Date fields
• Built-in fields such as createdAt and updatedAt
• Navigation and date-based UI components
• Relative dates

---

Proposed Solution

Introduce a configurable calendar system setting, separated from language/locale preferences.

Example:

{
  language: 'fa-IR',
  calendarSystem: 'jalali'
}

Possible values:

type CalendarSystem =
  | 'gregorian'
  | 'jalali'
  | 'islamic'

This setting could be configured:

• per user
• or per workspace

---

Important Clarification

This feature only affects date presentation/display.

It does not require any change to:

• database storage
• backend date handling
• API formats
• timezone handling

Dates can continue to be stored internally using ISO/Gregorian formats.

---

Why This Matters

Many users and organizations use non-Gregorian calendars in daily business workflows.

Examples:

• Persian-speaking regions use Jalali calendars extensively
• Some Arabic regions use Islamic calendars
• Enterprises may require localized date systems for compliance or usability

Supporting configurable calendar systems would significantly improve:

• internationalization
• enterprise localization
• regional UX adoption

---

Technical Suggestion

A centralized date formatting layer could make this manageable and extensible.

Potential approaches:

• Intl.DateTimeFormat with unicode calendar extensions
• adapter abstraction over existing date libraries (date-fns, dayjs, luxon, etc.)

Example:

new Intl.DateTimeFormat(
  'fa-IR-u-ca-persian'
)

or:

new Intl.DateTimeFormat(
  'ar-SA-u-ca-islamic'
)

This could automatically affect:

• tables
• filters
• sidebars
• activities
• date fields
• relative dates

without requiring per-component customization.

---

Benefits

• Better internationalization support
• More flexible localization architecture
• Enterprise-friendly regional customization
• No database/schema changes required
• Extensible for future calendar systems
• Improves adoption in non-Gregorian regions

---

Additional Note

This request is intentionally broader than “Jalali date support”.

The goal is to decouple:

• language
• locale
• calendar system

and make date rendering configurable in a scalable and future-proof way.