When moving issues with work logs - created or updated with ictime - to a different project in JIRA, this will lead to inconsistencies in ictime data. This problem needs to be fixed manually.
Inconsistent Work Logs
ictime relies on JIRA work logs and enhances JIRA work logs with additional information like an activity type or a relation to a team/price list. As JIRA is not "aware" of ictime and ictime can't modify base operations in JIRA like moving an issue, ictime data will get inconsistent when you move an issue with work logs - created or updated with ictime - to a different project in JIRA. This issue will now belong to a new project (and would be displayed correctly in ictime - Reporting, My Timesheet), but team & price list assignment (see Project Teams) of the work log in ictime would still point to the team of the old project - ictime does not even know that you have moved the issue. In addition to the team problem, you might also have a problem with activity types (see Project Activity Types), as the work log might have assigned an activity type that does not exist in the new project.
Unfortunately, there is no automated way to fix the problem, as any fix will require decisions on how to handle a conflict and specifically it might require that you create or modify a team in the new project in order to be bale to correct the work log. For this reason, there is a specific interface that lists work logs with problems and allows an administrative user either to delete such work logs or to "repair" them.
This problem only applies to work logs that have been created or updated when ictime was already installed. "Historic" work logs, i.e. work logs that only exist in the JIRA database and do not have any enhanced ictime data/relations, are never affected.
Access Repair Functionality
Repair Screen