Integrations

Elastic Time integrates with external tools for issue tracking, time logging, and data import/export.

Jira Integration

Warning: Always check scripts before you run them. If you are unsure about this feature, we recommend that you don’t use it.

Jira Worklogs Script

Export your time entries as Jira worklogs using a browser script:

1. Go to Reports
2. Filter to the desired date range and project
3. Click “Jira Worklogs” to copy the script
4. Open your Jira instance in a browser
5. Open Developer Tools (F12)
6. Go to the Console tab
7. Paste and run the script

How It Works

• The script uses your existing Jira session for authentication
• No API tokens or credentials needed
• Activities are matched to Jira issues by tag (the tag should be the issue key)
• Time is logged to each issue

Requirements

• You must be logged into Jira in the same browser
• Tags must match Jira issue keys (e.g., PROJ-123)
• Your Jira user must have permission to log work

Aggregation

The script aggregates time by issue and day:

• Multiple activities for PROJ-123 on the same day become one worklog
• The total time is summed
• Descriptions are combined

Jira Comments Script

Import activity notes as Jira comments:

1. Go to Reports
2. Filter your activities
3. Click “Jira Comments” to copy the script
4. Run in your browser console while on Jira

Differences from Worklogs

• Only includes activities with notes
• One comment per activity (not aggregated)
• Comments include the activity description and note
• Useful for documenting work performed

Tempo CSV Export

For Jira Server/Data Center with Tempo Timesheets:

1. Go to Reports
2. Filter your activities
3. Click “Tempo CSV” to download
4. Import the CSV into Tempo

CSV Format

The export creates a Tempo-compatible format:

• Issue key (from tags)
• Date
• Hours (aggregated by issue and day)
• Description

Ticket System Linking

Link activity tags to any URL-based issue tracker.

Configuration

1. Go to your client’s detail page
2. Set the Ticket URL Prefix
3. Save

Supported Systems

Any system with URL-based issue viewing:

Usage

When you export to HTML format:

• Tags become clickable links
• Clicking a tag opens the issue in a new tab
• Makes it easy to reference original tickets

Example: Tag PROJ-123 with prefix https://jira.company.com/browse/ links to https://jira.company.com/browse/PROJ-123

JSON Account Export

The Export everything (JSON) button in Preferences downloads a complete copy of an account as one JSON file. It is the format Alba Ticket imports when an account moves there, and it is documented here so that any other application can read it too. Every entity carries the identifiers it has in Elastic Time, so a reader can relate rows to each other and recognise the same row again in a later export.

Getting the file

1. Go to Preferences
2. Find the Export Activities section
3. Click “Export everything (JSON)”

The download is served as application/json and named elastictime-<email>-<date>.json, for example elastictime-jane@example.com-2026-09-30.json. Only the signed-in user’s own account is exported; a session is required.

Conventions

Top-level structure

{
  "format": "elastic-time-export",
  "version": 1,
  "exported_at": "2026-09-30T12:00:00.000Z",
  "user": { ... },
  "colleagues": [ ... ],
  "clients": [ ... ],
  "phases": [ ... ],
  "activities": [ ... ],
  "counts": { ... }
}

user

The account owner. This is the only object without updated_at and deleted_at.

colleagues[]

A colleague row links two users, or records an invitation that has not been accepted yet. Rows where the owner is either side are exported.

clients[]

clients[].team_members[]

Users other than the owner who may log time on this client’s projects.

clients[].contracts[]

clients[].tag_categories[]

clients[].projects[]

phases[]

activities[]

Time entries. The owner’s own entries are all included, whatever project they belong to. Entries logged by other users are included when they belong to a project of one of the owner’s clients, so the export holds everything the owner can see in reports.

counts

The number of rows of each entity in the file, deleted rows included, so an importer can check it read the whole file. projects, contracts, tag_categories and team_members are totals across all clients.

{
  "clients": 2,
  "projects": 3,
  "contracts": 2,
  "tag_categories": 1,
  "team_members": 2,
  "phases": 2,
  "activities": 5,
  "colleagues": 1
}

Example

A small account with one client, one team member and two activities:

