The Jira integration allows you to connect your project work in Jira with time tracking in timr.
If your teams manage their work in Jira but track time and budgets in timr, the integration helps you avoid duplicate work: Jira issues are automatically created as tasks in timr. You can define per project which issue types and statuses should be synchronized and how tasks in timr should be set up (bookable, billable, etc.).
The synchronization works in one direction only. Times or budgets are currently not written back to Jira.
Overview of features
Automatic import of Jira issues
The integration creates a task in timr for each synchronized issue. You always have an overview of all tickets and can book time directly on the corresponding task.Custom sync rules
Define from which Jira project issues should be imported, which status they must have, and which issue types should be included. This ensures that only relevant tasks appear in timr.Configurable task properties
Define whether tasks are bookable or billable and whether a note is required for bookings. These settings can be defined globally or per issue type.Flexible project configurations
You can create multiple configurations to connect different Jira projects with different rules. You can adjust configurations at any time.One-way sync
Currently, only issues from Jira are synchronized to timr. Budgets and booked times are not yet transferred to Jira. These features are on the roadmap.
Table of contents
2.1 Simple mode
2.2 Advanced mode
3. Starting the synchronization
4. Editing or deleting a configuration
1. Setting up the integration
Step 1: Enable the integration
If the integration feature is not yet enabled, contact timr support first. Only administrators can add integrations.
Step 2: Add the integration in timr
Log in to timr as an administrator and go to Administration → Settings → Integrations.
Click Add and select Jira Integration. A new browser tab opens with the timr app in the Atlassian Marketplace.
Step 3: Install the timr app in Jira
On the Marketplace page, click on „Install via Atlassian Marketplace“. The installation runs in the background.
Step 4: Connect timr and Jira
In Jira, open the settings menu (gear icon in the top right) and select Manage apps.
Find timr Configuration and click Connect.
Enter your timr identifier and your login credentials to connect your timr account with Jira.
After saving, the connection is established.
Step 5: Prepare the first synchronization
After installation and connection, the integration is ready to use. You can now create configurations for individual Jira projects.
After saving the first configuration, the sync will automatically start (see section 3. Starting the Synchronization).
2. Configuring a project
Configurations define which issues from a Jira project are created as tasks in timr and how these tasks are set up. You can create multiple configurations, for example to sync different projects or teams with different rules.
To create a new configuration, open timr Configuration and click Add Configuration.
Then follow these steps:
Step 1: Select project
Choose the Jira project from which issues should be imported.
Step 2: Assign timr task
Select an existing task in timr under which the synchronized issues will be created as subtasks. This task acts as a container for all project tickets.
Step 3: Filter by status
Define which issue statuses should be synchronized (e.g. “In Progress”, “To Do”, “Code Review”).
Tasks only appear in timr if the issue has one of the selected statuses.
If an issue moves to “Backlog” or “Done”, the corresponding task is hidden in timr.
Step 4: Select mode
Choose between simple mode and advanced mode.
2.1 Simple mode
In simple mode, all issue types of a project are synchronized. You define task properties once:
Task properties
Decide whether tasks should be bookable and/or billable and whether a note is required. These settings apply to all issue types.
Use this mode to quickly import all tickets from a project.
2.2 Advanced mode
In advanced mode, you can control in detail which issue types are imported and how tasks are configured.
All or specific issue types
Choose whether to sync all issue types or only selected ones.
Global settings
If you sync all types, define global settings for bookable, billable, and note requirement. These apply to all types without specific rules.
Custom rules
Define specific settings for individual issue types. For example: “Bug tickets should not be billable.”
These rules override the global settings.
Click Preview to review your configuration. If everything is correct, save the configuration.
3. Starting the synchronization
Synchronization starts automatically when you save the configuration.
The first import may take a few minutes depending on the number of issues. timr creates a task for each synchronized issue and displays it under the selected timr task.
After the sync is complete, your employees can book time on these tasks. If an issue no longer matches the selected status (e.g. it is set to “Done”), the task is automatically hidden in timr.
To run a manual sync, follow these steps:
Go back to timr and open Administration → Settings → Integrations.
In the Jira integration, click Manual synchronization of Jira tasks
4. Editing or deleting a configuration
Configurations are managed in Jira only.
Edit: Open timr Configuration in Jira.
You can change the project, adjust status filters, or update task properties.Add configuration: Click Add Configuration to sync additional projects.
Delete: Remove configurations you no longer need. This does not delete tasks. It only stops synchronization.
As soon as changes to the configurations are saved, timr will be automatically updated.
5. Limitations and outlook
One-way synchronization: Only issues are synced from Jira to timr. Bookings, notes, and budgets are not sent back to Jira.
Budget sync: The “Estimated Time” from Jira is not yet transferred as a budget to timr. This feature is on the roadmap.
Sync scope: Only the issue title and issue type are transferred. Labels, comments, and attachments are not imported.
These limitations may change in future versions. We will keep you informed and welcome your feedback.
Comments
0 comments
Article is closed for comments.