You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Some in our company use tom for time tracking in our company, but everyone else just enters their worktimes into our accounting system FreeAgent. So if there was a way to directly export data from tom-ui to FreeAgent via API, we could simplify and unify the process of timesheet creation and signing in our company.
I imagine that the following user user interface would be suitable, at least for our purposes: a dialog "File → Sync …" that allows to set up multiple regular synchronization tasks. Each task would have the following parameters:
API type (such as FreeAgent, and later other types of export via API)
API access credentials (depending on API type; including the target location of the data in the external data storage)
Interval (weekly, monthly etc.)
Project (would allow to select one project or sub-project)
Aggregation (this will depend on how records can be stored in the respective external data store, and on the level of detail one wants to export; for example, one might want to export only daily totals, not including notes and actual time entries)
To preserve consistency between the tom-ui and exported remote data, data in tom should be marked accordingly. The "archived" mark seems suitable for this, as it indicates that a time entry cannot or should not be edited anymore.
When a new sync task is due to run, tom-ui would not just execute it but present the user with a dialog that says: "Snychronization task … for time period … is due. Please finalize your time entries and click the toolbar button 'Run pending sync tasks'.". This gives the user a chance to look through time records, check for consistency, check for spelling mistakes in the notes or missing notes etc., before finally committing the data to be synched and archived.
(There may be better ways to structure this dialog of course. The above is just my first idea.)
The text was updated successfully, but these errors were encountered:
@tanius Would reports in Freeagent have to aggregate tracked time of multiple persons on a single invoice? Or does Freeagent have timesheets per person?
Technically best might be a (self-hostable) server which aggregates time entries of one or more persons. An administrator could then configure daily, weekly, monthly syncing for one or more persons. But that's out-of-scope for now.
Yes, it has. It can store worktime per person just as tom, and even includes an integrated browser based time tracker. But it's rather rudimentary and not integrated with my time tracking for projects I don't do for that same company, so I don't use FreeAgent time tracking.
What we need is a way to transfer and store the tom timetracking data into FreeAgent timetracking data. Everything after that like invoicing etc. based on these time records is then FreeAgent's problem and out of scope for this issue.
Some in our company use
tom
for time tracking in our company, but everyone else just enters their worktimes into our accounting system FreeAgent. So if there was a way to directly export data fromtom-ui
to FreeAgent via API, we could simplify and unify the process of timesheet creation and signing in our company.I imagine that the following user user interface would be suitable, at least for our purposes: a dialog "File → Sync …" that allows to set up multiple regular synchronization tasks. Each task would have the following parameters:
To preserve consistency between the
tom-ui
and exported remote data, data intom
should be marked accordingly. The "archived" mark seems suitable for this, as it indicates that a time entry cannot or should not be edited anymore.When a new sync task is due to run,
tom-ui
would not just execute it but present the user with a dialog that says: "Snychronization task … for time period … is due. Please finalize your time entries and click the toolbar button 'Run pending sync tasks'.". This gives the user a chance to look through time records, check for consistency, check for spelling mistakes in the notes or missing notes etc., before finally committing the data to be synched and archived.(There may be better ways to structure this dialog of course. The above is just my first idea.)
The text was updated successfully, but these errors were encountered: