A Tempo alternative

Switch from Tempo without losing a worklog

LogQuill reads what Tempo holds, gives every worklog back to the person who logged it, and brings your accounts, work attributes and teams. Run both side by side while you decide.

Get LogQuill for Jira Book a 30-minute demo

30-day free trial through the Atlassian Marketplace. Jira Cloud. English and French.

How the move goes

Connect, check, import, then switch when you're ready

Connecting only reads from Tempo. Nothing changes in Tempo or in Jira.

Connect Tempo

In Tempo's settings, create an API token with read access to accounts, work attributes, worklogs and teams, and paste it in LogQuill. It is stored encrypted.

Check what would be imported

Every account, work attribute and team, each with a choice: merge into one you already have, import as new, or leave it out.

Import

Tempo's worklogs come in with the Jira sync, each under the person who logged it, with its account, billable hours and attributes.

Run both, then disconnect

While Tempo is connected, its new worklogs keep coming in. Disconnect when you're ready: what was imported stays and becomes editable.

Step by step, with what each choice does: import from Tempo.

What carries over

Your data, in its LogQuill shape

Worklogs

Under the person who logged them, not Tempo's app account, so they count in each person's timesheet.

Accounts

With their customer, lead, billable setting and projects, including the projects where the account is the default.

Work attributes

As worklog fields with their options, or as the worklog's account. Attributes whose values come from outside Tempo are left out.

Teams

Their description, lead as leader, today's members and linked spaces as projects. Roles, commitments, programs and permissions are left out.

Tempo's timesheet approvals aren't imported: approvals in LogQuill start from your first period. Run Import again at any time to bring what changed in Tempo since.

After the move

What your team gets with LogQuill

Timesheets with approval

Periods of one to four weeks, handed in to team leaders, approved or sent back, then locked. Jira timesheets

Absences and leave balances

Approval chains per team, HR by email without a Jira account, allowances with carry-over. Leave management

Accounts and billable hours

Accounts with customers and leads, a default per project, billable hours on each worklog, and custom worklog fields.

Reports finance can use

By person, team, project, account or custom field, saved and shared, exported to Excel or CSV.

A public API and an MCP server

Per-person keys with scopes and an expiry date, and an MCP server so AI assistants can read and log time behind the same checks.

English and French

Per person, or following their Jira language. Built on Atlassian Forge for Jira Cloud.

Questions

Questions people ask

Everything else is in the documentation.

Tempo saves its worklogs in Jira under its own app account, not the person's, so on their own they can't count in anyone's timesheet. Connecting Tempo lets LogQuill find each worklog's real author.

No. LogQuill only reads from Tempo, with a token you create and can remove at any time. LogQuill keeps it encrypted and never shows it again.

Yes. While both apps are installed, worklogs made in either stay in step through Jira. Worklogs that came from Tempo stay read-only in LogQuill while Tempo is connected, as Tempo owns them.

The worklogs already imported stay, and can be edited in LogQuill from then on. New worklogs logged in Tempo stop coming in.

No. LogQuill is an independent app for Jira Cloud, not affiliated with Tempo.

Also in LogQuill

Tempo is a trademark of its owner. LogQuill is not affiliated with, endorsed by or sponsored by Tempo.

Give your team a timesheet they will actually fill in

Install from the Atlassian Marketplace, set it up in an afternoon, and try it free for 30 days next to whatever you use today.

Get LogQuill for Jira

See the first setup guide

Rather see it first? Book a 30-minute demo.