Worklog Rescue documentation

Worklog Rescue is an Atlassian Forge app for Jira Cloud. It reads the activity you’ve already done in Jira and lets you fill missing worklogs in seconds, without timers or surveillance. This page covers installation, the main screens, and the most common workflows.

What is Worklog Rescue

Worklog Rescue is two things in one app:

A calendar dashboard for your Jira month. Every working day is colour-coded by completion. Drill into a missing day and Worklog Rescue surfaces the issues you actually worked on, ranked by your real Jira activity (comments, status changes, assignments, mentions, prior worklogs). You pick which issues to include, allocate hours with a step picker, and submit in batch.
A one-click time logger on every Jira issue. A compact panel inside any Jira issue lets you log time without leaving the issue — today, yesterday, or any back-date. Smart text input parses 2h 45m, 2:45, and 165m as the same duration.

It is not a timer, a productivity tracker, or a surveillance tool. There are no keystroke logs, screenshots, active-window monitors, or productivity scores. Everything the app stores lives inside Atlassian’s Forge platform — the Forge manifest declares no external network access.

Install and first run

Marketplace install

From any Jira Cloud site where you are a site administrator:

Open Apps → Explore more apps in the top navigation, or go to marketplace.atlassian.com.
Search for Worklog Rescue and pick the Verro Labs listing.
Click Get it now, choose the Jira Cloud site, and approve the requested permissions.
Worklog Rescue installs in seconds. Open it from the top navigation under Apps, or from the Worklog Rescue link in the Jira sidebar.

Pilot / direct install

During the pilot phase, an install link is shared directly. Open the link while signed in to your Atlassian account, pick your Jira Cloud site, approve the permissions, and the app appears in Apps → Manage your apps.

Required permissions

read:jira-work write:jira-work read:jira-user storage:app

That’s all four. The app does not request external-fetch scopes or any data access beyond what you can already see and write in Jira yourself.

First steps after install

Open Settings (sidebar).
Pick the Jira projects you want Worklog Rescue to scan for your activity. The app will look only at these projects when ranking suggestions.
Pick your holiday calendar (200+ countries available, or pick None). Holidays in the chosen country drop out of your monthly required hours automatically.
Adjust your working days if you don’t work a standard Mon–Fri week.
Click Save. Worklog Rescue rebuilds your current-month dashboard.

The Calendar dashboard

The Calendar is Worklog Rescue’s primary screen and the one most teams open daily.

What you see

Month grid. Every day of the current month, coloured by completion state:
- Green: fully logged against your target.
- Blue: partially logged (in progress).
- Striped blue: drafts staged, ready to submit.
- Red: activity happened but no worklogs — the “act now” state.
- Gray: non-working day (weekend, holiday, PTO).
Header progress bar. Your monthly logged total against your monthly target. Holidays and PTO are subtracted from the target automatically.
Day detail panel. Click any day to see logged worklogs, draft hours, and the issues Worklog Rescue suggests you worked on that day.

Common actions on a day

Quick-log a suggested issue. One click on a chip (e.g. 1h) adds it as a draft.
Fill missing hours. Opens the allocation dialog (see below).
Copy from another day. Picks a source day and copies its worklog structure to the current day.
Mark as PTO. Removes the day from your required-hours total. Submitting drafts on PTO days is blocked.

Issue panel quick-log

Open any Jira issue. The Worklog Rescue panel appears in the issue’s sidebar (under the Apps section). It lets you log a worklog without leaving the issue:

Pick the date — Today, Yesterday, or any past date via the date picker.
Type the duration. The smart input parses 2h 45m, 2:45, 165m, and 2.75 as the same value. Or pick one of the preset chips (configurable in Settings).
Optionally add a comment.
Click Log to Jira. The worklog posts immediately.

The panel also shows how much you’ve logged on this issue this month, your most recent entries, and a hint if you already have a draft for this issue elsewhere in the app.

Filling missing days

Click Fill missing on any incomplete day in the Calendar to open the allocation dialog.

Day context header. Shows the date, the hours already logged, your daily target, and the remaining hours to allocate.
Suggested issues. A ranked list of issues Worklog Rescue thinks you worked on that day. Each suggestion shows the signals that surfaced it (e.g. “you commented”, “you closed it”, “you were assigned”).
Step picker. Pick the increment for the + and - buttons: 15m, 30m, 1h, or 2h.
Add another issue. If Worklog Rescue missed an issue you worked on, search for it by title or key. Results come from your configured projects only.
Fill remaining. A shortcut that distributes the remaining hours across the issues you’ve checked.

Nothing is logged to Jira from this dialog. The dialog creates drafts; you submit them in batch from My Month or from the Calendar header.

You always confirm. Worklog Rescue never auto-creates worklogs on your behalf. Every entry that reaches Jira passed through a draft you reviewed and an explicit Submit click.

