Duplicate "Log Work" Options Available

As ictime can't override respective JIRA functionality, it adds a separate "Log Work (ictime)" dialogue to JIRA. This means that users get two "Log Work" options, one from ictime, one from JIRA, e.g. on the issue screen, the issue navigator etc. This is not only confusing but would also mean that specific ictime functionality is not available when you use the JIRA dialogue. You can Atlassian gives instructions on how to disable the JIRA dialogue log work functionality here: https://confluence.atlassian.com/pages/viewpage.action?pageId=715129243. You can do the same (and/or can prevent the JIRA one dialogue from being usable) via ictime in a simple way (technically, same thing is done, i.e. some JIRA system plugin modules are disabled). Please refer to General Configuration.

Issue Screen: Time Tracking Panel

...

and "Work Log" Tab Disappear

Installing ictime will cause duplicate "Log Work" dialogues appearing in different places, one from ictime, one from JIRA. We offer . You can avoid this behaviour (see  https://confluence.atlassian.com/pages/viewpage.action?pageId=715129243) and ictime also offers a simple way how to disable do the JIRA dialogue same (see General Configuration). However, as a result, in some JIRA instances, not only If you use the third-party add-on "Hide Time Tracking", due to a bug in this add-on, in case the "Log Work" operation is disabled like intendedin JIRA, but the "Time Tracking" web panel disappearsand the "Work Log" tab disappear, too.  There is no known workaround, but you You can enable/use the respective "Time Tracking (ictime)" panel instead which offers basically the same functionality, and same for the "Work Log (ictime)" tab (see ictime Permissions).

4.1h is Converted Into 4h 5m (Instead of 4h 6m)

...

This is not an ictime bug, but a bug in JIRA functions ictime is using (multiplying a long value by a double value which which results in something like 14759.9999~ instead of 14760; and as no rounding is configured, this will get 4h 5m instead of 4h 6m). A bug report has been raised already: https://jira.atlassian.com/browse/JRA-41907. There is no known workaround or solution. We do not want to write our own conversion functions as we usually try to rely on JIRA functionality wherever this is possible. The given example so far is the only one where we have seen this behaviour, we could not reproduce any conversion issues with any other combination (like 2.1h, 7.1h etc.).

Timesheet/Reporting, Search Returns Blank Screen

If you have a higher number of projects, you might run into this problem. In this case, the URL for the request might get very long, and depending on your Web server configuration, the length exceeds the defined settings.  Although the specification of the HTTP protocol does not specify any maximum length for the URL, practical limits are imposed by web browser and server software. If this happens, please check with your system administrator the settings for the maximum lenght of the URL on your server and try to increase the length.

JIRA "Log Work" Operation No Longer Available After Uninstalling/Disabling ictime or Trial Expired

...

...

Explanation: If a license of a plugin is valid or not is not determined by the plugin itself, but by JIRA. In case of the bug, Atlassian's Universal Plugin Manager (UPM) returns an invalid license to ictime, and so ictime stops working. Reason why the UPM returns the invalid license is that on installation or update of ictime, the UPM did/does not store the build/release date of the plugin correctly, and this date is essential once your maintenance expires (for JIRA UPM to check if the version you have installed is valid in terms of having been released still within your maintenance period). As a result of the bug, after maintenance expiration, the UPM will always return that your license does not match the ictime version because the UPM thinks that this ictime version has been released after maintenance expiry, which is not the case.

There is no way to resolve this problem with reasonable effort from our side, as the suggested solution from Atlassian is not feasible in the specific case of ictime due to dependencies to another plugin (icbiz). Atlassian did not yet apply should have applied a fix to any JIRA version (status 23.02.2015; JIRA 6.3.x), but JIRA version 6.4 should fix the bugversio 6.4 (released 17.03.2015). You would need to update to JIRA 6.4, and after this uninstall and re-install ictime (the last version still released within your maintenance period). After this, everything should work like expected again. If you can't update to JIRA 6.4 - or if the last version of ictime you are entitled to use is not compatible with JIRA 6.4 -, please contact our support to find an alternative solution.