Make it possible to hide timezone in Automations and comments where date fields are used as variables
planned
Katie Subra
We have routine automations that we program into some of our lists and these are informational, including a date field, but the timezone of the ClickUp user is irrelevant. Our team members are all remote and the information we are communicating via these notifications is about someone other than a ClickUp user.
Log In
Zach - ClickUp
Merged in a post:
When using a Date as variable in automations, provide an option to include or exclude Time Zone
Matthew Ross
When I use a ClickUp automation to add the Due Date to a title, it always includes the time zone as well. Please add an ability to choose whether the Time Zone appears or not.
Zach - ClickUp
Merged in a post:
Automated time zone update
T
Tara Pagano
Description:
Since a recent updates to email Automations, the Start Date & Due Date variable in automated emails now includes the time zone (ie. Oct 3 2025, 5:00PM (America/Los_Angeles)) in addition to the date and time. Previously, the Due Date displayed only the date and time, which was much cleaner, plus this indicates that their class might be in LA.
This is causing confusion, as the time zone is unnecessary for our use case and makes the emails look cluttered.
P
Projects COE
We use email Automations for approval and signing workflows. Date Custom Fields show correctly in IST inside ClickUp, but the email shows them in UTC, which puts every approval record 5.5 hours off for our India-based stakeholders. We need (1) a timezone setting on email Automations, or for them to use the Workspace/creator timezone, and (2) a date format option like DD-MMM-YYYY hh:mm AM/PM. Formula fields can't be used as variables, so there's no clean workaround right now.
Zach - ClickUp
Merged in a post:
ClickBot Time Zone In Automated Emails
T
Tosha Brown
ClickBot now adds in the bot's time zone into all automated emails (America_New York). This can be very confusing for clients in different time zones receiving an email about an event happening in their time zone. Right now, the automation reads "Your even is scheduled to begin on Oct 7 2025 (America/New_York) at 1:00 PM" The time frame is always for the client's time zone, but having the (America/New_York) is entirely unnecessary and makes it obvious that the email is coming from a bot. The automation was at least somewhat personal before this new feature was added. Please remove.
Zach - ClickUp
Merged in a post:
Adjust Date format of automation created lists
Kolton White
I have an automation to create a new meeting list every week and set the first half of the title to be the date the automation triggers (every Monday).
But the date formatting when this triggers is way too long for a list name, it includes the day of the week, the full written date/month/year, as well as the time and timezone.
Can you fix to allow to allow for a shorter formatting?
Zach - ClickUp
The date string automations output is way too verbose for list names, day of week, full written date, time, timezone all jammed together. Totally reasonable to want more control over that format.
Merging your post into an existing request tracking this same problem so your vote counts toward it. The good news is date formatting in automations is already on the roadmap 🙌
Zach - ClickUp
Merged in a post:
Option to remove timezone from automation naming
Rob Davies
I have an automation that creates a task and adds the 'Date Updated' to the task title, but it writes the date out in full every time e.g. "Feb 26 2026, 16:00 (Europe/London)"
I really don't need to see the "Europe/London" part. Is there a way I can get the date in DD/MM/YY (or other) formats? At the very least shorten Europe/London to just 'UTC'
Zach - ClickUp
Good news — this is already planned. We're going to give you control over whether the timezone appears when date variables are used. Merging your post into the main tracking thread ⚡
R
Rabbi Leser
Yes Please!!
Zach - ClickUp
updated the status to
planned
Hey everyone, we're looking into this for a solution. Stay tuned.
Load More
→