...
- a worklog is moved from one project to another project using JIRA move Issue functionality
- the icTime project configuration for a project with existing and not billed worklogs changes
- JIra default worklog functionality is NOT disabled and worklogs are created using default JIRA worklog screens
- icTime is installed / enabled on a JIRA installation with existing JIra worklogs (similar to changing the project configuration)
ictime relies on JIRA work logs and enhances JIRA work logs with additional information like an activity type, a rounding rule or a relation to a team/price list.
A "broken worklog" is a work log which is not any longer in a consistent state. A non consistent state of a worklog can be reached when
- a worklog is moved from one project to another project using JIRA move Issue functionality
- the icTime project configuration for a project with existing and not billed worklogs changes
- JIra default worklog functionality is NOT disabled and worklogs are created using default JIRA worklog screens
- icTime is installed / enabled on a JIRA installation with existing JIra worklogs (similar to changing the project configuration)
Checking for broken work logs
...
From this view, you can either delete the work log/work logs, or try to "fix" it.
| Field | Description | Remarks |
|---|---|---|
 | Delete work log. |
 | Repair work log. |
There is also the option to "automatically" fix all work logs, as far as this is possible:
...
Depending on the activity type configurations of old and new project, you might have to choose a new activity type (if the activity type of the work log does not exist in the new project).
| Field | Description | Remarks |
|---|---|---|
| Work Log | Base information from work log, like date, summary, ... |
| Old Project | Project key of the original project (where the work log had been created before the issue was moved in JIRA). |
| New Project | Project key of the new project. |
| Issue | Issue key. |
| User | User who has created this work log. |
| Old Activity Type | Activity type used | If the original work log had been created without activity type (historic data or activity types deactivated in ictime at the moment you have created this work log), "none" will be displayed here. | ||
| New Activity Type | Depending on the activity type configurations of old and new project, you might have to choose a new activity type (if the activity type of the work log does not exist in the new project).
| If the activity type does not exist in the new project, and changing the activity type of the work log is not okay for you, you need to assign the missing activity type to the new project first (see Project Activity Types). If there is no suitable activity type in the new project, but you do not want to create a suitable one, you also might choose the option "–" (none), i.e. there will be no activity type assigned. |
| Old Team / Price List | Team and price list for the original work log. | Might be empty if the original project had been configured not to use teams & price lists at the moment when the work log was created/updated (see Project Teams). |
| New Team / Price List | Team and price list the user is assigned to in the new project. | You can't correct the work log if
If the new project is currently configured not to use teams & price lists (see Project Teams), there is no problem, regardless of the configuration for the original work log. In this case, you can always repair the work log. Price information from the original work log will be lost in this case. |
| Old Rounding Rule | Rounding rule (of the original project) applied to the work log when created/updated. |
| New Rounding Rule | Rounding rule (of the new project) that will be applied to the work log when you repair the work log. | There is nothing to configure. The new rule will automatically be applied to the work log. |
Correction Not Possible - Further Actions Required
...
- The target project also has the same WLA assigned. Nothing has to be done and no problem occurs, as the project-WLA relation exists in both projects, original project and target project.
- The target project does not have the same WLA assigned. When fixing the work log, the WLA value will be deleted, because this WLA does simply not exist in the target project.
...