Jira Sync

Sync your Jira data with your Toggl Track account to see the time spent on each Jira issue

Veljko avatar
Written by Veljko
Updated over a week ago

Toggl Track natively syncs Jira issues via our Integrations page. Jira Sync is available for Premium users.

Note: This integration only supports Cloud Jira.

About Jira

Jira Software is part of a family of products designed to help teams of all types manage work. Originally, Jira was designed as a bug and issue tracker. But today, Jira has evolved into a powerful work management tool for all use cases, from requirements and test case management to agile software development.

What can I import from Jira?

First, it’s important to note that the integration currently functions one way: you can only import your data from Jira to Track, and it’s currently not possible to export data from Track to Jira. However, if you would find this beneficial, please don’t hesitate to reach out so that our team knows to focus on it.

Also, note that we will not import any users and thus cannot retain the existing relationships between users and entities you have set up in Jira.

You can map Toggl Track entities ( Project, Task, Tag, Client) with Jira entities (Project, Issue, Label), and filter by Project Category, use queries or JQL, Status or Issue Type (Epic, Story, Task, Subtask, Bug, etc.), just how you’ve set them up.

Users can set up only one Jira site per Toggl Track workspace. If you have more sites, you’ll need to delete the existing one and add a new one or create a new workspace for each Jira site.

How can I enable Jira Sync for my workspace?

Go to Integrations > Native Integrations and click on the “Get Started” button next to the Jira integration to start setting up the sync:

Setup Jira Sync

You will have to log into your Atlassian account and then choose the Jira domain the data will be synced from on the following screens.

Authorize Jira Sync

Once the authorization is complete, you will be redirected to Toggl Track's integration page and see the following 3-step process.

To start syncing Jira entities into Toggl Track, you must first choose to set the integration up for the whole workspace or only some users/a user group. When you choose the former, note that all the projects will be imported as public. To make them private, navigate to Project Settings.

To start mapping, you must first assess the most logical way to set up your Toggl Track workspace. You can map Toggl Track entities ( Project, Task, Tag, Client) and Jira entities (Project, Issue, Label).

Mapping Jira entities to Tasks in Toggl Track

To ensure you import only tasks relevant to you right now, you can choose filters. We have different options based on what you have chosen to map Track entities with.

If you’ve chosen issues, you can select between multiple options and map multiple Jira entities into one Track entity.

For filtering issues, you can also use JQL for some more complex filtering needs.

The same applies to projects: you can use multiple ways to filter the data import, including different queries.

Handling duplicates

The last thing you need to do before you start mapping is to select how to handle duplicates.

Important notes:

  • If you experience issues connecting to the Jira site, please check if Toggl Track has proper access to Jira or remove the authentication and set it up again.

  • Toggl Track entities will be periodically auto-synced with configured Jira entities.

  • All imported Projects from Jira will be created as Public Projects, but you can manually change the privacy on the Project Settings page.

  • Suppose you get an error while enabling the integration. In that case, you may be trying to import more than 10,000 records from Jira into your Track workspace. In that case, it's best to delete the integration and create a new issue type in Jira, where you can assign issues with tags specifically for importing into Track and enable the integration again.

Need further help? Contact our Support Team via the chat icon in the bottom right corner.

Did this answer your question?