Update WF to pull timezone for all users from global settings. Offshore vs. Onshore

[#1]

Hello,

We are a large company with offshore and onshore employees. Our offshore team has the same dashboards as onshore and work on the same timelines and time zones as our onshore. They are required to change their work machines to match US Time Zone because WF won't pull through the WF timezone for dashboard reporting. I submitted a support request 00199948 to find this work around. We shouldn't have to tell someone in India to change there personal machine to US time when WF has a global setting for timezone. It seems like a defect really. Can you please view my support request as it has all the images from our testing and concern. This would help many companies not just AT&T. Thank you!

[#2]

This also affects how team members see what dates something is scheduled for AND when someone's time off is.

Examples:

1. Mountain time zone project manager assigns a task to London team member for August 30th but the London team member sees it as assigned to August 30th through August 31st because of the start and end time of the task. Start time is 9:00 am MT - 5:00 pm MT, but it adds 7 hours to the start and time so it shows as "Aug 30th 4:00 pm - Aug 31st 2:00 am"
2. London team member has time off for Friday, Aug. 14th but a project manager in Mountain time zone sees it as Aug 13th - Aug 14th because of the same task time adjustment workfront implements based on the team member's computer timezone.

[#3]

This is a huge issue for our company. We have not had our offshore associates change their machine time as it would impact other applications they use. We have a field in our project timelines to covert US time to the Off-shore time and then we have to go line by line to update the off-shore associate's due date and time so it aligns with the actual due date. This opens us to a lot of risk of not capturing all updates (and missing deadlines), is wildly inefficient and time consuming and impacts the project flow as when you adjust a due date time it automatically changes your task constraint. I wish I could upvote this one 10 times

[#4]

Copying Tara's comment This is a huge issue for our company. We have not had our offshore associates change their machine time as it would impact other applications they use. We have a field in our project timelines to covert US time to the Off-shore time and then we have to go line by line to update the off-shore associate's due date and time so it aligns with the actual due date. This opens us to a lot of risk of not capturing all updates (and missing deadlines), is wildly inefficient and time consuming and impacts the project flow as when you adjust a due date time it automatically changes your task constraint. I wish I could upvote this one 10 times

and adding on....... Leaders of the offshore teams and the onshore teams continue to question the structure, and deliverable due date reports with a growing lack of confidence in system accuracy which has a negative impact on adoption. I too would upvote this 10x as well if possible!

[#5]

Agreed!! The due dates can look weird, especially when there is a weekend or holiday involved.

[#6]

This is something we have an issue with as well for a global company. The Project Owner may be in EMEA but the tasks assigned to the team in the EST in US and the dates are all off.

I suggest there be an option of viewing the project schedule in a certain timezone. We set the timezone on the project details but when the PM in EMEA looks at it, it seems off because 5pm EST is bumping it to the next day for them. This is especially hard when dealing with Hong Kong vs EST US as it's a whole day a head.