Page Comparison

Assisted Setup

Open Assisted Setup using the search bar. Locate Set up Tempo Integration and launch it by clicking on its name. The setup wizard will then appear. Select Next to continue.

Default Values and Resource Creation

In the next two steps, you need to set the default values that the system will automatically fill in when the Project Journals are created, and whether you want to automatically create new resources when the worklogs are downloaded to Business Central.

Image Removed

Image Added

The value for Resource Default Gen. Product Posting Group can be set to any posting group according to your system needs, e.g. Resource.

Authentication Methods

There are two main authentication methods supported by Jira.

Basic authentication, which is easier to set up, but needs to be renewed every three months. We recommend this method if you are just starting out with our integration and want to check its general functionality and make some test API calls.

Since the Basic method will become deprecated in the near future, we recommend using the OAuth 2.0 bearer token method for day-to-day operations in the production environment. This method is more secure, a slightly more complicated to setup, but the token validity is automatically renewed on a regular basis without you having to think about it.

Tempo, on the other hand, only supports the OAuth 2.0 method.

Based on the options above, we came up with two ways you can authenticate yourself, User Consent Authentication, which corresponds to the OAuth 2.0 authentication method in both Jira and Tempo. If you decide to use this method, please leave both toggle buttons from the screenshot above turned on.

Our second authentication option is called Token Insertion Authentication and is equivalent to Basic authentication in Jira and the OAuth 2.0 method in Tempo. If you decide to use this authentication type, please uncheck both toggle buttons in the screenshot above.

User Consent Authentication (OAuth 2.0)

If you chose this type authentication method, leave both toggle buttons on the third page of the wizard turned on.

Tempo Account field

In this step, you need to get the ID of the Tempo Account field associated with your Jira projects. To get this value, go to any project in Jira, open any task or issue associated with the project, then right-click with your mouse anywhere in it and click the Inspect action from the pop-up menu, which will open developer mode in your browser.

Select the Element Inspection tool in the upper left corner of the developer tools window, then hover over the Tempo Account field, which contains the name of the Tempo account associated with the project. This field is located in the task Details section.

Thanks to the Element Inspection tool you can select a UI element in one part of the screen and see the corresponding HTML code in the developer tools pane. Next, look for the value of the customfield property, which corresponds to a five-digit number.

Redirect URI

The Redirect URI specifies the address to which Jira and Tempo will redirect the browser during the authentication process. The format of the address always consists of your Business Central URL, including your tenant ID and environment name, with /OAuthLanding.htm added at the end.

Jira and Tempo Credentials

In this step, you need to fill in your Jira and Tempo credentials.

The Jira Base URL is the URL of your company in Jira, e.g. https://my-company-jira-url.atlassian.net/.

Your Jira Client ID and Jira Client Secret can be obtained from your Jira developer profile at https://developer.atlassian.com/ .

Go to the developer console and create a new application.

When creating the new app using the Create button in the upper-right corner of the screen, you need to give it a name and specify the OAuth 2.0 integration type.

When you open the app, it brings up a page with a few menu options. In the Overview section, you don't need to configure anything. In the Distribution section, just set the application as private by selecting the Not sharing option.

In the Permissions section, select the Jira API option and for the Jira Platform REST API, check the View Jira issue data and View user profiles permissions using the Edit Scopes button in the upper right of the screen.

In the Authorization section, you need to enter the Callback URL that corresponds to the Redirect URI that you configured in the previous step of the wizard.

In the Settings section, you will find the information you need to complete your Jira Connection setup, your Jira Client ID and Jira Client Secret.

Tip

After all Jira credentials have been successfully generated and entered into the wizard, click the Authorize Jira button in the bottom right corner of the wizard screen. A new window opens in your browser showing the name of the app you created in the previous step and a list of the permissions the application has. To give this application authorization to access your Jira data, click Accept in the bottom right corner of the page. You will know that the action was successful when the message below appears. Once the Jira authorization is done, you can proceed to the next section for connecting to Tempo.

To obtain the Tempo Client ID and Tempo Client Secret, go to your Tempo settings, click Oauth 2.0 Applications in the Data Access section of the left side menu, and create a new application by clicking the button in the upper right corner of the page.

