Record start/end time, number, name or other identifying information on a separate timeline

The Cisco system (and others, I'm guessing) have web portals (and hopefully APIs) for individual users to access their call records from a central place, but those would require authentication to a central system.

I was able to dial my attached phone from within Outlook and from a company web phone directory, a la Skype, though, so there is some sort of mechanism to control the physical phone itself from the desktop. Hopefully this control would also include the ability to read that phone's call log, rather than have to request permission against a centralized system where other user's data would be stored, too.

Right now, the Statistics reports doesn't include Autotags - you have to copy autotags to regular tags in order to get them to show in Statistics. This is counterintuitive and not user-friendly: the whole purpose of autotags is to automatically tag certain activities, and not to include them in Statistics reports means those reports are inaccurate.

I have ALL my activities autotagged, and then monitor a statistics report to see how much time I've actually spend working as opposed to slacking off, surfing the web, etc. If I haven't put in enough time then I can decide to stay later. But this means I have to switch over to Day view and update the tags through out the day. Real PITA!

Please include Autotags in the statistics reports!! I'm piloting MaincTime for my company, but without this improvement I will not be able to recommend it.

Currently, the pomodoro timer opens a window that steals the focus from the current application.
While this might be good to signal the break, it can also affect current work. Especially when working with graphic or engineering applications where a single command might take several minutes (e.g. using a polygon mask in a graphics program), this might jeopardize the work of the user, making the technique inefficient.

Therefore I'd like to suggest to implement an option where a system tray popup is shown instead. When the user clicks the pop up, the window to tag the break is shown (as it is now). Optionally, a sound could also be played to emphasize the break.

Sometimes, it is possible to perform a bit of multitasking. A task may require attention every 5-10 minutes, in which time another similar task may be performed. - Both tasks are billable.
An example is server maintenance for a client (or several clients). Installing and configuring updates, software, etc. - Often such tasks are "fragmented" and may be performed in parallel.
It would be great to be able to have an option in Settings to switch on "Track Multiple tasks simultaneously", which enables several stopwatches in parallel. - This saves me from having to manually tracking it and manually adding it to the timeframe.

Whilst it's currently possible to zoom in/out in the Day\Timeline view, you have to do this manually and it can be very granular so you can end up recording to the second.

I would like to see an option to be able to configure the default view e.g. 5min, 15min interval etc.

This would ease recording and categorising tags for organisations that have rules around minimum billable time, or minimum time recorded intervals e.g. 5 or 15mins particularly when auto-tagging may nto be appropriate

NOTE: workaround for recording time as whole mins can be found in this request "Tagging snapping at 5min"
http://support.manictime.com/forums/222041-feature-requests/suggestions/12835254-tagging-snapping-at-5min

Currently, the Linux client lacks its own UI - it must be used with a separate server to act as its UI. The problem is, if you're already using a remote central server to coordinate multiple clients you can't run that server locally - and having to depend on a remote server as the only form of UI makes it impossible to work while offline (i.e. on flights, out in the field, etc). Furthermore, the only way to use screenshots is by syncing them - which will consume an immense amount of additional data, which may not be feasible if your clients are on metered connections. Thus I really think some form of a true local UI is still needed. Options:

1) Port the Windows client to Linux, natively. Obviously this is by far the most ideal from a user's standpoint, as the Windows client is far more convenient & powerful than a browser-based solution.

2) Support the Windows client running in WINE.

3) Have the Linux client fire up its own internal webserver, to act as its own dedicated UI. This loses the benefits of that great Windows UI, but would greatly simplify setup, enable users to work offline, and avoid the need to remotely upload all screenshots. Then the Linux client could still be connected to a "true" central remote server, in the same way as Windows clients.