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
Similarly to #160, we’d like to get rid of our custom fork and have as much of our changes as possible in the upstream gTimeLog. Our fork lives at our Gitlab instance.
We ourselves made multiple attempts at refining and rebasing our changes, e.g. this, this one, or this one.
We attacked it differently, by extending the format to add an extra field, e.g.: 2018-06-22 09:00 +0200: ** morning
Ability to get the task list from Chronophage, our time tracking solution
This feature is roughly a match to the feature already present in gTimeLog, but in our fork it allows for hierarchy of tasks (e.g. customer: project: task-type: task: …)
Ability to upload to Chronophage
It’s basically a POST request at a URL IIRC
I’ll add more things later
The text was updated successfully, but these errors were encountered:
Similarly to #160, we’d like to get rid of our custom fork and have as much of our changes as possible in the upstream gTimeLog. Our fork lives at our Gitlab instance.
We ourselves made multiple attempts at refining and rebasing our changes, e.g. this, this one, or this one.
The three main features we need are:
2018-06-22 09:00 +0200: ** morning
customer: project: task-type: task: …
)I’ll add more things later
The text was updated successfully, but these errors were encountered: