The following text is a complete documentation of the integration between Tempo and Business Central. It consists of three main parts: settings and a detailed description of how to download your worklogs, either manually or automatically.
Settings
To integrate with Tempo, it is necessary to set up the Tempo Integration Settings table, where you will have to enter the integration keys and URLs that will allow Jira and Tempo to connect to Business Central.
To ensure that the integration works properly, you must set up the project journal templates, the resource setup and the corresponding number series.
General Recommendations
To simplify the entire setup process, we recommend using our Tempo Integration Setup Wizard, which can be found in the Assisted Setup section accessible through the search bar. Once all the connection credentials are filled in, our wizard assistant will test if the connection is established correctly and if you have all the required permissions.
Complete documentation for the Tempo Integration assisted setup can be found under this link.
Since the integration requires only one Jira account and one user to connect to, we recommend that the person responsible for setting up the integration be a technical user or an administrator, ideally with access to all projects, issues and worklogs.
In addition to the wizard, you can also use the tooltips, which provide an example of what the system expects you to enter.
Before you start installing the integration, make sure that all users who will use the integration have the permissions to these tables:
Object Type | Object ID | Object Name |
Table Data | 156 | Resource |
Table Data | 169 | Job Ledger Entry |
Table Data | 203 | Res. Ledger Entry |
Table Data | 205 | Resource Unit of Measure |
Table Data | 210 | Job Journal Line |
Table Data | 237 | Job Journal Batch |
Table Data | 240 | Resource Register |
Table Data | 241 | Job Register |
Table Data | 71231910 | Jira Project Key ONP |
Table Data | 71231911 | Tempo Settings ONP |
Table Data | 71231912 | Tempo Worklog Archive ONP |
Table Data | 71231913 | Worklog Period ONP |
Tempo Integration Settings
The integration settings can be found by typing Tempo Integration Settings in the search bar. The settings are divided into several sections.
API Section
This section is already pre-populated with the credentials that you entered into the wizard when setting up the integration. You can skip it and move on to the next section.
Job Queue Section
The following settings can be customized according to the customer's needs:
Download Updated From
When downloading your worklogs automatically using job queue, this field is automatically populated with the date and time of the last successful job queue start and this value does not need to be further adjusted.
The value in this field is not the date on which the worklog was created, but the date it was last modified. The purpose of this functionality is to optimize the download process and avoid downloading worklogs that are already in the system and download only those that have been updated since the last download.
Even if you need to manually download worklogs for a certain period of time, for example because of additional changes in Tempo, we recommend not to change the last download date filled in automatically. When you run the manual worklog download feature, it will download all worklogs you have updated in Tempo since the last download date for the period you have filled in on the feature page.
TIP! We also recommend doing this manual catching up of all updated worklogs at the end of each month, before posting the worklogs from the project journal to the system. This way you can be absolutely sure that your worklogs will be up to date, even if there have been any changes to them after they have been downloaded to Business Central.
The only time it is appropriate to leave the field blank is when creating a new project or adding a new Jira project key to an existing project in Business Central. Once you run the manual download function, this will download all the worklogs for that project for the period you have filled in on the function page.
If you need to manually download a large number of worklogs over a long period of time, you should expect the process to take longer.
For more information about automatic and manual downloading of worklogs, see the corresponding documentation section.
Next Period Starts
Since worklogs are typically approved and closed at the end of the month, this field allows you to set a specific day of the month until which the previous month's period will remain open, so you can adjust the period length according to your company needs.
If you download worklogs after this date, only the current month's worklogs will be downloaded. This applies to the automated download workflow, which means that if you make any changes to previous month’s worklogs in Tempo after the start date of the next period, you will need to download the modified worklogs manually.
Using the example in the screenshot above, the February worklogs can be downloaded until March 5th, but if the system downloads the worklogs after that date, only the March records will be downloaded to your Business Central.
Automatically Load For All Project Tasks
If enabled, all worklogs for all tasks in the project are automatically downloaded when the job queue is started.
If the button is turned off in the settings, the user can specify whether or not to automatically download each project task on the corresponding project card.
On the other hand, if this field is enabled in the settings, the user will not see the option to select whether or not to automatically download the worklogs for a particular task on project cards.
Project Journal Creation Section
Project Journal Template
You can define exactly one template for the project journal. See the project journal template settings section for more information.
Project Journal Editable
When this button is enabled, it indicates that all users will be able to edit project journal lines without restriction.
Project Journal Editable for Project Manager
When enabled, this button specifies that only users who are set as the project managers on the project card can edit project journal lines.
Another way how to restrict undesired changes in the whole integration setup is to allow editing of this table only to selected users via appropriate permissions.
If neither of the options for editing project lines is enabled, users will still be able to delete entire lines or update resource prices in the journals using the action Update Amounts available in the Home tab.
Automatically Create Resources
This toggle specifies if the resources that do not exist in Business Central should be automatically created when worklogs are downloaded.
Resource Default Unit of Measure
The default unit of measure for creating a resource. This value should always be set to Hour as our integration only works with hourly rates.
Resource Default Gen. Product Posting Group
The default general product posting group for creating a resource. This value can be set to any posting group according to your system needs, e.g. Resource.
If the default unit of measure and general product posting group are set, these values are also filled in when a new resource card is created manually.
Merge worklogs when posting
To make the entries that are created by posting worklogs in project journals more clear, it is possible to reduce the number of project or resource entries or project planning lines by merging them.
You can use this field to specify a default rule for projects that have no rule defined on their project card. You can choose from the following options:
Do not merge - When entering worklogs into the system, each line of the project journal will correspond to to exactly one project entry after it's posted.
Merge by resources - When this rule is applied, the posted project journal lines are merged according to each resource loaded into the project journal.
Merge to one G/L account - When this rule is applied, the posted project journal lines are merged into a selected financial account.
Deafult Values for Manual Download
This setting specifies the default settings for the fields on the Load Tempo Worklogs page, which can be used for manual downloading of worklogs. For more information on manual downloading, see this section of the documentation.
Include Not Automatically Loaded
This toggle button can only be enabled if the Automatically Load for All Project Tasks button in the Job Queue section is not enabled (if it is, this toggle button is enabled automatically as well). This way you can be sure that the worklogs for all tasks in the given project are actually downloaded, even if you download them manually.
Project Journal Posting Checks Section
The last section of settings allows you to customize which parameters of your worklogs should be checked when posting them in the project journal.
Check Worklog Status
Checks if the worklog status is set to approved when posting project journal lines.
Check Unit Cost
Checks if the unit cost is other than 0 when posting project journal lines.
Check Unit Price
Checks if the unit price is other than 0 when posting project journal lines.
Check Different Doc. No.
Checks if the document number of all lines is the same when posting project journal lines. The document number series is defined in the format YYYYMM.
Check Doc. No. Posted
Checks for duplicate postings by document and project number in project entries when posting project journal lines.
Project Journal Template Settings
For correct functionality, it is necessary to set up a project journal template and enter it in the corresponding field in the Tempo Integration Settings table.
It is not necessary to manually create the individual project journal batches. The system will create them automatically the first time you download the worklogs or the first time you manually open the project journal from the project card. The name of the project batch is derived from the name of the project itself.
If there are multiple projects with identical values in the first 10 positions of their name, the journal batches are created with a numeric suffix and the full project name is automatically copied into the description field of the journal batch.
Resources Setup
If your resources in Business Central will be created manually, you need to assign a number series for the Resource Numbers field in the Resources Setup table.
The assigned number series should have the manual numbering option enabled, and we recommend filling the resource number (primary key) field on a given resource card with the name of the resource rather than a number. This value will then be displayed in the project journal lines and any related entries/reports.
If the resources in Business Central will be created only through the integration with Tempo, it is not necessary to set up a manual number series for your resources and assign this number series in the Resources Setup table.
Project Card Settings
On the card of each project for which you want to download worklogs, you should always fill in the following fields in the project header section.
Jira Project Keys
Corresponds to the Project Key field in Jira, it is possible to fill in any number of project keys.
If you’re not sure where to find your Jira Project Keys, refer to this part of the documentation.
After clicking in the grey box, a table will appear where you can add new Jira Project Keys either via the +New action or by typing in a new empty line.
And additionally, in the tasks of each project it is necessary to fill in the following fields.
Tempo Account
Corresponds to the Tempo Account key, which can be found either in the given project details in Jira or in Tempo under the Accounts tab.
If you’re not sure where to find your Tempo Account key, refer to this part of the documentation.
Note that this value must be filled in exactly according to the value in Tempo, therefore including the distinction between upper and lower case letters. Without following this rule, the system will not be able to download your worklogs correctly.
When creating new accounts in Tempo, we recommend not to use @, & and # characters for Account Name and Account Key fields, which are supported by our side, but due to Jira's features it can take more time to search and download worklogs.
Project Journal Line Type
The Project Journal Line Type determines whether the data created at posting will be only budget-related (cost side), billing-related (sales side) or if both sides of the process will be created at once.
Depending on how you intend to further work with the data, you can choose from the following line types:
Budget - if you only want to track costs spent on individual projects, for example budgeted costs versus actual costs. At the same time, it will not be possible to create invoices from this type of line.
Billable - if you want to use the lines for tracking the profitability of your projects and also for invoicing your customers.
Budget and billable - if you want to track both the cost and profitability of projects and also create invoices for customers.
Empty - Alternatively, you can leave this field empty and when the project journal is posted, no project planning lines will be created, only project and resource ledger entries.
The system prevents the creation of duplicate records in Business Central by not allowing the same Jira Project Key and Tempo Account to be assigned to multiple project cards. However, the system allows you to assign identical Tempo Accounts to different Jira Project Keys.
Totalling Group
We added this field to the Project Tasks to allow users to summarize cost and sales entries by different Tempo Accounts. In case they need to make additional analysis, lines with the same totalling group will be summarized in reports.
For newly created project tasks, the field is automatically populated with the project name. The user can then change the value according to their needs.
A great example of using the Totalling Group field is to set it as a basic summary filter in Power BI reports if you want to monitor some Tempo Accounts as a single unit.
Worklogs Merging
Optionally, on each project's card, you can specify whether worklogs should be merged according to pre-defined rules when they are posted.
You can choose from the following merging rules:
Do not merge - When entering worklogs into the system, each line of the project journal will correspond to to exactly one project entry after it's posted.
Merge by resources - When this rule is applied, the posted project journal lines are merged according to each resource loaded into the project journal.
Merge to one G/L account - When this rule is applied, the posted project journal lines are merged into a selected financial account.
If no merging option is selected on the project card, the system follows the default rule defined in Tempo Integration Settings.
Resource Card Settings
Resources Created Manually
If the resources are created manually, you need to fill in the fields:
No. - Unique resource ID in Business Central. In this case, it should be filled in with the resource name as mentioned in the corresponding section of the documentation.
Jira Resource Name - Corresponds to the resource name in Jira.
Jira Account ID - Unique resource ID in Jira.
Base Unit of Measure - This value should always be set to Hour as our integration only works with hourly rates.
Gen. Product Posting Group - This value can be set to any posting group according to your system needs, e.g. Resource.
If a resource with a unique name exists in both Business Central and Jira (resource number in Business Central and name in Jira), the system will automatically add the Jira Resource Name and Jira Account ID when manually creating the resource (diacritics must be preserved).
If there are multiple resources with the same name, the system will not be able to automatically assign the Jira Resource Name and Jira Account ID.
If a resource exists in Business Central but does not have a Jira Account ID entered, the system will not recognize it and will create a new resource with a numeric suffix.
Similarly, resources with the same Jira Resource Name will be created.
Resources Created Automatically
If the resources are created automatically when downloading the worklogs from Tempo, you don’t need to fill in any of the fields above, the system will fill them in for you.
The Resource No. in this case corresponds to the resource name in Jira. Both, Base Unit of Measure and General Product Posting Group fields have to be set up in the Tempo Integration Settings, as mentioned in the corresponding section of the documentation.
Price of the Resource
The fields on the resource card related to the resource price should always be filled in.
Unit Cost - Represents the cost of the resource.
Unit Price - Represents the price for which you sell the resource.
If you are used to bill your customers by resource, we also recommend to fill in the General Prod. Posting Group and the VAT Prod. Posting Group.
If a resource has different unit prices according to the projects it is allocated to, it is possible to set this unit price for individual projects using standard Business Central functionality available on project cards.
On the given project card, locate the Prices & Discounts tab and click on the Resource page.
The settings below are valid until Business Central version 25. From version 26, it will be possible to specify different resource prices for individual projects using the Sales Price Lists functionality.
It is then possible to define the sales price of the individual resources for the specific project and, if needed, for the individual tasks of the project.
The sales unit price of a resource for a specific project has a higher priority than the unit price of the resource on the resource card.
Job Queue Entry Settings
To download worklogs automatically, our integration uses the Job Queue Entry feature. It is recommended that you set the download to run every day during the night hours. The job queue will always download all new and updated worklogs. This ensures that the data in Business Central is always up to date and also ensures data consistency between the ERP and Tempo.
Your Job Queue Entry will be automatically pre-set at installation of the integration in one of the steps of our assisted setup wizard and it is not necessary to change it any further. If you want to adjust the settings, the following section describes the recommended configuration.
When setting up the job queue entry you need to fill in the fields below. The first two fields are the most important to run the correct codeunit.
Object Type to Run should be set to Codeunit.
Object ID to Run should be set to 71231913.
Other general fields such as Earliest Start Date/Time or Job Timeout and values in the Recurrence section depend on your personal preferences.
To ensure that the queue runs automatically according to the parameters you set, you must launch it. Since Business Central version 22, only the end user (customer) can start job queues external users (consultants) do not have sufficient permissions to do so.
Each new job queue is set to On Hold. You can start the job queue directly from its entry cardby setting its status to Ready.
User Permissions Settings
Once you assign purchased licenses to selected users in your Microsoft 365 Admin Center (via Billing and Licenses), there is no need to assign or check any specific permissions in Business Central. The full functionality of Tempo Integration will make itself available to users with assigned licenses.
Before you start using the integration, it is recommended that you check that these users have the correct permissions to work with the entities that the integration works with. For example, if your user doesn't have the right to create resources, they won't be able to download worklogs because downloading worklogs also creates new resources.
Automated Download
Automatic download of worklogs is ensured by the corresponding job queue entry. See the relevant part of the documentation for more details.
The download of worklogs also depends on the settings of the Tempo Integration Settings table, specifically the Job Queue section, where it is possible to limit e.g. the period for which worklogs should be downloaded and also whether all worklogs should be downloaded for all tasks of the project. For more information see this section of the documentation.
Viewing Downloaded Worklogs
All downloaded worklogs are displayed to the user in the corresponding Project Journal. The Project Journal can be opened directly from the Project Card in Tasks using the Project drop-down menu and Open Project Journal action.
Project journal lines are automatically filtered by the project number from which the user opened the project journal, and also by the month for which the worklogs were downloaded (Posting Date).
To view all currently downloaded worklogs in the corresponding project journal, simply remove the filter on the posting date.
The posting date filter is linked to the date you set in the Job Queue section in the Tempo Integration settings as the Next Period Starts date. If the Business Central work date has already exceeded the start date of the next period, then the posting date filter in the project journal displays only current month. If the work date has not yet exceeded the next period start date, the posting date filter in the project journal is set to the previous month.
Model situation:
Business Central Work Date is 3/11/2023
Next Period Starts date is set to 5
Posting Date filter in the corresponding project journal is set to 011023..311023.
If the work date was for example 6/11/2023, the posting date filter would be se to 011123..061123.
Project Journal
The project journal contains detailed information about each downloaded worklog. One line of the project journal corresponds to one downloaded worklog.
In order to maintain data consistency between the two systems, the single source of truth rule must be followed. In practice, this means that once the worklogs are downloaded to the appropriate project log in Business Central, the information that comes from Tempo ( resource number, quantity of hours worked, etc.) should no longer change. The only value that can be safely changed is the line description field, or possibly the line discount or dimensions.
If you need to make any changes to a given worklog, the best practice is to delete the line in Business Central, make the modification in Tempo, and then manually download the worklog back into Business Central.
If you want to edit a worklog in the project journal before it is posted, just delete the corresponding line, make the change on the Tempo side and manually download the updated line using the Load Tempo Worklogs action. You can learn more about manual downloading here.
If you need to edit a worklog that has already been posted, you need to reverse the corresponding entry in the project ledger entries, post the line with the opposite value created in the project journal, and then again make the change on the Tempo side and manually download the updated line using the Load Tempo Worklogs action. More information about reversing project entries can be found here.
Line Type - determines whether the expense is billable or not. It can be set automatically on the Project Card in Project Tasks according to the user's needs, more details can be found in Project Card Settings section.
Posting Date - corresponds to the date the worklog was created in Tempo and, at the same time, to the date it will be posted and entered in Business Central.
Worklog Status - determines the current status of the worklog in Tempo.
If the approval process is set up in Tempo, it is recommended that only worklogs with an approved status are entered into the system. Otherwise, it is possible that duplicates will be posted.
Document No. - specifies the number series under which the worklogs will be entered into the project entries in the system. The number series is defined in the format YYYYMM.
Type - specifies the type of account under which the worklog will be entered in the project entries, e.g. resource.
No. - corresponds to the number of the specified account type, e.g. resource number.
Description - corresponds to the name of the number, e.g. the name of the resource.
Description 2 - corresponds to the worklog description in Tempo.
Unit of Measure Code
Quantity
Unit Cost - corresponds to the unit cost of the resource or item set on the relevant card.
Unit Cost (LCY) - corresponds to the unit cost of the resource or item converted into local currency.
Total Cost - this value is calculated from the field Unit Cost multiplied by Quantity.
Total Cost (LCY) - this value is calculated from the field Unit Cost (LCY) multiplied by Quantity.
Unit Price - corresponds to the unit price of the resource or item set on the relevant card.
Line Amount - this value is calculated from the field Unit Price multiplied by Quantity.
Line Discount Amount - specifies the amount of discount applied to the entry on the given line.
Line Discount % - corresponds to the ratio between the logged billable/non-billable time of the resource on the given task in Tempo.
If all the time spent by a given resource on a given task needs to be marked as non-billable, a line discount of 100% can be entered, which will set the amount on the line to zero and in case of invoicing, the price of the line will be 0.
Other optional fields are dimensions which are inherited from the project card.
Entering lines from the project journal into the system
Ideally, worklogs should be entered into the system on a monthly basis for a full previous month after the approval process has been completed in Tempo.
If the unit cost or unit price is not filled in for any of the project journal lines, the system automatically highlights those lines and fields in red.
The user will then need to enter the missing prices for the resource in question directly on the resource card. Once the resource card has been updated, it is possible to add these prices to the already created lines of the project journal using the Update Amounts action in the Home tab.
If you need to apply several different prices to one of your resources within the given month, it is possible to change the prices of the resource on its card, then set a filter on the selected lines that should have a different price and perform the Update Amounts action. The system will update the price only for the selected lines.
Journal entries are entered into the system through the Post action. We always recommend running the Preview Posting function before you actually post.
The accounting function in the project journals is only used to record worklogs in the system, no general ledger entries are created during line posting that would affect the entry in the general ledgers.
Rules for merging worklogs during posting
If you have defined one of the rules for merging worklogs during posting when setting up the integration, either in the Tempo Integration Settings or directly on the individual project cards, you will find a detailed description of how each of the three rules works below.
If you decide to use one of the merging rules, it is recommended to check that all selected project journals lines have the same value in the Line Type column before posting them.
The date at which you then merge the lines should also correspond to the posting date on the invoice if you will subsequently be creating an invoice from the project planning lines.
For more information on general Tempo Integration settings or Project Card settings, see the corresponding sections of the documentation.
Merge by Resources
When this rule is applied, the posted project journal lines are merged according to each resource loaded into the project journal. The user will be prompted to enter the posting date.
In the example below, we can see that there are currently worklogs in the project journal for four different resources with a posting date interval for August 2024.
After selecting the Preview Posting or Post action, the user is prompted to select a single posting date for all worklogs.
The date selected affects the month in which the resource costs will be posted to the project entries and therefore the subsequent analysis.
At the same time, the selected posting date will be used as the date of the exchange rate used for conversion to the local currency.
We recommend using the Preview Posting to understand how the merging rules work.
In the screenshot below, you can see the merged worklogs in the project ledger entries after the project journal is posted.
Merge to one G/L Account
When this rule is applied, the posted project journal lines are merged into a selected G/L account. The user will be prompted to enter a posting date and a financial account.
There are currently 19 worklogs in the project journal for various resources with a posting date interval for August 2024.
After selecting the Preview Posting or Post action, the user is prompted to select a single posting date and G/L account for all worklogs.
The date selected affects the month in which the resource costs will be posted to the project entries and therefore the subsequent analysis.
At the same time, the selected posting date will be used as the date of the exchange rate used for conversion to the local currency.
We recommend using the Preview Posting to understand how the merging rules work.
In the screenshot below, you can see the merged worklogs in the project ledger entries after the project journal is posted.
If you need to split the worklogs into multiple G/L accounts, you can use filters in the project journal and post the filtered worklogs gradually.
Do not merge
When applying this rule, the lines of the project journal are not merged after posting, and one line of the project journal will correspond to exactly one project entry.
There are currently five worklogs in the project journal for various resources with a billing date of 7th March and a total of 7,5 hours 2024.
In the screenshot below, you can see the corresponding project ledger entries created after the project journal is posted.
Tempo Worklog Archive
If you use our merging functionality, the project ledger entries created after the worklogs are posted will only display in merged form.
The original, unmerged entries are recorded in the Tempo Worklog Archive, which can be accessed via the search magnifying glass. This archive can be used for auditing purposes or to track changes in records, for example, in case of additional downloading of worklogs.
Line ID
The best way to access the merged lines is by using the click-through value in the Line ID column, available directly in the project ledger entries. Once you click on it, all corresponding lines in the Tempo worklog archive are displayed.
The value in the Merged Line ID column is clickable too, when you click on it, you will be taken back to the corresponding line in the project ledger entries.
There are also other values in the archive to help you identify the origin of each merged line such as the Jira Account ID, Tempo Worklog ID, or Tempo Updated At columns.
If you decide not to merge the worklogs, you can find all the information you need directly in the project ledger entries. In this case the value in the Line ID column will be 0 and it won’t be possible to use it to access the archive.
Posting Checks in Project Journal
The following checks can take place before the worklogs in the project journal are entered into the system using the Post action. The user is always alerted about the information they should focus on, and can then decide if they want to post the journal lines despite the alert. Therefore, all warnings below are non-blocking.
The checks that the system performs before posting can be specified in the Integration Tempo Settings.
Worklogs status check
The worklog is not in the Approved status, which means that the approval process in Tempo has not been completed.
Unit cost and unit price check
The cost or unit price of the resource is 0 for the given journal line.
Different document numbers check
The posted lines of the project journal have a different document number. Since the document number is always created automatically according to the month and year for which the worklogs are currently being downloaded, this check alerts the user that they are about to post worklogs from two or more different months.
Posted document number check
This check keeps track of duplicate postings. It will alert you if it detects that a line with the same document and project number has already been posted in the past.
If the downloaded project journal line type is empty, the following message is displayed, indicating that after the project journal line is posted, no project planning lines will be created, instead the project and resource ledger entries will be posted directly.
Specific use cases for each type of project journal line are described in this part of the documentation.
Viewing data for posted worklogs
After posting/entering the project journal lines into the system, the costs associated with the resource will be displayed on the given project card, in the Tasks section, in the Actual (Total Cost) column.
Clicking the value of the Actual (Total Cost) field displays a list of all project ledger entries (posted worklogs for the project) that make up the value in the Actual (Total Cost) field.
Another way to view the project ledger entries for a specific project task is to go to the Line tab in the Tasks section, select the History drop down menu and click Project Ledger Entries, with the line for that task selected in the tasks lines.
If you want to see all entries for the entire project and all its tasks, you can go to the Project tab on the given project card and select the Ledger Entries action.
Project Ledger Entries Cancellation
If some worklogs (project journal lines) have been entered into the system incorrectly, it is possible to cancel them by reverse entry (cancellation) through the journal of the respective project. This can be done by using the Reverse function in the project ledger entries.
This function automatically converts the selected project ledger entry line into the corresponding project journal with a negative quantity. It is also possible to cancel lines in bulk by selecting multiple lines using Ctrl + click on a line. The newly created lines must then be posted in the project journal again so that they are recorded in the corresponding project ledger entries and the resulting cost amount is reduced by the cancelled line. The whole process is described in detail below.
When using the Reverse function, the system displays a message to the user that they have created the corresponding lines in the project journal.
To post the reversed lines, the corresponding project journal can be opened directly from the project ledger entries using the action Open Project Journal.
You need to unselect the lines to access this action. If more than one line is selected, the action is greyed out.
The cancelled line is then displayed in the project journal with a negative quantity and the user records it into the system using the Post action.
Make sure your filter is set to the correct dates before posting the lines, as the system sets the dates to the current month interval by default.
After posting, the cancelled lines are then reflected again in the ledger entries of the given project, and after summing them with the original entry, the resulting value is zero (assuming that the user does not change the values of the cancelled lines in the project journal).
The posting of the cancelled line is reflected on the project card in the tasks in the Actual (Total Cost) column by lowering the initial value.
Manual download
It is possible that while using this integration, you may need to download some of the worklogs in one-time session outside of the preconfigured job queue entry that provides automatic downloads. This might occur especially after additional changes to the worklogs in Tempo, after they have already been automatically downloaded.
Bulk Manual download
Bulk manual download of worklogs can be done from the Tempo Integration Settings table through the drop-down Actions and selecting Run Job Queue Function. When you run the function, all updated worklogs according to the selected parameters are downloaded to the corresponding project journals.
During the download process you will be informed about the details for each project by the window below. Once the download is complete, this window will show a summary of the results of the entire process.
The download of worklogs also depends on the settings of the Tempo Integration Settings table, specifically the Job Queue section, where it is possible to limit e.g. the period for which worklogs should be downloaded and also whether all worklogs should be downloaded for all tasks of the project. For more information see the Tempo Integration Settings section of this documentation.
Manual download
Worklogs can be manually downloaded directly on the project card from the Tasks section. Go to the Line tab, select the Project drop-down menu and click Load Tempo Worklogs.
A window with optional parameters for downloading worklogs will then appear.
The From, To and Updated From fields are pre-populated with the dates corresponding to the last date of the automated download. The user can delete the values and set the filter on the From and To date according to their own needs. More details on the Updated From field updated from can be found here.
The other fields represent the worklog status type for which the user wants to download the worklogs.
If the user will be downloading worklogs for multiple project tasks at the same time, it is recommended to have the Save After Each Project Task field active.
The last filter allows the user to restrict the download of worklogs for a specific project and a specific project task.
If the project task number or project number is blank in this window, the user will download the worklogs for all projects and tasks that are in the system.
The user should manually download only worklogs for those projects they manage themselves.
To download worklogs according to the parameters defined by the user, select the Ok option at the bottom of the window.
Downloaded worklogs will appear in the journal of the respective project similarly to the automated download and again you will be informed about the results of the download.
The Load Tempo Worklogs action is also available directly in the Project Journal under the Home tab.
The request page with filters and options is the same as for the manual download from the project card.
Other operations related to posting and cancelling project journal lines are the same as for the automated download.