An introduction
Only to be used if project manager permits
No pressure to upload (at least at your side)
Only simple conflict detection
Inofficial tool - no support from ELCA
Provided as is, use at you own risk. Check results in Vertec!
Feedback (issues, improvements) welcome
Only switch to Jimp on start of month
No manual
Easy recording of presence time
Comfortable service number assignment
Upload to Vertec
Optional JIRA connector (currently not used)
Auto-updating launcher (thx to JBR!)
Local storage of data
Readable JSON files
Located in %AppData%/Roaming/Jimp
Upload to Vertec using web "API"
Only one-way sync
dev2devs
Log file: %AppData%/Local/Temp/Jimp.log
Start/switch/stop activities
Edit/split activities
Delete/merge activities
Horizontal scroll
User inactivity
Assign text and service number
No explicit 9999-999-99
Time distribution (%, reject)
Continue work (.)
Ask someone (?VISA)
Favorites
Selecting days and range
Search / investigation
References
Report and assign missing service numbers
Upload (daily!)
Merging of work entries "task 1 (0:25), task2 (0:35)"
Concurrent usage with web client does not work
Conflicts
Colors
Autosave (on focus lost) and recovery
Close Dialog
workPackages.json
<date>.json(.old): days of current month
old/*: old months (read only)
templates.json
watch.json: watch for restrictions
app/*: binaries
cache/*: last known state of Vertec (for conflicts)
Best case
PL informs you about changes
You do the changes
OK
PL makes changes after validation
Only number changes get detected
Text must remain the same
Vertec Web-Client only supports one service instance
Mail with link to installer
Test Jimp WITHOUT uploading
Switch after month validation
If it does not fit, upload and uninstall