pindrop
/
timetracker
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

Added subtotal language after 2020-09-16 commit to do_process 

Described the current output of do_process.sh in the requisite section of this README.md.  Also mentioned that the tally caveat is *MUCH* less prevalent now that I can compare the subtotal thus far with what's in Clarizen, as I go.
This commit is contained in:
tblancher 2021-02-12 16:32:56 -05:00 committed by GitHub Enterprise
parent e4bd71e9ec
commit 83d90bd4ba
1 changed files with 9 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

15
README.md
View File

@ -62,7 +62,7 @@ Section total: 8.41hrs
You may have noticed, the output of timetracker.py is in alphabetical order by category, then by task. This follows for `./do_process.sh` and `./chug.sh` below.
## `do_process.sh`
This script filters the output of timetracker.py, giving each category (in square brackets) its own section, with its own tallies. The header is the list of categories and the log file basename (below this is `example`, but would normally be a date such as `2017-12-08`). After the header, each line of output and sections are designed to be directly transferred to Clarizen manually, and the tally used to verify the daily and weekly totals in Clarizen. It calculates the time total for each organization/category. At the end it prints a grand total for the day, which should be used to cross-verify in Clarizen.
This script filters the output of timetracker.py, giving each category (in square brackets) its own section, with its own tallies. The header is the list of categories and the log file basename (below this is `example`, but would normally be a date such as `2017-12-08`). After the header, each line of output and sections are designed to be directly transferred to Clarizen manually, and the tally used to verify the daily and weekly totals in Clarizen. It calculates the time total for each organization/category. It also prints the subtotal thus far, to be sure no items are missed when adding them to Clarizen. At the end it prints a grand total for the day, which should be used along with the subtotals to cross-verify in Clarizen.
```
[CS Support]
@ -80,29 +80,30 @@ example
[CS Support] internal task 2 0.50hrs
Section total: 3.75hrs
Subtotal: 3.75hrs
[Customer 1] PDROP-0000000 case-related task 1 1.00hrs
[Customer 1] PDROP-0000000 case-related task 2 0.25hrs
[Customer 1] task 1 0.08hrs
Section total: 1.33hrs
Subtotal: 5.08hrs
[Customer 2] task 2 1.75hrs
Section total: 1.75hrs
Subtotal: 6.83
[Customer 3] external meeting 0.75hrs
Section total: 0.75hrs
Subtotal: 7.58
[Productive Non-billable] email triage 0.75hrs
[Productive Non-billable] internal task 1 0.08hrs
Section total: 0.83hrs
Subtotal: 8.41hrs
Grand total: 8.41hrs
@ -155,6 +156,8 @@ In the same vein as month-pack.sh, year-pack.sh tars up all the monthly tarballs
# CAVEATS
## Tallies
Since I (the author, Trey Blancher) have been using this system to keep track of time, I've noticed that sometimes either Clarizen or these scripts get slightly off. Usually it's no more than 0.25 hours off in the tallies, but it gets time consuming trying to track down where the tally went wrong. If I do find the culprit, it's usually because I've entered the wrong time for a specific task in Clarizen (i.e., entering '0.08' instead of '0.25' for some tasks).
### 2020-09-16 UPDATE
As of the institution of the subtotals, the tallies being off in Clarizen is a *MUCH* less frequent problem. Usually if Clarizen is off it's because I missed an entry, or Clarizen didn't absorb an entry properly (that happens from time to time).
## vim
The vim-specific files in this repository are tailored for my tastes. One big item of note, I've disabled vim cursor navigation with the arrow keys (Up, Down, Left, Right), to force me to get into the habit of using h, j, k, l for cursor navigation, and only navigate in normal mode (not insert mode). You will probably want to delete the following lines from .vimrc if you're not interested in the true Vim way®:
@ -188,6 +191,6 @@ The 'End' macro copies the category and task name from the previous 'Begin' macr
2020-03-11 19:30:36: End [CS Support] timetracker doc
2020-03-11 19:30:36: Begin
```
I also have Keyboard Maestro text string triggers for common categories, to minimize typing. For instance, the text string triggers `[css` becomes `[CS Support] `, `[non` becomes `[Productive Non-billable] `, `[mm` or `[MM` becomes `[Mass Mutual] `, `[vzw` becomes `[Verizon Wireless] `, `[pin` becomes `[Company] ` (to match the Pindrop related items in Clarizen), etc. These are included in `timetracker.kmmacros` for your convenience.
I also have Keyboard Maestro text string triggers for common categories, to minimize typing. For instance, the text string triggers `[css` becomes `[CS Support] `, `[pro` becomes `[Productive Non-billable] `, `[mm` or `[MM` becomes `[Mass Mutual] `, `[vzw` becomes `[Verizon Wireless] `, `[pin` becomes `[Company] ` (to match the Pindrop related items in Clarizen), etc. These are included in `timetracker.kmmacros` for your convenience.
See [INSTALL.md](https://github.atl.pdrop.net/tblancher/timetracker/blob/master/INSTALL.md) in this repository for a detailed explanation of how to use the `timetracker.kmmacros` and set up the vim macros.