feat: 🎸 added higher resoulution options in the dateTime Filter

[Bhoomaahamso]

Title: "feat: Add second, minute & hour resolution options to relative date Filter action"

Summary

This PR enables support for smaller time units — Seconds, Minutes, and Hours — in the Relative Date filter used in workflows, rather than being limited to days only.

---

What Changed

This PR extends the relative date filter to include support for the following units:

✔️ SECOND
✔️ MINUTE
✔️ HOUR
✔️ (Existing: DAY, WEEK, MONTH, etc.)

Changes include:

• Adding SECOND, MINUTE, and HOUR options to the internal relative date unit enum/constant.
• Updating utility functions and parsers to correctly interpret and evaluate these new units.
• Enhancing existing tests and adding new tests to cover second, minute, and hour relative filters.

---

Testing

New and updated tests include:

• Unit tests for serialization of relative filter values including seconds, minutes, and hours.
• Workflow filter evaluation tests that verify minute/hour resolution behaves correctly.

Tests are included in the changeset.

---

Backward Compatibility

This change is fully backward compatible:

• All existing relative date filters using days or larger units behave exactly as before.
• Adding finer units does not alter existing stored data or workflow definitions.

---

Issue Reference

Fixes: #15525

[greptile-apps]

Your free trial has ended. If you'd like to continue receiving code reviews, you can add a payment method here.

[cubic-dev-ai]

No issues found across 11 files

[github-actions]

🚀 Preview Environment Ready!

Your preview environment is available at: http://bore.pub:44292

This environment will automatically shut down when the PR is closed or after 5 hours.

[guillim]

Is that something we want to add in the UI @Bonapara ? (the more options, the messier it can feel)
IMO it would be a good addition but just double checking what the product wants

[Bonapara]

I think it is a great addition but:

• Seconds should be the last option, not the first
• It should only be available for datetime

[guillim]

Great. I will let you implement those feedback @Bhoomaahamso . But that's a great addition to our CRM. thanks for the work

I think it is a great addition but:

• Seconds should be the last option, not the first
• It should only be available for datetime

[Bhoomaahamso]

Hi @Bonapara @guillim ,
For point 1, do you mean the order should be ['Minute', 'Hour', 'Day', 'Week', 'Month', 'Year', 'Second'] or ['Day', 'Week', 'Month', 'Year', 'Hour', 'Minute', 'Second']? I would appreciate if you could specify it.

For point 2, both DateTimePicker and DatePicker use options from RELATIVE_DATE_UNITS_SELECT_OPTIONS. Do you think I should create a new variable specifically for DateTimePicker and use it within RelativeDatePickerHeader based on a condition?

[guillim]

Hi @Bonapara @guillim , For point 1, do you mean the order should be ['Minute', 'Hour', 'Day', 'Week', 'Month', 'Year', 'Second'] or ['Day', 'Week', 'Month', 'Year', 'Hour', 'Minute', 'Second']? I would appreciate if you could specify it.

-> ['Day', 'Week', 'Month', 'Year', 'Hour', 'Minute', 'Second']

For point 2, both DateTimePicker and DatePicker use options from RELATIVE_DATE_UNITS_SELECT_OPTIONS. Do you think I should create a new variable specifically for DateTimePicker and use it within RelativeDatePickerHeader based on a condition?

-> yes please. in the same file will be fine.
sometihng like

export const RELATIVE_DATETIME_UNITS_SELECT_OPTIONS: RelativeDateUnitOption[] = [
   ...RELATIVE_DATE_UNITS_SELECT_OPTIONS,
  { value: 'HOUR', label: 'Hour' },
  { value: 'MINUTE', label: 'Minute' },
  { value: 'SECOND', label: 'Second' },
];

[Bhoomaahamso]

Hi @Bonapara @guillim. I’ve implemented the feedback, could you please review the PR?

[guillim]

LGTM

CleanShot.2025-12-17.at.14.37.57.mp4

[twenty-eng-sync]

Hey @guillim! After you've done the QA of your Pull Request, you can mark it as done here. Thank you!