Dear Technical Support Team,
We are currently using JIRA v9.12.3 and Bitbucket v8.19.13.
After upgrading Bitbucket from v7.x to v8.19.13, we have encountered an issue where JIRA no longer displays links to new Bitbucket commits containing JIRA keys.
However, links to older commits made before the update still function correctly.
Interestingly, within Bitbucket, JIRA keys in the commit messages are correctly detected, and clicking on them redirects to the corresponding JIRA pages without any issue.
I noticed the error message below in the atlassian-bitbucket.log, which might shed some light on the cause of this problem within Bitbucket:
Could you please assist us in resolving this issue?
Thank you in advance for your help.
Best regards,
Markus
2025-01-09 08:19:14,532 ERROR [commit-indexing:thread-1] c.a.s.internal.idx.HierarchyIndexer [XXX/repo[100]] Indexing failed java.lang.NoSuchMethodError: 'void com.atlassian.bitbucket.idx.CommitIndex.addProperty(java.lang.String, java.lang.String, java.lang.String)' at ch.mibex.stash.rightrepo.idx.JiraProjectCommitIndexer$$anonfun$index$1.apply(JiraProjectCommitIndexer.scala:19) at ch.mibex.stash.rightrepo.idx.JiraProjectCommitIndexer$$anonfun$index$1.apply(JiraProjectCommitIndexer.scala:17) at scala.collection.immutable.Set$Set1.foreach(Set.scala:79) at ch.mibex.stash.rightrepo.idx.JiraProjectCommitIndexer.index(JiraProjectCommitIndexer.scala:17) at ch.mibex.stash.rightrepo.idx.RightRepoCommitIndexer.onCommitAdded(RightRepoCommitIndexer.scala:21) at com.atlassian.stash.internal.idx.DefaultCommitIndexingService$IndexOperation.lambda$indexCommits$0(DefaultCommitIndexingService.java:465) at com.atlassian.stash.internal.idx.DefaultCommitIndexingService$IndexOperation.eachIndexer(DefaultCommitIndexingService.java:400) at com.atlassian.stash.internal.idx.DefaultCommitIndexingService$IndexOperation.indexCommits(DefaultCommitIndexingService.java:463) at com.atlassian.stash.internal.idx.DefaultCommitIndexingService$IndexOperation.run(DefaultCommitIndexingService.java:353) at com.atlassian.stash.internal.idx.DefaultCommitIndexingService.indexRepository(DefaultCommitIndexingService.java:146) at jdk.internal.reflect.GeneratedMethodAccessor2799.invoke(Unknown Source) at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at jdk.internal.reflect.GeneratedMethodAccessor188.invoke(Unknown Source) at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at jdk.proxy3/jdk.proxy3.$Proxy479.indexRepository(Unknown Source) at com.atlassian.stash.internal.idx.HierarchyIndexer$1.perform(HierarchyIndexer.java:64) at com.atlassian.stash.internal.idx.HierarchyIndexer$1.perform(HierarchyIndexer.java:38) at com.atlassian.stash.internal.user.DefaultEscalatedSecurityContext.call(DefaultEscalatedSecurityContext.java:59) at com.atlassian.stash.internal.idx.HierarchyIndexer.process(HierarchyIndexer.java:38) at com.atlassian.stash.internal.concurrent.HazelcastBucketedExecutor$BucketProcessingBootstrapper.run(HazelcastBucketedExecutor.java:146) at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:539) at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264) at java.base/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:304) at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136) at java.base/java.lang.Thread.run(Thread.java:840)
... 17 frames trimmed
Hello
It looks like you have an older version of the `Create Branch Wizard for Bitbucket` app installed.
Update to at least version 2.1.6 to be compatible with Bitbucket 8.19.x, or even better the latest version 3.0.1.
If version 3.0.1 does not work for you, let us know or contact the Mibex Software support: https://support.mibexsoftware.com/
Best regards
Roman from Mibex Software
Many thanks for your quick and precise response.
We had an installation of the "Create Branch Wizard Lite" from our previous Bitbucket Server active. This was not marked as incompatible.
After uninstallation it seems everything is fine again.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Add-On: I also get the protocol analyse error "Plugin incompatibility with Bitbucket Server 3.0" indicating to this line without further information what plugin is incompatible.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.