{
  "format": "elastic-time-export",
  "version": 1,
  "exported_at": "2026-09-30T12:00:00.000Z",
  "user": {
    "id": "u_jane",
    "name": "Jane Doe",
    "email": "jane@example.com",
    "company_name": "Doe Consulting",
    "company_address": "1 High Street\nLondon",
    "company_phone": null,
    "company_email": "billing@example.com",
    "invoice_footer": "Payment within 30 days",
    "tax_label": "VAT",
    "tax_rate": "20.00",
    "billing_currency": "GBP",
    "created_at": "2024-01-01T00:00:00.000Z"
  },
  "colleagues": [
    {
      "id": "col_1",
      "user_id_a": "u_jane",
      "user_a_email": "jane@example.com",
      "user_id_b": "u_sam",
      "user_b_email": "sam@example.com",
      "invite_email": null,
      "status": "accepted",
      "created_at": "2024-02-01T00:00:00.000Z",
      "updated_at": "2024-02-02T00:00:00.000Z",
      "deleted_at": null
    }
  ],
  "clients": [
    {
      "id": "c_acme",
      "name": "ACME",
      "billing_email": "ap@acme.example",
      "billing_address": "1 Main Street",
      "ticket_url_prefix": "https://acme.example/browse/",
      "has_tag_categories": true,
      "default_invoice_label": "Other",
      "created_at": "2024-01-10T00:00:00.000Z",
      "updated_at": "2024-01-10T00:00:00.000Z",
      "deleted_at": null,
      "team_members": [
        {
          "id": "tm_sam",
          "user_id": "u_sam",
          "email": "sam@example.com",
          "created_at": "2024-02-02T00:00:00.000Z",
          "updated_at": "2024-02-02T00:00:00.000Z",
          "deleted_at": null
        }
      ],
      "contracts": [
        {
          "id": "k_retainer",
          "name": "Retainer",
          "reference": "PO-4711",
          "invoice_description": "Consulting",
          "billing_rate": "100.00",
          "currency": "GBP",
          "created_at": "2024-01-10T00:00:00.000Z",
          "updated_at": "2024-01-10T00:00:00.000Z",
          "deleted_at": null
        }
      ],
      "tag_categories": [
        {
          "id": "tc_dev",
          "name": "Development",
          "invoice_label": "Dev",
          "tags": ["dev", "Review"],
          "created_at": "2024-01-10T00:00:00.000Z",
          "updated_at": "2024-01-10T00:00:00.000Z",
          "deleted_at": null
        }
      ],
      "projects": [
        {
          "id": "p_web",
          "name": "Website",
          "created_at": "2024-01-10T00:00:00.000Z",
          "updated_at": "2024-01-10T00:00:00.000Z",
          "deleted_at": null
        }
      ]
    }
  ],
  "phases": [
    {
      "id": "ph_sep",
      "name": "September",
      "user_id": "u_jane",
      "contract_id": "k_retainer",
      "project_id": "p_web",
      "start_date": "2026-09-01",
      "end_date": "2026-09-30",
      "billing_rate": null,
      "max_days_available": 10,
      "hours_per_day": "8.00",
      "created_at": "2026-08-20T00:00:00.000Z",
      "updated_at": "2026-08-20T00:00:00.000Z",
      "deleted_at": null
    }
  ],
  "activities": [
    {
      "id": "a_1",
      "user_id": "u_jane",
      "user_email": "jane@example.com",
      "start_time": "2026-09-01T07:00:00.000Z",
      "end_time": "2026-09-01T09:30:00.000Z",
      "description": "Fix the checkout bug",
      "note": "Found it in the flex gap",
      "tags": ["Dev", "WEB-1"],
      "project_id": "p_web",
      "locked_at": "2026-09-05T10:00:00.000Z",
      "locked_by_user_id": "u_jane",
      "locked_by_email": "jane@example.com",
      "created_at": "2026-09-01T09:31:00.000Z",
      "updated_at": "2026-09-05T10:00:00.000Z",
      "deleted_at": null
    },
    {
      "id": "a_2",
      "user_id": "u_sam",
      "user_email": "sam@example.com",
      "start_time": "2026-09-02T08:00:00.000Z",
      "end_time": "2026-09-02T09:00:00.000Z",
      "description": "Review the fix",
      "note": null,
      "tags": ["review"],
      "project_id": "p_web",
      "locked_at": null,
      "locked_by_user_id": null,
      "locked_by_email": null,
      "created_at": "2026-09-02T09:01:00.000Z",
      "updated_at": "2026-09-02T09:01:00.000Z",
      "deleted_at": null
    }
  ],
  "counts": {
    "clients": 1,
    "projects": 1,
    "contracts": 1,
    "tag_categories": 1,
    "team_members": 1,
    "phases": 1,
    "activities": 2,
    "colleagues": 1
  }
}