Settings

Open Settings from the sidebar to configure personal preferences, working days, the holiday calendar, and quick-log presets.

Personal settings (visible to every user)

Your projects. The Jira projects Worklog Rescue scans for your activity. Empty list = no suggestions until you pick at least one.
Personal daily target override. Override the workspace daily target (default 8h) with your own value, e.g. 6h for a part-time setup.
Working days. The days of the week that count toward your required hours. Non-working days render gray on the Calendar but stay loggable for overtime.
Holiday calendar. Pick from 200+ country calendars (powered by the date-holidays library). Pick None if your team doesn’t observe statutory holidays. The setting is per-user, so colleagues in different countries each see their own.
Excluded issue types. Issue types you don’t want surfaced as suggestions (default: Epic, Initiative). Loaded from your Jira instance.
Quick-log presets. The duration chips that appear next to suggested issues and on the issue panel.
Show low-confidence suggestions. Surfaces additional issues that didn’t reach the high/medium tier ranks.
Theme. Light / Dark / System.

Workspace settings (admin-only)

Workspace daily target. The default daily target hours for users who haven’t set a personal override. Editable only by Jira site administrators.
Managers. Users granted access to the Team view (see below). Editable only by site administrators.

Clear my data

Wipes your personal app data (drafts, ignored issues, settings overrides, cached scoring). Workspace settings stay. Useful when handing off a Jira account or testing a clean state.

Manager Team view

Visible only to users designated as managers in Settings.

Create a team. Add members by name or by picking everyone assigned to a specific project.
Completion tracking. The team page shows each member’s monthly completion percentage, sorted by missing hours descending (most behind first). Hours come from each member’s real worklogs in Jira.
Nudge. Sends a polite in-app reminder banner to a team member to log their missing hours. The nudge banner is distinct from the automated month-end reminder — it identifies you as the sender by name.
Team CSV export. One row per (member × issue) with hours, project, and date range.

Privacy by design. The Team view shows aggregate completion percentages and hour totals only. It never exposes which specific issues a team member worked on, comment content, or any individual worklog detail beyond what the manager could already see in Jira themselves.

CSV exports

Worklog Rescue offers two CSV exports for finance and billing handoff:

My Month CSV. Available from My Month → Export CSV. One row per submitted worklog, including issue key, date, hours, comment, and project. Open in Excel or Numbers; column headers are stable across releases.
Team CSV. Available from the Team page, manager-only. One row per (member × issue), with hours, project, and date range.

FAQ

Where is my data stored?

Inside Atlassian’s Forge platform, under Atlassian’s existing data-residency and security commitments. There is no separate backend, no analytics pipeline, and no third-party data processor. The Forge manifest explicitly declares no external-fetch scopes.

Does the app see my password or any tokens?

No. Worklog Rescue uses Forge’s scope-based OAuth (read:jira-work, write:jira-work, read:jira-user, storage:app). It never sees, requests, or stores passwords, personal access tokens, or any shared secrets.

Does it work with Jira Service Management?

Not for v1.0. JSM tickets technically have worklogs and the app would partially function on them, but the suggestion engine is tuned for dev-style activity (comments, status changes, assignments) and JSM workflows look different. JSM support is on the roadmap once the Jira release lands.

What countries are supported for the holiday calendar?

The library backing the holiday calendar (date-holidays) supports over 200 countries and territories. Only public holidays count — bank-only, school, observance, and optional types are intentionally excluded to avoid surprises (e.g. Sweden’s bank-only Midsommarafton is not subtracted from your required hours).

Can I run Worklog Rescue on a non-standard working week?

Yes. Pick any combination of weekdays in Settings → Working days. Part-time schedules like Mon/Wed/Fri are first-class. Non-working days render gray on the Calendar but remain loggable for overtime.

What happens if I submit the same draft twice?

Submissions are idempotent. Each draft carries a unique key; retries against the same draft return the existing Jira worklog ID instead of creating a duplicate. Network errors are safe to retry.

Is there a daily cap?

Yes. The combined total of submitted worklogs and staged drafts on a single day cannot exceed 24 hours. This cap is enforced server-side on every draft and worklog mutation. A 16-hour soft warning appears in the UI before reaching the hard cap.

How do I uninstall the app?

Open Jira → Apps → Manage your apps → User-installed apps and uninstall Worklog Rescue. All of the app’s storage is automatically cleared by Forge on uninstall, and the app also runs an explicit cleanup hook to actively delete any per-user data the platform might otherwise retain.

Support

For questions, bug reports, or feature requests, email support@worklogrescue.com.

For privacy-specific enquiries, see the privacy policy.

Discussion threads also live on the Atlassian Community — the Worklog Rescue space is linked from the Marketplace listing page.