I have a use case where I have a custom field that is a date.
I am using it to look into current and near future.
When I filiter the view, it would be good to get current month filter added to this field from the list of options.
Hi everyone,
Date filters in project views only support fixed ranges (“is between 08/01/26 – 08/31/26”). There’s no way to set a relative period, like “current month”, that updates automatically.
The problem: any saved view meant to show “this month” or “this week” becomes outdated as soon as the period changes. You have to open each view and edit the dates by hand, every week or month. With several views, it turns into a recurring chore, and it’s easy to miss one and end up looking at outdated data.
Some use cases:
- Finances: “Paid this month”, “Pending this month”, monthly overview of bills
- Client work / agencies: deliverables and tasks completed this month for monthly reports
- Content calendars: posts scheduled for this week or this month
- Team management: tasks completed last month for retrospectives and reviews
- Sales / operations: follow-ups due this week, next month’s planning
The quick filters already include “Due this week” and “Due next week”, so relative dates exist. They just don’t cover months and aren’t available as conditions in “All filters”.
Suggestion: add relative options to all date filters (Due date, Start date, Completion date and custom date fields):
- Last week / This week / Next week
- Last month / This month / Next month
- Ideally also: Last X days / Next X days, and This quarter / This year
These should work as conditions alongside “is”, “is between”, etc., so they can be combined with other filters and saved in views.
Why it matters: most teams run in weekly or monthly cycles. Relative date filters would keep saved views always up to date with zero manual maintenance.
Thanks!
*(Screenshot attached showing the current date filter options.)
*
Hi @Jonathan_Gustavo_Pin, I’ve merged your post with a similar request. Be sure to scroll to the top to vote!
Nice!
Thanks, @Jeremy_Long !


