Description -
Currently, Workfront utilizes the time zone on the user's computer to determine the times and dates for tasks versus the setup time zone within Workfront for the user. It also ignores the time zone schedule of the project. We are finding issues with this in a few locations within Workfront. For example, in the Time Off section, if the user's setup time zone within Workfront is not set to the same time zone as their computer, it will select 2 days when trying to select 1. Another example, if a user is located on the West coast and their computer is set to PST, but their Workfront time zone is set to CST, it will override the CST and use the computer's time zone. This is especially difficult for Planners that are setting up due dates and times for tasks within a project. We'd like Workfront to stop referencing the "computer" time of users and set all users to CST, regardless of where are they are located in the world.
Configuring user accounts with their actual time zone doesn't work, either. Our default schedule in Workfront is set to CST so when a Planner goes to schedule tasks and their time zone is set to something other than CST, the planner hours fall over different days, messing up the Workload Balancer.
Why is this feature important to you -
Times are showing up different for users depending on their physical time zone which is causing a great deal of confusion across our global company.
How would you like the feature to work -
The system should display times in the time zone schedule assigned to the project, or, Workfront should not reference the time zone of the user's computer and refer only to the time zone configured in their user account. Also, time entered in PTO should be entered as CST so that the PTO doesn't incorrectly affect the workload balancer or planner.
Current Behaviour - Our default system schedule and projects schedules is CST. If a person in another time zone enters a full day of PTO for a single day, it places the time off over two days in time off calendar and adversely affects the workload balancer.
All of this refers to original support ticket E-001557318, which was rejected by Adobe Workfront Support, that it is "not feasible within the current scope of our work".
