Admin Configuration for Tempo Importer

The Admin tab in Tempo Importer is organized into two sub-tabs: Connection Settings and Application Settings. Use Connection Settings to configure how data is fetched and imported; use Application Settings for notifications, logs, and application management.

Under the Admin tab, you can select the Object Types you want to import. By default, all Object Types are enabled. Review and disable any that do not align with your organization's use cases.

• Viewing Object Types: Navigate to Object Types and select Show Object Types.

Open Open

• Editing Object Types: Navigate to Object Types and select Change Object Types.

Open

This setting lets you customize how data is fetched from Tempo APIs. While the default configuration works well for most users, adjusting these parameters may improve import speed.

However, doing so could also cause memory or runtime issues, particularly when handling a high volume of worklogs. For organizations with more than 2,000 Tempo users, we're excited to work with you directly to optimize these settings and better suit your requirements.

You can update the settings by selecting Show Settings.

Open Open

Worklog settings are used to adjust the import process and influence which worklog data is included. You can retrieve worklogs either updated recently, recorded within a specific date range, or captured during a recent period.

This is the default setting and imports workload data that have been recently updated, regardless of their creation date.

Open

This configuration is intended for importing data within a defined date range and should be used solely for pre-existing data imports. Once the process is complete, it's crucial to revert the application to its original settings for "Updated/Recorded recently." Neglecting to do so may lead to duplicate data imports, regardless of whether imports occur daily or hourly.

Open

Workload data created recently will be imported through this process. However, any updated data not created within this timeframe will be excluded from the import.

Open

Scope settings allow you to define whether the application's import in Accounts is restricted to a specific scope. By enabling this setting, you can limit the data imported to align with your requirements, while disabling it ensures no such restrictions are applied.

Open

This setting enriches the Jira Projects object type by looking up each imported Jira Project's Name and Key from Jira and adding them as attributes during import.

• Enable Project Name and Key in Jira Projects — Jira Project Name and Key are fetched from Jira and stored as attributes on each Jira Projects object.

• Disable Project Name and Key in Jira Projects — No additional Jira lookup is performed (default behavior).

Check the current import execution in real time. You can also cancel a running import from this view if needed.

Review past import runs with details including status, triggered by, result, type, start time, end time, and duration.

Configure automatic notifications to alert you when something goes wrong during an import. This helps you stay informed about failures without having to manually check Import Status each time.

View a full audit trail of configuration changes and import events. Audit Logs are useful for compliance tracking and understanding the history of changes made to the application.

Access detailed technical logs for troubleshooting import issues. Debug Logs provide low-level information about the import process to help diagnose problems when standard error messages are not enough.

Use this option to reset the application to its initial state, clearing all configuration settings and import history. This is useful when you need to start fresh with a new configuration.