necatimeral / clockify-it Goto Github PK

Create Dockerfile(s) for Docker distribution and deployment guides:

• Docker
• Native (maybe as a windows-service?)

Check error handling and current design decisions.

Consider a new internal api design to minimize errors when handling time entries.
Prevent duplicate bookings or un-flagging of time-entries which weren't processed completely.

Azure DevOps doesn't provde a property time booking API.

But when working with azure devops, developers can track their progress on their own work items.
The integration should check the work item links for links to known integrations. This could be solved as a kind of "chained integration" which resolves the redmine integration for example when matching a redmine link.

Additionally, we could increment the "simple" fields Original Estimate, Remaining Work or Completed Work

Basic flow:

"WIT1234 Fix something" resolves to Azure DevOps WorkItem 1234 which has a redmine-link; extract ID and create redmine time-entry

• Basic Azure DevOps integration (Original Estimate, Remaining Work, Completed Work)
• Redmine over Azure DevOps (check hyperlinks to retreive redmine issue id)

The user can configure his timezone in his clockify profile.

For propery time entry fetching, we have to respect this value and use the correct time zone to build the fetch range.

From the api docs, regarding the start and end parameters:

You send time according to your account's timezone (from Profile Settings) and get response with time in UTC.

Helpful links:

• mattjohnsonpint/TimeZoneConverter

Create (semi) automatic versioning with releases on github.

Goal: Publish...

• NuGet-packages
• Docker-Images
• Native binaries

Bonus content

• Generate changelogs