Documented Tyme import

This commit is contained in:
マリウス 2020-10-16 01:30:08 +01:00
parent 0722e1d23d
commit 4bdf38b6a1
No known key found for this signature in database
GPG key ID: C228EF0A530AF06F
3 changed files with 23 additions and 1 deletions

1
.gitignore vendored
View file

@ -15,3 +15,4 @@
# vendor/
/zeit
.DS_Store

View file

@ -11,7 +11,8 @@ make
## Usage
Please make sure to `export ZEIT_DB=~/.config/zeit.db` (or whatever location you would like to have the zeit database at).
Please make sure to `export ZEIT_DB=~/.config/zeit.db` (or whatever location
you would like to have the zeit database at).
### Track activity
@ -67,6 +68,26 @@ zeit erase 14037730-5c2d-44ff-b70e-81f1dcd4eb5f
zeit import --help
```
#### Tyme 3 JSON
It's possible to import JSON exports from [Tyme 3](https://www.tyme-app.com).
It is important that the JSON is exported with the following options set/unset:
![Tyme 3 JSON export](documentation/tyme3json.png)
- `Start`/`End` can be set as required
- `Format` has to be `JSON`
- `Export only unbilled entries` can be set as required
- `Mark exported entries as billed` can be set as required
- `Include non-billable tasks` can be set as required
- `Filter Projects & Tasks` can be set as required
- `Combine times by day & task` **must** be unchecked
During import, *zeit* will create SHA1 sums for every Tyme 3 entry, which
allows it to identify every imported activity. This way *zeit* won't import the
exact same entry twice. Keep this in mind if you change entries in Tyme and
then import them again into *zeit*.
Example:
```sh

BIN
documentation/tyme3json.png Normal file

Binary file not shown.

After

Width:  |  Height:  |  Size: 66 KiB