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 maven.atlassian.com 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.
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(ClauseChecker.java:46)
at com.atlassian.jira.plugin.devstatus.issuenavigator.searcher.checker.ClauseChecker.lambda$and$6(ClauseChecker.java:55)
at com.atlassian.jira.plugin.devstatus.issuenavigator.searcher.checker.ClauseChecker.lambda$and$6(ClauseChecker.java:55)
at com.atlassian.jira.plugin.devstatus.issuenavigator.searcher.checker.ClauseChecker.lambda$and$6(ClauseChecker.java:55)
at com.atlassian.jira.plugin.devstatus.issuenavigator.searcher.checker.ClauseChecker.lambda$build$7(ClauseChecker.java:85)
at com.atlassian.jira.plugin.devstatus.issuenavigator.searcher.JqlHelper$3.lambda$visit$0(JqlHelper.java:211)
at java.util.stream.MatchOps$1MatchSink.accept(MatchOps.java:90)
at java.util.Spliterators$ArraySpliterator.tryAdvance(Spliterators.java:958)
at java.util.stream.ReferencePipeline.forEachWithCancel(ReferencePipeline.java:126)
at java.util.stream.AbstractPipeline.copyIntoWithCancel(AbstractPipeline.java:498)
at java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:485)
at java.util.stream.AbstractPipeline.wrapAndCopyInto(AbstractPipeline.java:471)
at java.util.stream.MatchOps$MatchOp.evaluateSequential(MatchOps.java:230)
at java.util.stream.MatchOps$MatchOp.evaluateSequential(MatchOps.java:196)
at java.util.stream.AbstractPipeline.evaluate(AbstractPipeline.java:234)
at java.util.stream.ReferencePipeline.anyMatch(ReferencePipeline.java:449)
at com.atlassian.jira.plugin.devstatus.issuenavigator.searcher.JqlHelper$3.visit(JqlHelper.java:211)
at com.atlassian.jira.plugin.devstatus.issuenavigator.searcher.JqlHelper$3.visit(JqlHelper.java:207)
at com.atlassian.query.clause.TerminalClauseImpl.accept(TerminalClauseImpl.java:143)
at com.atlassian.jira.plugin.devstatus.issuenavigator.searcher.JqlHelper$3.lambda$doVisit$1(JqlHelper.java:223)
at java.util.stream.ReferencePipeline$7$1.accept(ReferencePipeline.java:267)
at java.util.ArrayList$ArrayListSpliterator.forEachRemaining(ArrayList.java:1382)
at java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:481)
at java.util.stream.AbstractPipeline.wrapAndCopyInto(AbstractPipeline.java:471)
at java.util.stream.ReduceOps$ReduceOp.evaluateSequential(ReduceOps.java:708)
at java.util.stream.AbstractPipeline.evaluate(AbstractPipeline.java:234)
at java.util.stream.ReferencePipeline.collect(ReferencePipeline.java:499)
at com.atlassian.jira.plugin.devstatus.issuenavigator.searcher.JqlHelper$QueryToOptionsConverter.toOptions(JqlHelper.java:264)
at
@dubey.harsh07,
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.