After upgrade JIRA to 7.1 Timesheet plugin works incorrect
After upgrade JIRA to 7.1 Timesheet plugin works incorrect: 1. Configuration screen for gadget is corrupted - screenshot attached 2. People who didn't log any worklogs during the week disappeared from list of people in gadget.
Comments (11)
-
-
reporter No, It doesn't help
-
Could you please try reinstalling it then.
-
reporter doesn't help
-
Last stupid question, are actually using plugin version 3.x for JIRA 7?
-
reporter Version: 3.0.4
-
Could you please check if there is old version left in the filesystem, e.g.:
--$ find jira -name jira-timesheet-plugin*.jar jira/home/plugins/.osgi-plugins/transformed-plugins/jira-timesheet-plugin-3.0.4_1456425179000.jar jira/home/plugins/.osgi-plugins/transformed-plugins/jira-timesheet-plugin-3.0.4_1456428073000.jar jira/home/plugins/installed-plugins/jira-timesheet-plugin-3.0.4.jar
It should have only 3.0.4
-
reporter I see 3.0.4 only: /var/atlassian/application-data/jira-rh7/plugins/.osgi-plugins/transformed-plugins/plugin.8372789879002682069.jira-timesheet-plugin-3.0.4_1455949536000.jar /var/atlassian/application-data/jira-rh7/plugins/.osgi-plugins/transformed-plugins/plugin.4733540978794166991.jira-timesheet-plugin-3.0.4_1456475365000.jar /var/atlassian/application-data/jira-rh7/plugins/.osgi-plugins/transformed-plugins/plugin.1625602795863925290.jira-timesheet-plugin-3.0.4_1455936556000.jar /var/atlassian/application-data/jira-rh7/plugins/installed-plugins/plugin.4733540978794166991.jira-timesheet-plugin-3.0.4.jar
But there are two more instances of JIRA is stored on the same server, and they older versions of plugin. But they locate din different locations /var/atlassian/application-data/jira/ and /var/atlassian/application-data/jira-rh/. Can it affect?
-
No, I don't think so, but may be you can uninstall it again from JIRA7, (stop JIRA) remove all 3.0.4 occurrences, (start JIRA) and install it again.
-
reporter It doesn't help
-
- changed status to resolved
Fantastic! Thank you for figuring it out, sorry I was not aware of such case.
- Log in to comment
Hi Andrey,
It may be that plugin is not properly initialised, could you please try if restarting JIRA helps?
Thank you.