This page explains the various reasons why a worklog is invalid. The Status column in any list view shows if the worklogs are invalid and for which reasons. The Advanced Timesheet and any of its views, have a standard Invalid Worklogs filter available.
Issues with invalid worklogs are displayed with an Invalid Worklogs label, at the end of the issue line in timesheets. This accounts for the User, Advanced and the Issue Timesheet (if Include sub-tasks is ticked).
The List View showing Invalid Worklogs reasons in the Status column
The table below explains the three reasons why a worklog can become invalid.
| Status | Description | ||||||
|---|---|---|---|---|---|---|---|
| This message is displayed if a required field is missing, according to the set Expression on the Fields screen.
| ||||||
| If the user does not have a Staff ID user property set, the message Staff ID missing is displayed.
| ||||||
| The last type of message in the Status column is if Tempo data is synced with an external system. The message is either OK or some error message from the external system. |
Correcting an account mismatch
Worklogs might contain an Account field, through which the worklogs can be directly linked to an account. When you move or split a worklog, you might cause the worklog to be associated with an issue in a project that is not linked to the worklog's account. In such a case, where worklog account and project account do not match, the worklog is listed on the invalid worklogs page.
You can make the worklog valid by linking the project to the same account or by editing the worklog in any report.
In reports, you can identify invalid worklogs, which are listed with an account key but without an account name.
| Panel | ||||
|---|---|---|---|---|
| ||||
| Panel | ||||
|---|---|---|---|---|
| ||||
|