Worklog Courier support

Email support@plumblineapps.com. We aim to reply within one business day (UK hours).

When reporting a problem, include: your Jira site URL, whether Tempo is connected, the schedule you configured, and the approximate time of the run that failed. Never include your Tempo API token in an email.

To report a security issue, email the same address with "SECURITY" in the subject line.

FAQ

Does it work without Tempo?

Yes. Without a Tempo token, Worklog Courier exports Jira's own worklogs directly. The Tempo connection is optional and adds three things: real author names on Tempo-logged work, billable hours, and Tempo work attributes.

How does the author name fix work?

Tempo stores worklogs in Jira under a service account, so Jira-side exports and JQL show "Tempo Timesheets" instead of the person. This is architectural and neither vendor fixes it. Worklog Courier reads the real author's account ID from the Tempo API, looks each unique ID up against the Jira user directory, and writes the display name into every row before the file is built.

What schedules are available?

Daily, weekly, or monthly, at an hour you choose (UTC). Each run covers the completed previous period: yesterday, last week, or last calendar month. Delivery lands within about an hour of your chosen time, a scheduling constraint of Atlassian's Forge platform, so schedule "the morning of the 1st" rather than expecting 09:00:00 exactly. There is also a Send now button for on-demand exports.

Are there file size or row limits?

No row limits on the export itself: the app pages through the API, so month-end volumes that time out in UI exports work fine. Practical ceilings: email attachments are limited to roughly 40 MB by our email provider (far above a typical 50,000 row month), and the "download last export" button on the admin page only works for files under about 1 MB; larger exports are email-only.

Is my worklog data stored anywhere?

Not by us. The app runs entirely on Atlassian's Forge platform. Worklog data is processed in memory during a run and delivered by email; it is not written to any server of ours (we do not have any). Your Tempo token is stored encrypted in Atlassian's Forge secret storage. The one exception: a copy of your most recent export may be cached inside Atlassian's infrastructure to power the download button. The email itself is delivered through Resend, a US email provider. Full details in our privacy policy.

Can it edit worklogs or handle timesheet approvals?

No. The app is read-only by design and requests read-only permissions. It cannot change, approve, or delete anything in Jira or Tempo. If you need approval workflows, use Tempo's approval feature; Worklog Courier exports the resulting data.

What Tempo token scope should I use?

Create the token under Tempo > Settings > Data Access > API Integration with the "Worklogs (View)" scope only, and set a long or no expiry so scheduled runs do not break when the token lapses. The app never needs write access.