Die neue Version Februar 2015 (1.33) ist rückwärtskompatibel bis zur Version März 2013 (1.10). Sie können alle Versionen bis dahin gleichzeitig in einem Account verwenden.
Changes in the New Version
Error Diagnostics and Resetting Configuration
We have extended the options dialog by two new features. You will find them in the "Log Options" section:
- "Send log files tosupport@timecockpit.com"
When something goes wrong in time cockpit we often ask you for the log files to diagnose the problem. By now you had to open the folder with the log files, add all log files to a zip archive and send an email to us with the zip archive attached. Now, this is all down for you automatically. The created email will be opened in your default email client and you will just have to hit "Send". - "Delete local data and reset time cockpit"
When something really goes wrong and you want to throw away all your local data and reload everything from the server you had to manually delete some files and restart time cockpit to be able to reconfigure time cockpit. "Delete local data and reset time cockpit" will do this for you. It deletes your local database and the configuration file with your account information and then it will restart time cockpit. Time cockpit will ask you again for all of your account information (user name, password and signal data password). Then it will fetch all data from the server. Do not use this feature if you are not sure if there are unsynced changes on your client.
There are scenarios where time cockpit may not be able to start. For this case we have added two new shortcuts to the program files folder: %programfiles%/software architects/time cockpit/time cockpit 2010. They do the same like the buttons in the options dialog but you do not need to start time cockpit to run them.
Timesheet Template Improvements
We have added some improvements for time sheet templates in the calendar. Only templates that are generated by a query or a script are affected by this changes. For templates in the "My time sheet templates" area nothing has changed. For scripts or query templates the following changes have been made:
- Performance: When selecting a template and dragging a new time sheet entry with the mouse, there was a delay of multiple seconds in some accounts depending on the customizations that have been made to the time sheet entity and form. In the new version you should immediately see the dragged time sheet entry.
- Selection in Silverlight: There was a bug in the Silverlight client that did not always update the time sheet templates when a new time range was selected by clicking on a day, time sheet entry or signal.
Additionally, we have improved the performance of the docking panels in the calendar. If you have experienced performance problems in the time tracking calendar since docking has been introduced in October 2014, the new version may solve this problem.
Signal Lanes
In the signal lanes area it is not possible to add new time sheet entries by dragging them with the mouse. We have added a light background color to this area to make it clearer that this area is reserved for signals. Especially when there were no point signals like sent emails, it was difficult to tell where the signal area ended and the area for time sheet entries started.
Refresh Calendar after Sync
The time sheet calendar is not automatically refreshed when synchronization with the server has finished. So you will immediately get all changes from the server without having to click "Refresh" in the ribbon.
Signal Tracker for TFS 2013
We have added support for tracking work item changes and check-ins for TFS 2013 in our signal trackers.
HTML5 Client
For the HTML5 Client we have spent most of our time with grouping of lists. Left above the list there is a new icon that contains all the grouping information for the list. You can add new group rows, remove existing ones, change the sort order of groups, or expand and collapse the groups at every level. There will come more ways to manage groups that will be faster to use with mouse and keyboard but we want as much functionality as possible to be available for touch devices too.
comments powered by 