There is a fundamental difference in how JIRA handles work logs regarding the timezone of a user who logs works and how this is done. In certain scenarios, this will lead to a situation where the same work logs will have a different time/date depending on if you look at them in JIRA or in ictime.
...
| Table of Contents |
|---|
How JIRA Saves Work Logs
JIRA assumes that work is logged on server time and converts it from the "user time" to "server time" before saving. Once JIRA displays the work log, the user timezone setting (= of the user who is "owner" of the work log) will be applied so that the user gets the correct display. However, unfortunately JIRA does not include the timezone information into the work log. As a weird consequence, this means that when a user changes his/her timezone (e.g. because the user works in a global company and moves to an office in a different country), all existing work logs will now show a different time (and maybe even date). This is not correct, as a user would definitely expect his old worklog report not to change just because he/she now works in a different timezone.
How ictime Saves Work Logs
...
- you use JIRA and ictime at the same time to log work,
- you work with historic JIRA work logs in ictime
- you work with ictime work logs in JIRA.
No Solution for this Issue
It is not possible to solve this problem, as JIRA does not provide the data that would be required to solve the problem and as in general the way JIRA handles this use case does not seem to be correct so that is does not make sense that ictime does it the same way JIRA does (other plugin vendors have taken the same decision, see http://www.tempoplugin.com/faq/why-is-there-a-time-difference-between-my-jira-worklog-and-my-tempo-work-log/). This means:
...