Support for "duronly" entries.

[torotil]

Toggl has a setting that allows users to pause and resume time entries. Those time-entries then don't get a "stop"-time. Due to the filter in this plugin those time entries are ignored even though they are completed.

Currently I'm using a condition like ((!entry["stop"].nil? && !entry["stop"].empty?) || (entry["duronly"] && !entry["duration"].empty?)) to get all the time entries, but I'm unsure whether this is the best approach.

[SkyWriter]

When designing this plugin, I tried to make the logic as clear and simple as possible.

The entries are imported once and only once. Ever since that moment they become independent of each other. This approach gives you the following benefits:

1. You can edit them both in Redmine and in Toggl, and be sure your changes persist.
2. Since import happens only once, you have no conflicts to resolve. I.e. if the same entry gets changed both in Trello and in Redmine, you don't have to decide which one of them is correct.

Unfortunately this way of dealing with things makes it conceptually impossible to use pause-and-resume Toggl entries, which I too favored before starting to use this plugin.

If you have ideas of another concise algorithm that will allow you to exercise pause-and-resume stuff, I would happily implement it.

[torotil]

I see.

I'd propose to always update the time-entries in redmine:

1. Time entries that are created in redmine won't be touched.
2. Time entries created in toggl will be updated whenever they are edited in toggl.
3. Time entries created in toggl and edited in redmine will be overridden. (Toggl "owns" those time-entries).

I think 3. is not such a big issue since users who log time in toggl also tend to edit those entries there. Also editing existing time-entries in redmine is not that common (adding time entries is).

[SkyWriter]

What about deletion in Redmine or in Toggl?

Or changing the entries in such a way, that they become disconnected from the tasks or reconnected to different ones?

[torotil]

Good points.

• Deletion in redmine: if possible I'd block edits/deletes from within redmine for all time entries coming from toggl.
• Deletion in toggl: That one is tricky. I can live with orphaned entries though (a 99%-solution is good enough for me atm).
• Disconnect / reconnect from tasks: I don't think that's an issue with redmine. The time-entries could be deleted / reassigned to tasks as needed. I guess that's more important than following deletes in toggl - but still not as important as having all the time entries imported in the first place.

Also to avoid syncing "incomplete" time entries the import could be limited to all time-entries started at least X hours in the past.