ictime | time tracking 5.x
Page tree

This documentation describes all functionality of the latest ictime version (5.x for JIRA 7 and 4.x for JIRA 6.x ) for administrators and users. For documentation of older versions, please refer to Documentation History.

Skip to end of metadata
  • Created by Unknown User (557058:ce44f342-16e1-4518-890d-09042c8c16a4), last modified by Unknown User (5c50bfbc825530450d75c2e1) on Aug 12, 2014
Go to start of metadata

ictime offers a simple possibility to move work logs between different JIRA issues within one project.

Access Move Work Log Functionality

You can move work logs on

Limitations

You can only move work logs between different JIRA issues within one project. It is not possible to move work logs between issues of different projects. Reason is that configuration of different projects might be fundamentally different regarding activity types, teams and price lists so that a work log would not be "compatible" and you could only move it by making configuration changes before - if possible at all.

Move Work Log

Find the work log you want to move in your timesheet or in your report (see Timesheet and Reports: Work Log Details). Click on the following icon:

The following interface will open in a separate window:

To select a new issue where the work log should be moved to, start to type part of the issue description or key in the "New Issue" field. The JIRA issue picker will return suggestions.

Please note that the issue picker will also suggest issues of different projects (as this is the default JIRA behaviour). You can select such issues, but will get an error message when trying to move the issue.

Restrictions for Moving Work Logs

The restrictions applied when moving a work log are different, depending on if you are moving a work log in Timesheet or in the Reporting section. The general difference between Timesheet and Reporting is that a Reporting user is considered a user with basically all possible permissions, and these permissions will overwrite a couple of JIRA permission checks. A timesheet user is basically subject to all limitations defined by JIRA.

Timesheet

  • Current user needs the JIRA permission to edit and to delete a work log ("Edit Own Work Logs", "Delete Own Work Logs"; and/or "Edit All Work Logs", "Delete All Work Logs"). If you have the permission for all work logs in JIRA, you will be able to move work logs of other users, too.
  • JIRA restrictions regarding issue status are applied when moving a work log to another issue within the same project: You can neither move a work log from a closed issue nor can you move a work log to a closed issue (more general: an issue in state "not editable", this also might be another status that has this property).
  • Current user needs the JIRA permissions "Work on Issues" and "Browse Project" for both the origin and the target issue (please note that we do not check if the user who has originally created the work log has these permissions).

Reporting

  • None of the above restrictions.

In both cases, it won't be possible to move a work log that has already been approved or charged.

Move JIRA Issues

Although ictime does not support moving of work logs between issues of different projects, JIRA offers the option to move issues to different projects. If issues have work logs already, those will be moved with the issue. This will lead to an inconsistency in ictime as JIRA is not aware of ictime and all data added to the JIRA work log on ictime level won't be moved, so they still have a wrong project relation in ictime.

This topic is addressed here: Fix Work Logs (Warnings).

  • No labels