Reading the file

• Check format and version first, and refuse a file whose values differ from those you support
• Decide whether deleted rows matter to you; if not, drop every row whose deleted_at is set, and drop nested rows of a deleted client too
• Resolve project_id against clients[].projects[] and contract_id against clients[].contracts[]; a project of a deleted client may still be referenced by live activities
• Match people by email rather than id if you are merging with data from elsewhere; user_email and locked_by_email are provided for this
• Compare what you read with counts to make sure nothing was skipped

CSV Import/Export

Exporting Data

Export your activities for backup or analysis:

1. Go to Preferences
2. Find the Export section
3. Select the year to export
4. Click “Download CSV”

The export includes:

• All activity fields
• Full descriptions and notes
• Tags (comma-separated)
• Project and client information

Importing Data

Import activities from a CSV file:

1. Go to Preferences
2. Find the Import section
3. Select your CSV file
4. Configure import options
5. Click “Import”

Import Options

• Timezone - How to interpret times without timezone info (defaults to your current timezone)

CSV Format

The import accepts flexible date/time formats:

• ISO 8601: 2024-01-15T09:00:00
• Date and time columns: 2024-01-15 + 09:00
• Various date formats: 01/15/2024, 15-01-2024

Required Columns

• Email - User email address
• Description - Activity description
• Start - Start datetime, or use separate Start date and Start time columns

Optional Columns

• End - End datetime, or use separate End date and End time columns
• Client - Client name
• Project - Project name
• Tags - Comma-separated tags
• Note - Personal note

Example CSV

Email,Start date,Start time,End date,End time,Description,Client,Project,Tags,Note
alice@example.com,2025-01-15,09:00,2025-01-15,10:30,Sprint planning,Acme Corp,Website Redesign,PROJ-101,
alice@example.com,2025-01-15,10:45,2025-01-15,12:30,Implement login form,Acme Corp,Website Redesign,"PROJ-102,frontend",Added validation
bob@example.com,2025-01-15,13:30,2025-01-15,17:00,API development,Acme Corp,Website Redesign,PROJ-103,REST endpoints
alice@example.com,2025-01-16,09:00,2025-01-16,11:00,Code review,Acme Corp,Website Redesign,PROJ-102,
bob@example.com,2025-01-16,11:15,2025-01-16,12:30,Bug fixes,TechStart,Mobile App,"BUG-204,urgent",

Automatic Client & Project Creation

New clients and projects listed in the CSV will be created automatically if they don’t already exist.

Duplicate Detection

The import automatically skips duplicates:

• Activities with matching date, time, and description are skipped
• Prevents accidental double-imports

Team Member Import

Import activities for colleagues by including an email column in your CSV:

1. The colleague must be a team member on the relevant client
2. Each row’s email is matched to the corresponding user
3. Activities are created under that user’s account
4. They can see the imported activities in their reports

Toggl Import

Migrate your time tracking data from Toggl Track to Elastic Time.

Exporting from Toggl

1. Log into Toggl Track
2. Go to Settings (gear icon)
3. Select Data Export
4. Choose Time Entries
5. Enter the year you want to export
6. Click Export Time Entries

The exported CSV imports directly into Elastic Time. To export multiple years of data, repeat the process for each year.

AI Integration

Export data in formats optimized for AI assistants.

Markdown Export

1. Go to Reports
2. Filter your activities
3. Click “AI (Markdown)”

The export organizes activities by:

• Project grouping
• Tag categorization
• Date ordering

Use this with AI assistants to:

• Generate executive summaries
• Create status reports
• Write time entry descriptions

HTML for AI Export

Similar to Markdown but with HTML structure:

1. Go to Reports
2. Click “AI (HTML)”

Some AI tools prefer HTML input for better structure recognition.

Best Practices

Consistent Tagging

For Jira integration to work well:

• Always use exact issue keys as tags (e.g., PROJ-123)
• Be consistent with case (Jira keys are usually uppercase)
• One primary tag per activity for cleaner worklogs