No trick, just treat! EAP milestone 07 for Jira 8.0 is ready!

A for Awesome EAP

The last in the row of Jira 8.0 EAPs, EAP milestone 07 features a batch of platform upgrades. We have also migrated Jira to a new Fugue and upgraded Guava.

With this EAP milestone, you’re also getting a new cool feature to batch email notifications. It reduces the number of emails you receive when issues are being updated.

To make your testing as easy as a pumpkin pie, we have listed all the changes in our thrilling Preparing for Jira 8.0. Make sure you read it before you download this EAP.

If you use the site to download your milestones, make sure you get milestone 8.0.0-m0021.

B for Beta…

Yes, Beta is next in line. Feature-wise, it will be close to what we want to ship as Jira 8.0. However, if internal or vendor feedback brings it home to us that some more changes are required (and yes, these can be breaking changes), they will be introduced in the upcoming beta.

C for Comments…

Your feedback is super important. Post any comments you might have here and we’ll be on them shortly.


The Jira Server team


@mmichalak is there an ETA for the beta release?

They’ve been going at a 2 week pace … I would assume to see it in 2 weeks.

Custom jql functions are not working with this build.

Steps to reproduce

  1. Write a custom JQL, and ensure to add the ID of the data you’re filtering such as project per my example below
  • project = 10000
  1. Copy the URL with the JQL in it and paste in the web browser (e.g http://localhost:8080/issues/?filter=-3&jql=project%20%3D%2010000)
  2. Jira will trigger an error as the example below
    Getting the below error.

Log excerpts — start

2018-11-09 12:51:57,516 http-nio-7080-exec-1 ERROR admin 771x1637x1 1eg6rep 0:0:0:0:0:0:0:1 /issues/ [o.a.c.c.C.[.[localhost].[/].[action]] Servlet.service() for servlet [action] threw exception
java.lang.NoSuchMethodError: com.atlassian.query.clause.TerminalClause.getProperty()Lcom/atlassian/fugue/Option;
at com.atlassian.jira.plugin.devstatus.issuenavigator.searcher.checker.ClauseChecker.lambda$expectProperty$5(
at com.atlassian.jira.plugin.devstatus.issuenavigator.searcher.checker.ClauseChecker.lambda$and$6(
at com.atlassian.jira.plugin.devstatus.issuenavigator.searcher.checker.ClauseChecker.lambda$and$6(
at com.atlassian.jira.plugin.devstatus.issuenavigator.searcher.checker.ClauseChecker.lambda$and$6(
at com.atlassian.jira.plugin.devstatus.issuenavigator.searcher.checker.ClauseChecker.lambda$build$7(
at com.atlassian.jira.plugin.devstatus.issuenavigator.searcher.JqlHelper$3.lambda$visit$0(
at java.util.Spliterators$ArraySpliterator.tryAdvance(
at com.atlassian.jira.plugin.devstatus.issuenavigator.searcher.JqlHelper$3.visit(
at com.atlassian.jira.plugin.devstatus.issuenavigator.searcher.JqlHelper$3.visit(
at com.atlassian.query.clause.TerminalClauseImpl.accept(
at com.atlassian.jira.plugin.devstatus.issuenavigator.searcher.JqlHelper$3.lambda$doVisit$1(
at java.util.ArrayList$ArrayListSpliterator.forEachRemaining(
at com.atlassian.jira.plugin.devstatus.issuenavigator.searcher.JqlHelper$QueryToOptionsConverter.toOptions(

Log excerpts — end

Thanks for your report! Unfortunately EAP07 was released with an incompatible version of Development Integration Plugin.
You can try disabling this plugin and see if this lets you work on your custom jql functions.

Thanks for the reply.
What is the expected date of release for compatible version of integration plugin.

No luck with disabling the plugins as well.

The version 5.2+ is compatible with EAP07. You can download if from here.
Sorry for the inconvenience.

Where I have to update this jar file ?

@dubey.harsh07 you have to put it into the home directory under plugins/installed-plugins

Or you can install it via “Admin” -> “Add-ons” -> “Manage apps” -> “Upload app”.

Thanks, it worked after deploying the provided jar.
when will be the fix roll out for the same?