...
In the next two steps, you need to set the default values that the system will automatically fill in when the Job Project Journals are created, and whether you want to automatically create new resources when the worklogs are downloaded to Business Central.
...
| Info |
|---|
We recommend that you set up your Job Project Journal Template only once, for example to a template named JobProject, and not further change it during use of the integration. If a worklog with this template has already been downloaded to the job project journals and then posted, it will no longer be possible to change this value. If a worklog has only been downloaded and not posted, it is still possible to delete the worklog and change the template in the settings. |
...
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 its 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 bearer token method.
Based on the options above, we came up with two main 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.
...
| Info |
|---|
Both authentication options are described in detail in the sections below. For the sake of this documentation, the available authentication methods are described in pairs, but you can combine them according to your needs. Just make sure that all required credentials are filled in when switching from one method to another. When switching from Token Insertion Authentication to User Consent Authentication, also make sure to use both Authorize Tempo and Authorize Jira functions. |
| Note |
|---|
In case you install our solution, set it to OAuth 2.0 authentication and then leave it unused for several months, it may happen that the API tokens will not be automatically renewed after such a long delay, which means that you will not be able to download new worklogs. In such a situation, simply use our Authorize Tempo and Authorize Jira actions, which are available in both the Assisted Setup Wizard and the Tempo Integration Settings. |
...
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 is a five-digit number.
...
| Tip |
|---|
As this is not the only customfield property present in the code, make sure that your Element Inspection tool is focused on the correct area of the screen. If you can't find the Inspect action, you may need to check how the developer console is named in your browser, as it can vary. However, this feature is available in all major browsers. |
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.
...
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.
...
| 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. |
...
| 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.  |
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, click on the three dots on the line below and the field number will fill itself in.
...
| Note |
|---|
Please note, during the setup of all the steps on this page, you must follow the order in which the sections follow each other and select the appropriate actions for authorization, otherwise your Tempo account ID will not be filled in correctly.
|
After you have filled in the Tempo account ID, 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)
...
With the Token Insertion Authentication, your setup screen will look like this:
po úpravě vyměň screenshot
...
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 SetupYou can now proceed to set up your connection to Jira.
The Jira Base URL is the URL of your company in Jira, e.g. https://my-company-jira-url.atlassian.net/.
...
Once your settings are confirmed, you will receive your Tempo Access Token, which you can copy to the wizard in Business Central.
| Info |
|---|
If you need to renew the validity of your Tempo token, you can do so by using the Regenerate function, accessible from the three-dot menu on the token line, or you can create a new token. |
...
Tempo Account field
The Tempo Account field ID associated with Jira projects can be obtained in the same way as for user consent authentication. For detailed instructions, see the relevant section of the documentation.
After you have entered all Jira and Tempo credentialsfilled in the Tempo account ID, you can test the connection using our automated tests in the next section, API Keys and Permissions Tests.
...
| Info |
|---|
Jira Project KeysIf 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 KeysTempo 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.
...