Please let Smartsheet work with time

the ability to track time/duration in a HH:MM:SS format would be so handy for a lot of media organisations for things like slate management, production management, scheduling etc.

@Genevieve P. I apologize, I had a new member enter my family and lost track of everything.

So, this seems to link to the documentation that the SmartSheets system currently seems to save the timesheet's timezone as whatever user last saved the sheet (which is what I found in the SmartSheet documentation). So, let me give you a very realistic hypothetical for my team:

----------------------

We have an event in Vietnam in 2 months, for which we're planning to run backend setup and operations. Our PM's are in Australia, Egypt, and Texas and all 3 are working to coordinate this project with support teams in each region.

For 4 timeslots each day, we will be running 4 rooms of labs per timeslot, for each day. This equals 16 separate setup, run, teardown tasks per day. Our operations teams are in Australia, India, Austria, Portugal, Iowa, and Utah - round the clock, and each team has work to do, and sometimes they need to cover for one another.

In our planning, we have setup, run, and teardown tasks that will be planned according to Vietnam's timezone due to the event, but each PM is coordinating a separate stream of work that applies to when setup needs to run for each room and the organizer/speaker in that room, and assigning it to the operation team that has that task land during their business-day, and how early thethe speaker/organizer(s) need to run through prep on their environment(s) based on what they are doing, and that work needs to be coordinated across.

Onsite at the event we will have a single coordinator PM who will then make sure the tasks that need execution are executed on that specific time and will be running early/late calls with each operations team to ensure setup/teardown are completed on-time according to the needs.

So, that's the use-case.

----------------------

What do I need in order to realistically use SmartSheets for this?

1. I need to be able to force a Gantt chart to always use the Timezone of the event for the specifc calculations of time - else the teams in each timezone will not know when their task begins and ends - and we need somewhere we can see that to confirm that all tasks are in Event-localtime, and are thus showing up correctly for the Ops teams in their local time.
2. I need to be able to make sure each Operations team in our FTS setup can see what time each task occurs in their specific timezone as well as localtime.
3. I then need to be able to provide the full Critical path to the event team for the site to ensure that they also know what we need, when, and where, in order to make the event successful.

At this point in time, I can't use Smartsheet for that, so we're back to Google Spreadsheets again.

Does this help explain what I'm requesting?

Hi, @Joe Goetschel,

I took a look at Bridge - but it's far beyond what I need. According to the SmartSheet documentation I read, the Smartsheet document itself adjusts to match the Timezone of the last EDITOR of the sheet. Which means our PM's in APAC, EMEA, and NA will constantly nuke the intended timezone. That's not going to work.

All I really need is the ability to set a Timezone, with a variable or function that lets me adjust the time to the user's local timezone. And I can't do that currently - I've tested the existing system with my teammates in Australia, India, Europe, US East/Central/West, and Canada, and the systems doesn't handle it because of the current limitations.

Thus why I'm back to spreadsheets again instead of SmartSheets. :(

Not sure if this has been added to this field. I utilize smartsheet as an ATS since I am the Senior Recruiter for my company. I input into my sheet the date that I am talking with my candidates, but it would be nice if I could build an automation that would take a date and time from a row, then create a calendar event for Outlook and include attachments from that same row. Would cut down on a decent amount of time for me and prevent from having to jump back and forth between applications.

Another use case is for support ticket tracking. We track how long a ticket is open along with its priority to determine when to escalate the ticket. We have SLAs ( service level agreements) in place for how quickly a ticket needs to be responded to as well as different levels of escalations and communication times ( it would be great to automate these).

Of course, we would want to do reporting on durations in hours, minutes, seconds (maybe not).

We are looking to replace our current ticketing system, but cannot even consider using SS without have the options to create timestamp columns.

Thanks

Would be great to have standardization across data!

@Paul Newcome Thanks Paul. Creative idea - this could work. Thanks for the idea.