# 7pace Time Tracker > 7pace Time Tracker (Azure DevOps) — create/edit/delete worklogs in 7pace on a SINGLE day or across a range of weekdays. Primary path is the bundled Python 7pace REST API script (fast, no UI); browser UI automation of 7pace is a fallback. Use when the user wants to log/register/track work hours in 7pace on a work item (by numeric ID or by name) — e.g. "register 4 hours on - Skill: `whobat/7pace-time-tracker` (Agent Skill, multi-file: 6 files) - Install (CLI): `npx skillmds@latest add whobat/7pace-time-tracker` - Raw SKILL.md: https://api.skillmd.com/api/skills/whobat/7pace-time-tracker/raw - Safety review: pending - Works with: Claude Code, Claude.ai, OpenAI Codex - Category: DevOps & Infra - License: MIT - Author: whobat (https://skillmd.com/u/whobat) - Updated: 2026-09-17 - Page: https://skillmd.com/skills/whobat/7pace-time-tracker --- # 7pace Time Tracker > **This skill targets [7pace Timetracker](https://www.7pace.com/) for Azure DevOps.** All time entries (worklogs) are created in 7pace via its REST API at `https://.timehub.7pace.com`. Creates / updates / deletes worklogs in 7pace. **Prefer the API script** (`scripts/timetracker.py`) — it calls the 7pace REST API directly and is far cheaper than driving the UI. Fall back to the browser UI only if no API token is available. It supports **two modes**: - **Single day** — one entry on one date: `--date --hours `. - **Range of weekdays** — batch across a period with a per-weekday pattern: `--from --to --hours ""` (weekends are skipped automatically). `SCRIPT` = this skill's `scripts/timetracker.py`. Config lives at `~/.7pace/config.json` (the default — `--config ` only needed to override). Always pass `--yes --json` for automation. ## First-time setup (once) `python SCRIPT --auth` prompts (input hidden) for the 7pace **Bearer API token** (7pace → Settings → Reporting & API → Create New Token) and an optional **Azure DevOps PAT** (only for `--search`, scope "Work Items (Read)"), and writes `~/.7pace/config.json` (chmod 600, gitignored). The two tokens are different systems — the ADO PAT does not work for 7pace and vice-versa. Skip if config already has valid tokens. ## Inputs to parse from the user's request | Input | How to pass | Notes | |-------|-------------|-------| | **One date** | `--date 2026-04-09` | Single-day mode. Accepts `YYYY-MM-DD`, `DD-MM-YYYY`, `today`, or `yesterday`. Convert other relative dates ("last Friday") to an absolute `YYYY-MM-DD` yourself. | | **Date range** | `--from 2026-04-01 --to 2026-06-08` | Batch mode. Same date formats; `--to today` = up to today. | | **Hours (single)** | `--hours 4` or `--hours 7:30` | Decimal or `HH:MM`; comma or dot both work (`7,5` = `7.5` = `7:30`). | | **Hours (range)** | `--hours "7.5 mon-thu and 7.0 fri"` | Per-weekday pattern. Weekday tokens: `mon tue wed thu fri sat sun` (or full names). Only the named days are created, so Sat/Sun are skipped. `all` = all weekdays. | | **Comment** | `--comment "Work"` | Mandatory — 7pace rejects empty comments. | | **Work item** | `--work-item 12345` | Numeric ID. If the user gives a **name** instead, resolve it with `--search` first (see Examples). | ## Holidays (adapt to your organization's policy) Many organizations require public holidays that fall on a weekday to be booked on a dedicated **non-working-time work item** (with a fixed comment such as "Public holiday", same hours as a normal day) — NOT the normal work item. If the user's organization has such a policy: ask for (or look up in your notes) the holiday work item ID and comment, apply the local public-holiday calendar, and if a holiday already has time logged, flag it instead of duplicating. ## Examples > Replace dates/IDs/hours with the user's actual request. `--json` returns machine-readable output you can parse and report back. **1. Single day, known work item** ("register 4 hours on #12345 on 9 April 2026"): ``` python SCRIPT --date 2026-04-09 --hours 4 --work-item 12345 --comment "Work" --yes --json ``` **2. Single day = today** ("log 7.5 hours today on #12345"): ``` python SCRIPT --date today --hours 7.5 --work-item 12345 --comment "Work" --yes --json ``` **3. Register by work-item NAME** ("log 7:30 today on Website Redesign") — search → pick → create: ``` python SCRIPT --search "Website Redesign" --json # returns matches with id/title/project/state # 1 match → use it. Multiple → ask the user which id (show title — project — state). 0 → tell them. python SCRIPT --date today --hours 7:30 --work-item --comment "Work" --yes --json ``` **4. Date range with a weekday pattern** ("7:30 Mon–Thu and 7:00 Fri from 1 April to today"): ``` python SCRIPT --from 2026-04-01 --to today --hours "7.5 mon-thu and 7.0 fri" --work-item 12345 --comment "Work" --yes --json ``` Weekends are skipped automatically; days that already have time are skipped by default (`--no-skip-existing` to override). **5. A holiday weekday** (book non-working time, if the org has such a policy): ``` python SCRIPT --date 2026-05-14 --hours 7.5 --work-item --comment "Public holiday" --yes --json ``` **6. List, update, delete** (find an entry's id, change it, or remove it): ``` python SCRIPT --date 2026-04-09 --list --json # -> worklogs with ids python SCRIPT --update --hours 8 --work-item 12345 --comment "Work" --yes --json python SCRIPT --delete --yes --json ``` **7. Dry-run / health check** (verify auth + connection, creates nothing): ``` python SCRIPT --date today --hours 0 --dry-run --json # expect status: dry_run ``` ## Workflow for a bulk range (steps) 1. **Confirm the plan first** (day count, total hours, work item, comment) — a range can be 40+ entries. 2. **Health check** (Example 7) → expect `status: dry_run`. 3. **Batch create** the range (Example 4). 4. **Holidays** (when the org books them on a dedicated work item): the batch also creates entries on holiday *weekdays*. For each holiday in range, convert it: `--date --list` to get the `id`, then `--update --work-item --comment "Public holiday" --hours --yes`. (`--update` sets the work item from `--work-item`; always pass it so you don't reset it.) 5. **MANDATORY final validation** (always last): `--from --to --list --json` and confirm **every weekday in range has an entry** — normal work item on regular days, the holiday work item on holiday weekdays. The only acceptable blanks are weekends and pre-existing days you intentionally left. Any other blank weekday is a gap → fix and re-list. Don't declare done until clean. 6. **Report**: days created (date+hours), holidays converted, days skipped (weekend/holiday/existing), totals, and "validation: every weekday accounted for". Fail loud on any gap or `status: error`/`partial`. For a **single day** you don't need the full workflow — just confirm the request and run Example 1/2/3, then report. ## Search details `--search ""` matches work-item titles **org-wide** (across all ADO projects) by default; add `--project "MyProject"` to narrow. Returns `matches` (id, title, type, state, project). Exactly 1 → use it; multiple → ask the user (show id — title — project — state, so they avoid Obsolete/closed items); 0 → tell them; ~50 (the cap) → ask them to refine. ## Errors If the script returns `status: error` with `401`/auth problems, the token is missing/expired → tell the user to regenerate the 7pace token (Settings → Reporting & API; it is NOT the Azure DevOps PAT) or run `--auth`. Only then consider Method 2. ## Method 2 (fallback): browser UI automation Only if the API token cannot be used. Drive the 7pace **Timesheet weekly grid** via the claude-in-chrome MCP. Full click recipe, coordinates and gotchas (masked Length field, double-click-Comment trick, limited-mode data lag) are in [REFERENCE.md](REFERENCE.md).