In the next step, a short form will appear where you need to enter the name of the application, the redirect URI address that you already configured in the previous steps of the wizard, and set the Client Type value to Confidential.

In the next step, you’ll get the credentials you need. Now you can copy them to the wizard in the Business Central.

Tip

After both Tempo credentials have been successfully generated and entered into the wizard, click the Authorize Tempo button in the bottom right corner of the wizard screen. You will know that the action was successful when the message below appears. After you have authorized the connection to Jira and Tempo, you can test the connection using our automated tests in the next wizard section API Keys and Permissions Tests.

Token Insertion Authentication (Basic and OAuth 2.0)

If you chose this type authentication method, leave both toggle buttons on the third page of the wizard turned off.

With the Token Insertion Authentication, your setup screen will look like this:

Tempo Account field

The ID of the Tempo Account field associated with your Jira projects can be obtained in the same way as for the User Consent Authentication. You can find the detailed instructions in the corresponding part of the documentation.

Jira and Tempo Credentials

Next, you can continue to the Jira Connection Setup.

The Jira Base URL is the URL of your company in Jira, e.g. https://my-company-jira-url.atlassian.net/.

The Jira API Email is the email of the Jira user account through which the integration will be established. If you're not sure what level of permissions your Jira user should have, please see our general recommendations at the beginning of the main Tempo Integration documentation.

To obtain the Jira API Key, go to your Jira environment and look for the Atlassian account settings, accessible through the gear in the upper right corner of the main horizontal menu.

Once you're in the account settings, look for the Security tab in the horizontal menu at the top of the page, then look for API tokens. Create new token using the Create API token button.

In the next step, you will be prompted to enter and confirm the token name. On the following screen, you will be given your Jira API Key, which you can copy to the wizard in Business Central.

After the Jira Connection is set, you can proceed to the Tempo Connection section.

To generate your Tempo Access Token, go to the Tempo settings, click API Integration in the Data Access section of the left side menu, and create a new token by clicking the button in the upper right corner of the page. In the form that appears, enter the name of your token.

The expiration period can be typically set to 30, 90, or 365 days.

Next, select Custom Access from the access options. In the permission options that appear below, check all the View permissions and leave the Manage permissions unchecked since the integration won't be editing any data. Once your permissions are set, confirm your selection.

Once your settings are confirmed, you will receive your Tempo Access Token, which you can copy to the wizard in Business Central.

After you have entered all Jira and Tempo credentials, you can test the connection using our automated tests in the next section, API Keys and Permissions Tests.

API Keys and Permissions Tests

In this section, you will be asked to enter a key for one of your existing Jira projects and a key for one of the Tempo accounts you use to log time on tasks within that project. Then use the Test API Keys action in the bottom right corner.

Info
Jira Project Keys If you’re not sure where to find this type of information, the easiest way is to click on the Projects drop-down menu in the main Jira navigation bar, and then click View all projects. Your project keys will be displayed in the column next to the name of each project. Tempo Account Keys Tempo account keys can be easily found in the Tempo side menu under Accounts.

The tests allow you to verify that the integration can access the project and Tempo account you entered and download the information it needs. At the same time you can see if your Jira user has enough permissions for the integration to work correctly.

If the tests are successful, the corresponding line will be filled with a green OK. In case of an error, you will be provided with the details of the given API call.

The tests are the same for both authentications types.

Job Queue Setup

As your worklogs will be automatically downloaded through a job queue entry, in this part of the wizard you can predefine the date until which the previous month's period will remain open, so you can adjust the period length according to your company needs.

Using the example in the screenshot below, the worklogs for the previous month can be downloaded until the 5th day of the current month, but if the system downloads the worklogs after that date, only the current month records will be downloaded to your Business Central.

In the next step, you will be asked to create a job queue entry to automatically download your worklogs from Tempo. When you click the Create Job Queue action in the bottom right corner, the system creates a new job queue entry for you, and all you need to do is set the status of the entry to Ready.

If for some reason there is already a job queue in the system (for example, if you are switching authentication methods), the system will notify you.

Here's an example of the job queue that our integration will create for you. It's a standard Business Central job queue entry. If you want to know more details about it, please refer to the corresponding section of the main documentation.