Adds JIRA Integration

[CharlesWinter]

Adds a "push" command that will push your timetrace records for that day to a remote system (JIRA in this PR).

This PR is still a draft. I've thrown caution to the wind and have exactly zero tests for what I've done, as I started this work just for fun. Please don't merge it yet until there are tests. The purpose of the PR is simply to make you guys aware that I've been working on this, and to of course allow others to improve upon it as they see fit. As it stands the code does work, and records are pushed where timetrace sees fit, and are pushed only once. It of course also needs a readme entry on how to actually set it up.

How does it work? (see the GIF for a demo)

• The user adds their credentials (including an API token) to the timetrace config file as specified here
• Through a new cobra command "push" the user can select which integration they wish to push to (only jira at the moment)
• I examine all records from today here and loop through to find a subset of those records that should be added to JIRA as worklogs, these worklogs are presented to the user to "confirm" the push.
• records will be pushed to JIRA if: A. The project ID for the record matches a ticket. e.g. tw-20@timetrace or tw-2 would be pushed to tw-20 and tw-2 respectively. B. The record has not been pushed before.
• Once confirmed, those worklogs are added to JIRA.
• worklogs have metadata (entity properties in JIRA speak) in the form of a key value pair added to them of the form timetrace_record_id: "2020-10-20T10:32:00". It seems timetrace uses the startdate as a unique ID for a record so I thought I would continue the convention in JIRA. This metadata is added so a record can only be pushed once.

Technical Considerations for Reviewers

• Timetrace seems to be well decoupled, with a nice use of dependency injection and inversion. I've tried to continue this with a slightly presumptious introduction of an interface here Any integration need only fufill this to be used with the push command.
• The JIRA API is horrendous in that one must make a second call to add metadata to an object. This has resulted in a fair few API requests going over the wire for each push. A lot of the request making boilerplate in the repository can be consolidated into functions.
• I've added a spicy terminal hack that has those cool little crosses/ticks appear in place in the table when performing a push. I've no idea if this will work on a wide variety of terminal emulators, and when it goes wrong it looks bloody awful with a feast of emojis on the screen. I'm happy to drop this, I did it more for my own personal interest, but it's pretty evil.

To conclude, still early days for this PR, as it started mainly for my own enjoyment and the code needs some love/tests/rebasing to get it in :) I'll continue working on it when I get time.

Contributions welcome.

[dominikbraun]

Wow, thanks a lot for this massive feature! I'm just going to release timetrace v0.11.1 today and review and merge some PRs in the pipeline for timetrace v0.12.0 - then I'll be able to take a closer look at the push command.

[dominikbraun]

Hey @CharlesWinter, is this ready to be reviewed? :-)

[CharlesWinter]

Hi @dominikbraun it's definitely missing some tests, so I don't think it's ready for merge yet.

But I think the implementation isn't likely to change so if you want to take a look I would welcome it!