<commit_before>FogHarvest submits time logged against Fogbugz tickets to Harvest timesheets.

All time logged to tickets is submitted to a task called "Development". The notes for the time entry contain the case number and its title.


* Does not attempt to limit API requests.
* When in debug mode will willfully print your password all over the screen and logfile in plain text.
* Makes no attempt to detect if time has already been posted (expect duplicates if you run it more than once a day).



Usage
-----

*Requires* Python 2.7

`python fogharvest.py`

This will process yesterday's timesheets. It is possible to control what time period is processed, and for which users; run `fogharvest.py -h` for more details.


Config
------

You'll need a `fogharvest.cfg` in the directory from which you launch fogharvest. It contains the urls of your Fogbugz and Harvest instances, usernames and passwords. There is an example in (`fogharvest.cfg.example` in the checkout).


Debugging
---------

Run `fogharvest.py --debug` to dump masses of info to the terminal. Add the `--dry-run` switch if you want to see what will be posted without posting it.<commit_msg>Formatted and neatened readme.<commit_after>FogHarvest submits time logged against Fogbugz tickets to Harvest timesheets.

Operation is rudimentary: all time logged to tickets is submitted to a
task called "Development". The notes for the time entry contain the
case number and its title.

* No attempt is made to limit API requests.
* When in debug mode willfully prints your password all over the
  screen and logfile in plain text.
* Makes no attempt to detect if time has already been posted (expect
  duplicates if you run it more than once a day).


Installation
------------

Clone the repository into a directory on a server that can reach your
Fogbugz and Harvest servers.


Usage
-----

*Requires* Python 2.7

`python fogharvest.py`

This will process yesterday's timesheets. It is possible to control
what time period is processed, and for which users; run `fogharvest.py
-h` for more details.


Config
------

You'll need a `fogharvest.cfg` in the directory from which you launch
fogharvest. It contains the urls of your Fogbugz and Harvest
instances, usernames and passwords. There is an example
(`fogharvest.cfg.example`) in the checkout.


Debugging
---------

Run `fogharvest.py --debug` to dump masses of info to the terminal.
Add the `--dry-run` switch if you want to see what will be posted
without posting it.
{'fraction_non_alphanumeric': 0.0678714859437751, 'fraction_numerical': 0.001606425702811245, 'mean_word_length': 3.7178030303030303, 'pattern_counts': {'":': 0, '<': 3, '<?xml version=': 0, '>': 3, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 2, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '433860', 'n_tokens_mistral': 704, 'n_tokens_neox': 669, 'n_words': 374}