About this skill

Problem

TAPD timesheet entry often pulls engineers back into day-by-day input: weekdays and holidays need manual curation, multi-task effort percentages need repeated hand calculations, and failed submissions can lead to accidental retries. This skill turns the workflow into a local HTML app backed by tapd_proxy.py, which handles TAPD API CORS, Bearer Token authentication, and response classification, making period-based submission previewable, voidable, and retry-aware.

How It Works

Open tapd-timesheet-v4.html and keep tapd_proxy.py running on 127.0.0.1:8899
Configure the TAPD personal access token and name; the app derives workspace_id from the 19-digit task ID
Select a period, edit working days, and use built-in 2024–2027 holiday data
Add task IDs, effort percentages, and independent date ranges; the app validates that totals reach 100%
Generate a date × task preview, then submit line by line with progress feedback
Local localStorage keeps the latest 100 records and supports bulk voiding through the TAPD delete API

Boundaries and Notes

Designed for single-user desktop browsers, without collaboration or mobile support
Supports only entity_type: 'task', not requirement or defect entities
No bidirectional sync with already submitted TAPD timesheets; submitted records cannot be edited directly, only voided and resubmitted
Holiday data is static built-in data and may need manual updates; submission and deletion both depend on the local proxy

Screenshots

Use Cases

On Monday, split the prior month's working days by task effort, preview the result, and batch-submit it to TAPD.
After adding two front-end tasks, adjust date ranges and effort percentages so the total stays 100% before previewing.
After finding an incorrect day, select that history entry and bulk-void it, then resubmit the corrected task.
When submission returns 401 or a workspace_id mismatch, inspect proxy logs and validate the 19-digit task ID.

Best For

Front-end engineers who must enter daily multi-task development effort into TAPD each month
Project members who need to split task effort to 100% before period submission
Developers who found incorrect submitted timesheets and need bulk voiding before resubmission
Office-tool maintainers who use a local HTML app and Python proxy to call the TAPD API