Currently once a time entry and expense has been approved, the user could not undo the approval, deletion is locked, status is locked.
There are cases where the project manager might make mistake and need to undo the approval. Please allow this scenario.
Once the time entry being approved, it can't be cancelled and sit in read-only state as actuals.
Sometimes there is a need to adjust the approved timesheets and actuals and this is not possible right now.
Current workaround is to open a support ticket and they will modify or delete the record using SQL script.
Allow editing of Actuals to correct / updated project codes, hours, customer or billings
Time entries calendar - First day of week is Monday in our company and we should be able to see Monday first and Sunday the last, not Sunday first and Saturday the last. This will confuse our users and also the Date format we use is 04/07/2018 (for example, July 4, 2018) so the fact we are not able to see this format is confusing as well. Please enable this in the system - I am sure users around the world are facing the same problem.
Allow us to set Business Closures based on countries so that an individual country can have a country specific Business Closure. Then allow to set a user to a defined country so that work hours use a correct business closure.
The need for country specific operations and settings has become even more critical with PSA and Field Service. As multinational companies have to take these into account, we should be able to offer them the OOTB possibility to choose country specific Business Closures.
I would like to see how to define tasks efforts as minutes, as we have sometimes tasks of 30 minutes or 3.5 hours for example. Also, duration can be divisions of a day for small tasks. For example, 4 tasks of 1h each end up to be 4 days in duration.
When trying to change those values for float number, it defaults to "one".
That functionality is possible in Microsoft Project but not taken into account when importing to PSA.
It seems possible since the effort and duration are float values is a float. Only the interface, business logic and calculation engine is limiting the functionality.
In a project, we should have the option to mark the task to be completed as some cases organisation does not want to track the timesheet due to the nature of their business model.
This is a typical MS project example.
When the language is changed into English, it is not translated into English.
- erroneous display in Navigation bar -
From " Resource Requests " To " リソース要求 "
From " Resource Requirements " To " リソース要件 "
Probably, we think the translation is forgotten in Development.
Could we have you consider improving this problem ?
Given that everything else in CRM is customizable it is very hard to argue with customers that when they add additional values to the Time Registration Type (msdyn_type) these new options aren't available when registering time throught the time registration page. Would be great to see that the additional values added to the option set is also available to use
People needs to recover time entries approved because it´s common that they change their days of vacations, and now it is not possible.
All customers think it is imperative for the right use of the app.
There is an error when we create the time entry from time entries section.
The start date field has the start hour included. When we create the time entry from time entries section, the hour is established in 1 PM and PSA creates 2 unavailabilities because the first starts at 1 PM and not at the time it should starts.
In contrast, if I create the time entry from a standard CRM form and if I show the hour field, it takes the correct hour (is the start hour of the resource calendar).
All the customers of Project Service Automation need that the start hour of the unavailability are the start hour of the resource calendar, because if not, there will be unavailabilities on incorrect days and theys will create bookings on incorrect days.