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 kinds of use cases, from requirements and test case management to agile software development.

What can I import from Jira?

The user will be able to choose to map between Toggl Track entities (description, Project, Task, Tag) and Jira entities (Story, Task, Bug, Sub-Task, and Epic).

Users can set up only one Jira site per one Toggl Track workspace at a time. 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 the 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 next few screens.

Authorize Jira Sync

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

The first step is about connecting data, where you will see your Atlassian URL and a button to add a connection. After you click on "+ Add a connection" the following options will appear allowing you to configure how you want your Jira data to be mapped with your Toggl Track data:

Click to add a link to see the available options:

You can use the search box to find a Jira object or pick one from the list by clicking on it. After you are done, you'll be able to see the connections you made and edit or delete them if needed:

To save the configuration click on the "Save" button in the lower-right corner of the setup view. After you save your configuration you will be asked to choose if you want to add a prefix or a suffix to synced entities from Jira:

After you are done with adding a prefix or a suffix (which is optional) you can click on "continue to handle duplicates" which takes you to the next step where you can choose what happens with duplicates:

After you are done with this step you can click on "Continue to preview your setup". If you need to edit something in the previous step related to connecting data you can go back by clicking on "Previous step". If you continue to preview the setup you will see the following preview:

Again, if you want to go back click on the "Previous step" button to make any changes to previous configuration steps If you are happy with the setup you can click on the "Finish setup and begin syncing" which will save the configuration and start the sync.

Once everything is setup, you will see the following screen showing the setup.

The sync happens periodically, but, you can always click on the "Sync" button to trigger a sync manually. Under that button, you will see the date and time of your last sync. You also have the option to Pause the sync, edit or remove the Jira integration entirely.

Jira Sync Settings

You can also reach this screen any time from the Integrations page by clicking the Settings button next to the Jira Integration.

Sync is setup

Mapping Jira entities to Tasks in Toggl Track

Users must select from within their Jira issue types the ones that have the property of being a sub-task. For example, for a default new Jira site, you may usually find these issue types already predefined: Story, Task, Bug, Subtask, and Epic; from which only the Subtask one has the property of being a sub-task.

In Toggl Track, Tasks are nested within Projects, so in order to sync foreign entities from Jira to be imported as Tasks in your Track workspace, you need a parent-child hierarchy on the Jira side. For this use case, you could map:

  • Toggl Track Tasks to Jira Sub-Task entities

  • Toggl Track Projects with Jira Tasks

With this setup every time you create a Sub-Task named "X" for a given Task named "Y" on Jira, you would sync a Toggl Track project named "Y" and within it a task called "X".

For the time being, we do not support custom Jira hierarchies.

Important notes:

  • If you experience issues with 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

  • If you get an error while enabling the integration it is possible you are 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 perhaps 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?