LeDuc Systems

Import your own time

The Import tab on the Saguaro Hours page brings in time you recorded somewhere else: a CSV from another time tracker or a spreadsheet, or the events of a calendar file. Every user has it.

Each row you import becomes a normal Jira worklog written as you. That is why only your own time can be imported: Jira does not let an app log work in someone else's name, so a Jira administrator cannot import other people's time with it. (Moving a whole team from Tempo is a different job: see moving from tempo.)

Files are read in your browser. They are not uploaded or stored, and the app makes no calls outside Jira.

A worklog CSV

Any CSV with one time entry per line, for example an export of Clockwork, Toggl or Harvest, or your own spreadsheet. Semicolon and tab separated files work too; Excel files must be saved as CSV first. Up to 2,000 rows at a time.

  1. Choose the file. The columns are matched by their names; check them and change any that are wrong:
  2. Issue key (required): a column with the key, or with text that contains one, such as a Toggl description "SAM-12 fix login". The first key in the text is used.
  3. Date (required): 2026-11-03, 03/11/2026, 3 Nov 2026 and similar. If the file does not settle day and month order, you choose it.
  4. Duration (required): read as hours (1.5, 1:30, 1:30:00, 1h 30m, 90m), minutes or seconds, as you choose. It is rounded to the minute, as Jira keeps minutes.
  5. Start time (optional): when the work started. Without it a worklog starts at 09:00, as in the grid.
  6. Description (optional): becomes the worklog comment.
  7. Billable (optional): yes / no / true / false, or a number above zero. Without it the site's billable default applies.
  8. Person (optional): a name, email address or account id. Rows of anyone but you are refused. Blank counts as you.
  9. The preview shows the first rows as they will be read, with any problem.
  10. Check reads Jira and writes nothing. Each row is Ready, or Skipped with the reason:
  11. the issue does not exist or you cannot see it;
  12. the day is in your submitted or approved timesheet (locked);
  13. a duplicate: you already have a worklog on that issue and day with the same duration (to the minute) and description, or an earlier row of the file is the same. Importing the same file again therefore creates nothing new.
  14. Rows that could not be read (no issue key, a date or duration not understood, someone else's time) are listed as Unreadable.
  15. Import writes the ready rows one by one. Stop ends the run between rows; the rows already written stay. The locks are checked once more just before writing. A row that fails is reported and the next one is tried.
  16. Download the check or the result as CSV, with the Jira worklog id of each row written.

A calendar file (.ics)

An .ics file exported from Google Calendar, Outlook or Apple Calendar. There is no connection to your calendar account.

  1. Choose the file and a week (Prev, Next, This week). The week's events are listed in your Jira time zone with their length.
  2. Tick the events you worked on. For each, check the hours, enter the issue key and, if you like, change the description (the event title by default). An all-day event has no length: type the hours.
  3. Check and Import work as for a CSV, including the duplicate and lock checks.
  4. The issue you chose for an event title is remembered for you, so a weekly meeting gets its issue filled in next time. A title that contains an issue key gets that key. "Forget them" deletes what was remembered. Only you can see or change your remembered titles; they are deleted if your Atlassian account is closed.

What is read: event title, start and end (or duration), time zone, repeat rule, exceptions and moved occurrences. Times in a named time zone, including the Windows names Outlook writes for common zones, are converted to your Jira time zone; a zone the browser does not know is read in your own zone, with a warning. Repeating events (daily, weekly on chosen days, monthly on the same date, yearly, with an interval, count or end date) are listed in the week they fall in. Rules such as "the first Tuesday of the month" are not expanded: only their first occurrence is listed, with a warning. Cancelled events are left out.

Remaining estimate and billable

Imported worklogs follow the site's rules like any other worklog written in Saguaro Hours: the billable default for rows without a billable value, and the remaining estimate rule (weekly-timesheet.md). The worklogs can be changed or deleted afterwards in the grid, the Log work panel or Jira.