Skip to main content

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:

SystemExample Prefix
Jira Cloudhttps://yourcompany.atlassian.net/browse/
Jira Serverhttps://jira.company.com/browse/
GitHub Issueshttps://github.com/org/repo/issues/
GitLab Issueshttps://gitlab.com/org/repo/-/issues/
Linearhttps://linear.app/team/issue/
Asanahttps://app.asana.com/0/project/

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

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