Currently, it's only possible to set a project alert against the total hours or % of the project, but it would be more useful if I could set an alert against a task.

My use case:
Our team often overruns heavily on one task, but will spend less time than estimated on another. When I set a project alert based on hours/% spent against the entire project I don't catch the task that is overrunning until it has overrun so much that it's using up almost all estimated project hours (across all tasks).

This means that after the overrunning task is completed we don't have any estimated time left for the remaining tasks and will definitely be overspending on the project.

To give a concrete example, consider this scenario:

Task A - estimated 5h, actual 3h
Task B - estimated 15h, actual 20h
Task C - estimated 5h, not started

Total estimated: 25h
Total actuals: 23h

If I have set an alert for 90% of hours spent, at this point I would receive a project alert notifying me that we have gone over that threshold and have 2 estimated hours left, but still at least 5 hours to complete the project - ergo, we will run over by 3h and there's nothing I can do at that point.

What I would rather know is when we are getting close to the total estimated hours of a task, instead of the entire project. In that case I would catch the Task B risk at, say, 75% of the task's estimated hours, not at 133%.

It's still useful to have the alert option for the entire project, but it doesn't cover risk management very well.

It would be great if you were to send out a monthly newsletter to Dovico admins where you highlight:

- new releases
- new features
- tips & tricks
- best practice examples
- featured suggestions with a prompt to vote on suggestions

Either all of these or a selection each month would be great.

For example I didn't know that I could vote on feedback from other users, but I'm sure this would be great for Dovico in terms of roadmapping and prioritizing your next features.

It's also a nice touch because for us as admin users it feels like we're all working together to make the product better. I think the Microsoft Teams product team does a stellar job at that and users have been happier with Teams than with other MS products when you look at feedback sentiments across the web.

Entered on behalf of a client.

Dear support team,

As a suggestion for a future update of the DOVICO timesheet (desktop/website application):

When I am in the ‘Time Calendar section’ and I need to add/update entries there, then there is a box at the bottom for doing that. The first item in that box is called ‘* Project’. This opens a drop-down menu on the right with ALL projects from present and past. That is not efficient, especially if those past projects have been listed as ‘finished’ (end-date is also already in the past) and ‘flag for archive’. They are not relevant for entry of new data in this Calendar section anymore. The result of the current situation is that the ‘*Project’-list becomes very long and it takes extra effort (the lay-out of the drop-down is also not very appealing) to find the right project.

My improvement suggestion is:

The project-list in the drop-down menu ONLY shows current projects, meaning projects which are ‘active’ or ‘estimate’ and within the start-date and end-date boundaries. All past projects/finished projects should not appear anymore.
The drop-down menu has some alternate colouring, so you see more quickly which project you need. Now everything is uniform and compressed.

I hope you can take this into consideration.

Best regards

Roy

Pass phrases are more secure than passwords.
You allow uses to create passwords like "This is my password1234" but when this user tries to login, it will not allow it citing incorrect username/password. Changing the password to a shorter password without spaces solves the issue but reduces the complexity of the password, making it less secure. The password creation screen should either reject passwords which won't allow users to login, or the login should accept valid passwords.

I believe pass phrases should be accepted as logins as they're easier to remember and much harder to crack/hack due to the increased entropy.