500 Error in Bitbucket Server when selecting Issue Transitions Settings
Symptoms
500 Error in Bitbucket Server when selecting Issue Transitions Settings. The following stack trace is displayed in the atlassian-bitbucket.log:
2014-10-08 14:08:29,560 ERROR [http-nio-7990-exec-58] @HI6X1Cx848x326597x0 n1x7he 10.10.47.3,127.0.0.1 "GET /mvc/error500 HTTP/1.0" c.a.s.i.web.ErrorPageController There was an unhandled exception loading [/plugins/servlet/issue-transitions/AP/apple-core]
javax.servlet.ServletException: Servlet execution threw an exception
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:314) ~[catalina.jar:8.0.9]
at com.atlassian.applinks.core.rest.context.ContextFilter.doFilter(ContextFilter.java:25) ~[na:na]
at com.atlassian.bitbucket.internal.spring.security.Bitbucket ServerAuthenticationFilter.doFilter(Bitbucket ServerAuthenticationFilter.java:86) ~[Bitbucket ServerAuthenticationFilter.class:na]
at com.atlassian.bitbucket.internal.web.auth.BeforeLoginPluginAuthenticationFilter.doInsideSpringSecurityChain(BeforeLoginPluginAuthenticationFilter.java:111) ~[BeforeLoginPluginAuthenticationFilter.class:na]
at com.atlassian.bitbucket.internal.web.auth.BeforeLoginPluginAuthenticationFilter.doFilter(BeforeLoginPluginAuthenticationFilter.java:77) ~[BeforeLoginPluginAuthenticationFilter.class:na]
at com.atlassian.security.auth.trustedapps.filter.TrustedApplicationsFilter.doFilter(TrustedApplicationsFilter.java:100) ~[TrustedApplicationsFilter.class:na]
at com.atlassian.oauth.serviceprovider.internal.servlet.OAuthFilter.doFilter(OAuthFilter.java:69) ~[na:na]
at com.atlassian.analytics.client.filter.DefaultAnalyticsFilter.doFilter(DefaultAnalyticsFilter.java:33) ~[na:na]
at com.atlassian.core.filters.AbstractHttpFilter.doFilter(AbstractHttpFilter.java:31) ~[AbstractHttpFilter.class:na]
at com.atlassian.bitbucket.internal.web.auth.BeforeLoginPluginAuthenticationFilter.doBeforeBeforeLoginFilters(BeforeLoginPluginAuthenticationFilter.java:89) ~[BeforeLoginPluginAuthenticationFilter.class:na]
at com.atlassian.bitbucket.internal.web.auth.BeforeLoginPluginAuthenticationFilter.doFilter(BeforeLoginPluginAuthenticationFilter.java:75) ~[BeforeLoginPluginAuthenticationFilter.class:na]
at com.atlassian.bitbucket.internal.request.DefaultRequestManager.doAsRequest(DefaultRequestManager.java:84) ~[DefaultRequestManager.class:na]
at com.hazelcast.web.WebFilter.doFilter(WebFilter.java:450) ~[WebFilter.class:3.3-RC3]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [na:1.7.0_67]
at java.lang.Thread.run(Thread.java:745) [na:1.7.0_67]
... 177 frames trimmed
Caused by: java.lang.NoSuchMethodError: com.atlassian.bitbucket.repository.RepositoryService.findBySlug(Ljava/lang/String;Ljava/lang/String;)Lcom.atlassian.bitbucket/repository/Repository;
at com.hindsighttesting.bitbucket.storyflow.IssueTransitionsPage.doGet(IssueTransitionsPage.java:54) ~[na:na]
... 15 common frames omittedCause
You've got the Storyflow for Bitbucket Server plugin installed on a 3.X instance. This happens for what is explained on Plugin incompatibility with Bitbucket Server 3.0. The issue with this plugin was reported to the vendor through https://bitbucket.org/hindsightsoftwareltd/storyflow-for-bitbucket/issue/16/add-support-for-bitbucket-3x-release
Resolution
Please uninstall the plugin (resolution described on Plugin incompatibility with Bitbucket Server 3.0) . As described on JIRA integration under "Transition JIRA issues automatically", by integrating Bitbucket Server 3.2+ and JIRA 6.3.3+:
"Your JIRA workflow can now respond to events in your linked development tools. For example, when a pull request is created, your JIRA workflow can be configured to automatically transition the related issue. Configure this from transitions within the JIRA workflow editor.
The events available in Bitbucket Server are:
- Branch created
- Commit created
- Pull request created
- Pull request merged
- Pull request declined"
That's very close to what this plugin used to provide. Please upgrade your Bitbucket Server and JIRA instances and configure them accordingly.