Introducing Worklog Approvals & Capacity Planning in TimeEase

The Problem: Logged Time Isn't Reviewed Time

Jira will happily let anyone log any amount of time on any issue, and it stays that way forever — no review step, no sign-off, no comparison against what a person was actually expected to work that week. For agencies billing clients off worklogs, or managers trying to plan the next sprint around real capacity, that's a real gap:

• You bill a client for hours nobody double-checked
• You plan next sprint without knowing who's already overloaded
• A miskeyed worklog (8h instead of 0.8h) ships straight to your reports

Step 1: Set Weekly Capacity Baselines

Capacity lives in TimeEase Settings → Rates & Capacity — the same table that already handles hourly rates for Feature Analytics, now with a second column.

• Per-user baseline: Click the Capacity cell next to a teammate's name and enter their expected hours per week (e.g. 40). Press Enter or click away to save.
• Optional, per person: Not every user needs a baseline — contractors on a different arrangement, or anyone you simply haven't set up yet, are just skipped in the capacity math elsewhere in the app.
• One-click clear: The Clear button removes both the rate and the capacity baseline for that row in a single action.

Step 2: Review Worklogs Against Capacity

The new Worklog Approvals tab is where that baseline becomes useful. Pick a period — Today, Current Week, Current Month, Previous Month, Last 7 Days, or a custom range — and you get a roster of your team with six columns: Capacity, Planned, Logged, Remaining, Utilisation, and Status.

• Planned scales the weekly baseline to the period you selected (a 40h/week baseline over a 3-day range plans ~17h, not 40h)
• Utilisation renders as a meter bar, and turns pale red — not solid alarm red — once someone crosses 100%, so an overloaded week is visible without feeling like an accusation
• Status shows at a glance whether a person has "No worklogs," is "All approved," or has "N Pending" entries waiting on you

Click a row to expand it and see the individual worklogs — date, issue, time logged, comment — and approve them one at a time, or hit Approve all to clear every pending entry for that person in one action.

A Record, Not a Lock

One deliberate design choice: approving a worklog in TimeEase doesn't lock it in Jira. Forge apps can't restrict native Jira edits, and we didn't want to pretend otherwise. Instead, approval stores a snapshot of the time and comment at the moment you reviewed it.

If someone edits that worklog afterward — changes the hours, rewrites the comment — TimeEase flags it as “Modified since approval” right next to the status badge. You're not blocked from anything, but you also can't miss that something changed after you signed off on it.

Who This Is For

• Agencies: review worklogs before they turn into a client invoice, instead of billing whatever happened to land in Jira
• Team leads: spot over- and under-booked teammates a week before it becomes a missed deadline or burnout
• Anyone tired of chasing corrections after the fact: catch the miskeyed 8-hour worklog before it ships in a report, not after

Getting Started

1. Go to Apps → Manage apps → TimeEase settings → Rates & Capacity
2. Set a weekly capacity baseline for each teammate you want to track (rates are optional and independent)
3. Open the Worklog Approvals tab, pick a period, and start reviewing