Bastion Helix for Jira
Guide

Moving from Tempo Timesheets: what comes across, and how

Switching time-tracking apps is only possible if your history comes with you. Here is exactly what the import reads from a Tempo export, and what it does with each row.

·2 min read·Time tracking
A weekly timesheet fills in while a timer runs

Why an export, not an API

Tempo keeps its own data on its own servers. Reading it through Tempo's API would mean your hours leaving Atlassian for a Bastion Helix server, which is the one thing this app is built never to do. So the import works from a CSV file you export from Tempo and choose in your browser.

Before you import

  • Install Bastion Helix and let its first sync of your worklogs finish. The import matches Tempo rows onto the Jira worklogs Tempo created, so those need to be there first.
  • Export your logged time from Tempo as CSV, not Excel. If you choose an .xlsx file, the import asks for the CSV instead.
  • You need to be a Jira administrator; the import is on the app's admin page.

Which columns are read

The import recognises Tempo's usual column names and lets you correct its guess before anything is written. Three are required.

FieldRecognised headings (examples)
Issue keyIssue Key, Keyrequired
Work dateWork date, Date Started, Started, Daterequired
HoursHours, Time Spent (h), Hours worked, Logged Hoursrequired
Jira worklog IDJira Worklog Id, Worklog Id
WorkerAccount Id, Full name, Worker, Author, User
AccountAccount Key, Account Name, Account
Billed hoursBilled Hours, Billable Hours, Billable
DescriptionWork Description, Description, Comment
CategoryCategory, Work Type, Activity

Dates are read in the common export formats, including 2026-03-14, 2026-03-14 09:00, 14/Mar/26, 14 Mar 2026 and 14.03.2026.

What happens to each row

  1. Checked first. The import reads the whole file and reports what it found before anything is written.
  2. Matched rows keep their Jira worklog. The import adds what Jira has no field for: the account, the billable flag and the work category.
  3. Rows with no Jira worklog behind them are kept as read-only history, with their dates, people and descriptions, so old reports still add up.

After the import

From then on, time logged through the timesheet, the timer or plain Jira is the same kind of worklog, with billable flags, accounts and categories kept by the app alongside it.

Bastion Helix for Jira isn’t on the Marketplace yet. All seven modules are built and running in our own test Jira site. Try the live demos, or leave your email below to hear the day early access opens.

Early access

Be first in when it opens.

One email when early access opens. Nothing else — no newsletter, no drip sequence, and the list isn't shared with anyone.

You're on the list. Talk soon.

Early access members get the first year at launch pricing, locked.
Your address is stored with Resend, the email service that will send that one email.

Recorded from the live demo on this site: the module’s real code running on sample data. Nothing is edited apart from the title cards.