dalescott wrote:Hi @Nik, this is only a first impression but it feels IMHO that the daily Notes fields are a step backwards, in particular because they seem too small to be useful for viewing or editing the note...
You can actually see the entire comment on mouse hover over due to a title attribute that is set on these controls. Example below.
dalescott wrote:... but also because it takes more mouse clicks now to enter a weekly timesheet.
IMHO, your situation may be quite unique if comments are the same for the entire week.
I can return the Week note
field, as it is relatively easy to do, but I was trying to address your own concerns earlier in this thread about confusing behavior of this control. New design completely eliminates this problem. It also allows to edit a comment right there, without clicking on Edit, going to time_edit.php, then Day View, then switching back to Week View. Furthermore, you can edit multiple comments for many records in the week (and keep them different) in one click. How is this a step backwards?
No design is good for everybody, and perhaps the best way to address some of the issues is by making stuff configurable. For example.
- Whether or not to display a week comment for new entry.
- Whether or not to display individual comment fields.
- Whether or not to display the list on the bottom.
Here are a couple of notes from another user I was trying to address (both already implemented).
1. keep the projects that are active populated from week to week - i.e. once you shift from one week to the next, you have to re-populate each active project to build up your “project set”. it would be nice if this was just always there. for extra credit, just populate all projects that each employee is active on at all times, then you would never need to populate projects in the week view, each employee just has their own “project set” up all the time.
2. if there were a way to add notes in the week view to each entry, that would be really awesome for us, as this is where we keep track of individual tasks etc.. I realize this may be a bit more difficult, but imagine a little box that you could type in right below the hours. Here is a screen shot sketch of the idea.
dalescott wrote:I'm currently using my production site for testing. Will there be any problems if I revert back to a previous version after testing? I recall having to manually run the end of dbinstall.php when Weekview was first introduced. There was a recent commit to dbinstall.php but it didn't seem to change the schema. Never hurts to double-check though.
There were no changes in the database, so a rollback back is realistic. You can also test at https://timetracker.anuko.com
as it runs the latest code.