TimeReg Tool

Connects to your Clockify and ClickUp, resolves BC customer codes and Progressus job/task numbers, and displays a ready-to-use reference table for filling in BC/Progressus time registration manually.

Prerequisites

• Node.js 18 or newer - required to run the tool.
• Git - optional. Without it the tool runs fine, but the automatic updates and team sharing of project numbers are disabled. Sharing your own project numbers also needs a GitHub account with push access to this repository.

Getting the tool

You can either:

• Clone with git (recommended): you get automatic updates and can share/receive project numbers with the team.
• Download the ZIP from GitHub (green Code button → Download ZIP) and unzip it: this works for everyday use, but because there is no git repository, the update and team-sharing features are disabled. Your project numbers are still saved locally and work normally - they just aren't pushed to or pulled from the shared repository.

Setup

1. Run the tool

Double-click start.bat. It runs start.ps1, which checks the requirements (Node.js, and optionally Git), offers to open the download page if anything required is missing, installs dependencies on first run, then starts the tool and opens it in your browser.

Alternatively, from a terminal:

npm install
node server.js

Then open http://localhost:3000.

2. First-run setup

On first launch the tool shows a setup screen. Paste your Clockify API key and click Connect - it will automatically look up your workspace and user ID and save config/settings.json for you.

Where to find your API key: Clockify → Profile icon → Profile Settings → scroll to API → Generate API key.

3. Clockify project naming convention

Project names must include the BC customer number in parentheses:

Vigmann (BCUK-P00042)
Lobiz - Phase 2 (BCDE-P04711)

The tool parses anything matching (DWDK-Pxxxxx) from the project name automatically. Projects without this pattern show as red rows.

Daily workflow

1. Open the tool - it defaults to yesterday's date
2. Click Fetch
3. Use the table as a reference while filling in BC/Progressus:

Row colour	Meaning	Action
Green	All codes resolved	Copy BC Customer, Job No, Task No, Work Type directly into BC
Amber	BC customer found, Progressus codes missing	Click + Add Progressus mapping, fill in once - remembered for all future days
Red	No (DWDK-Pxxxxx) in the Clockify project name	Edit the project name in Clockify

Adding Progressus mappings in advance

When a PM gives you Job No and Task No before you have logged any time, go to the Mappings tab → + New Mapping → select the Clockify project from the dropdown → fill in the codes → Save.

Sharing with colleagues

Share the folder or git repo. Each person:

1. Double-clicks start.bat (it checks requirements and installs dependencies on first run)
2. Follows the setup screen to connect their own Clockify account

config/settings.json is personal (git-ignored). config/mappings.json and config/project-codes.json are shared and committed to git, so the team can share Progressus mappings and project numbers.

• Receiving others' additions: git pull. The repo is public, so this needs no account or SSH key. (If you got the tool as a zip/shared folder with no git remote, you won't receive updates - ask for a fresh copy.)
• Sharing your own additions: needs push access to the repo (a git account), then git commit + git push. Without it, your additions stay local - they still work for you, they just aren't shared.