JIRA 8.x compatibility

Create issue
Issue #23 new
Former user created an issue

Plugin appears to not be updated for the new lucene in 8.x. Module loads, but doesn't work properly when issues are indexed:

2019-03-23 18:04:32,451 http-nio-8080-exec-24 ERROR nneulinger 1084x13960x1 111inu1, /rest/gadget/1.0/issueTable/jql [c.a.j.issue.fields.ImmutableCustomField] Error during searcher initialization of the custom field eu.kprod.jira.stattable-searchers:stattableExactText (Custom field ID: 12100):
java.lang.NoClassDefFoundError: org/apache/lucene/document/Fieldable
    at eu.kprod.jira.searchers.ExactTextSearcher.init(ExactTextSearcher.java:60)
    at eu.kprod.jira.searchers.ExactTextSearcher.init(ExactTextSearcher.java:38)
    at com.atlassian.jira.issue.fields.ImmutableCustomField.loadCustomFieldSearcher(ImmutableCustomField.java:1784)
    at io.atlassian.fugue.Suppliers$MemoizingSupplier.get(Suppliers.java:175)
    at com.atlassian.jira.issue.fields.ImmutableCustomField.getCustomFieldSearcher(ImmutableCustomField.java:1519)
    at com.atlassian.jira.issue.fields.ImmutableCustomField.createAssociatedSearchHandler(ImmutableCustomField.java:627)

Comments (9)

  1. Barby Sizemore

    Any timeline for upgrading the plugin to be compatible with Jira 8.x?? We are upgrading and I did find another plugin – Natural Searchers for Jira – that looks like it will work for us, but since this is a paid plug-in, I was hoping to get more support and to see an upgrade soon.


    Barby Sizemore

  2. Nathan Neulinger

    We’re coming up on a license renewal for a 2000-user Jira installation - and I see no reason for us to renew if the plugin is abandoned. Are you going to release a new build with fixes for Jira 8.x?

  3. Dominique Ledit

    Same concern about the compatibility of the plugin with Jira 8.x. We have a 500-users Jira installation. Any update?

  4. Jorge Jerez

    @Marc Trey Is there any update planned or you just stop the support for the app? We’re not paying 2k license for this

  5. Dalectric

    I’ve asked Atlassian to see if they can contact him, but they’ve received no response either.

  6. Dalectric

    I’ve started updating the source code offline to see if I can fix the issues I have with NumericStatisticMapper showing very large values instead of the values from my custom field.

    I’m by no means a Java expert, so my modifications probably aren’t 100% correct. So far I have it building and working for Jira 8.2.4 with Amps 6.3.21 but I’ve not resolved my strange value issue above. If I find a solution I will post it on here.

  7. Dalectric

    The velocity code needs updating for more recent versions of Jira which has increased security for Velocity. This can be done without recompiling the code by opening the JAR file with 7Zip and updating the code as shown below (example for viewn-umber.vm

    #set ($numberTool = $ctx.getClass().forName("com.atlassian.jira.util.velocity.NumberTool").newInstance())


    #set ($numberTool = $ctx.get("jirautils").loadComponent("com.atlassian.jira.util.velocity.NumberTool", $ctx.getClass()))

    I’m assuming this will be similar for the other VMs but I’ve not tested this yet.

  8. Log in to comment