Crashing when clicked on configure link of the timesheet plugin In Jira 5.2.6

Issue #391 resolved
Former user created an issue

I am with Southwest Airlines co and we purchased Timesheet plugin license very recently.

Today we upgraded Jira to 5.2.6 and getting following error and crashing when clicked on the configure link of the timesheet plugin in Jira 5.2.6

Timesheet plugin version 2.4.2

--------------------Error Below--------------------------------------

Not Found (404) Error creating bean with name 'jira.timesheet.plugin.configuration.ConfigurationAction': Unsatisfied dependency expressed through constructor argument with index 0 of type [jira.timesheet.plugin.configuration.ConfigurationService]: : No unique bean of type [jira.timesheet.plugin.configuration.ConfigurationService] is defined: Unsatisfied dependency of type [class jira.timesheet.plugin.configuration.ConfigurationService]: expected at least 1 matching bean; nested exception is org.springframework.beans.factory.NoSuchBeanDefinitionException: No unique bean of type [jira.timesheet.plugin.configuration.ConfigurationService] is defined: Unsatisfied dependency of type [class jira.timesheet.plugin.configuration.ConfigurationService]: expected at least 1 matching bean Could not find what you were looking for. Maybe you should raise an issue. JIRA home

Comments (6)

  1. Andriy Zhdanov

    Hi Rao,

    This is unfortunately problem, that I've never managed to reproduce or understand the cause. Could you please clarify from which JIRA version have you upgraded?

    Also you may try to restart JIRA, and/or reinstall plugin, i.e. uninstall it and install again.

    See also issue#370

    Thank you.

  2. Former user Account Deleted

    Hi Andriy, thanks for the quick response. We did our routine maintenance work in jira and as a part of it we restarted and re-indexed Jira but still no luck with this error. Last weekend we upgraded from Jira 4.3.3 to 5.2.6. In in the next maintenance window i will try to uninstall and install it again. In the mean time could you please check and see if you can find the the firm fix for this issue.

  3. Andriy Zhdanov

    Hi Rao,

    Upgrading from JIRA 4.3.3 you should have upgraded plugin from 2.2.9 most likely to 2.4.2. I wonder how did you proceed? Because 2.2.9 could not work on JIRA 5.2.6 and thus might not have been properly upgraded.

    Thank you.

  4. Log in to comment