Heads up! On March 5, starting at 4:30 PM Central Time, our community will be undergoing scheduled maintenance for a few hours. During this time, you might find the site temporarily inaccessible. Thanks for your patience. Read more.

×
Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Power BI throwing an error while validating a JQL Query

Saif Allah AZZAZA January 22, 2025

Hello,

I am trying to create PowerBI connector. When I hit the validate JQL button, The following error message does appera:

 

 

aio.jira.connector.exception.InvalidJQLException: the value 'XXXX' does not existe in the field project. I am querying to fecth data from 'YYYY' project. I checked onlien and it looks like  this happens when users are not authenticated but in my case I am connected. My colleagues can create connectors and use the url with no issue. It happens for users who will create their first connector.

Thansk

1 answer

0 votes
quentin.leroy January 22, 2025

Hello @Saif Allah AZZAZA ,

Quentin from Appfire here; thank you for taking the time to write your question. 

I am glad to hear you have chosen to use the Power BI Connector and your colleagues is able to generate connectors successfully.

Your Jira administrator can enforce the use of Basic Auth, which means you would be ask to set up a username and password in order to authenticate on Power BI. This happens after the JQL validation though. The application perform a validation of the JQL query when you click on Save & Close (more info here in the documentation).

Could you share the exact JQL query you are trying to parse and a screenshot of the error message? That would help me better understand the context.

We also have a great support team, always ready to help and very knowledgeable. They can go deeper into your specific challenge and quickly troubleshoot it.

Looking forward to hearing from you! 

Saif Allah AZZAZA January 23, 2025

Hello Quentin,

this erros occurs when I am trying to setup my Connector for the first time to get the connector url. Please refer to the following screen shot.

BRpowerbi connector.png

Saif Allah AZZAZA January 23, 2025
aio.jira.connector.exception.InvalidJQLException: La valeur 'XXXX' n'existe pas pour le champ 'project'.
at aio.jira.connector.service.business.ConnectorHelper.validateJql(ConnectorHelper.java:916)
at aio.jira.connector.powerbi.service.business.PowerBIHelper.validateJql(PowerBIHelper.java:232)
at aio.jira.connector.powerbi.service.business.PowerBIConnectorManagerService.strictValidateJql(PowerBIConnectorManagerService.java:54)
at aio.jira.connector.powerbi.rest.PowerBIProtectedResource.validateJql(PowerBIProtectedResource.java:68)
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:77)
at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.base/java.lang.reflect.Method.invoke(Method.java:569)
at org.glassfish.jersey.server.model.internal.ResourceMethodInvocationHandlerFactory.lambda$static$0(ResourceMethodInvocationHandlerFactory.java:52)
at org.glassfish.jersey.server.model.internal.AbstractJavaResourceMethodDispatcher$1.run(AbstractJavaResourceMethodDispatcher.java:146)
at org.glassfish.jersey.server.model.internal.AbstractJavaResourceMethodDispatcher.invoke(AbstractJavaResourceMethodDispatcher.java:189)
at org.glassfish.jersey.server.model.internal.JavaResourceMethodDispatcherProvider$TypeOutInvoker.doDispatch(JavaResourceMethodDispatcherProvider.java:219)
at org.glassfish.jersey.server.model.internal.AbstractJavaResourceMethodDispatcher.dispatch(AbstractJavaResourceMethodDispatcher.java:93)
at org.glassfish.jersey.server.model.ResourceMethodInvoker.invoke(ResourceMethodInvoker.java:478)
at org.glassfish.jersey.server.model.ResourceMethodInvoker.apply(ResourceMethodInvoker.java:400)
at org.glassfish.jersey.server.model.ResourceMethodInvoker.apply(ResourceMethodInvoker.java:81)
at org.glassfish.jersey.server.ServerRuntime$1.run(ServerRuntime.java:256)
at org.glassfish.jersey.internal.Errors$1.call(Errors.java:248)
at org.glassfish.jersey.internal.Errors$1.call(Errors.java:244)
at org.glassfish.jersey.internal.Errors.process(Errors.java:292)
at org.glassfish.jersey.internal.Errors.process(Errors.java:274)
at org.glassfish.jersey.internal.Errors.process(Errors.java:244)
at org.glassfish.jersey.process.internal.RequestScope.runInScope(RequestScope.java:265)
at org.glassfish.jersey.server.ServerRuntime.process(ServerRuntime.java:235)
at org.glassfish.jersey.server.ApplicationHandler.handle(ApplicationHandler.java:684)
at org.glassfish.jersey.servlet.WebComponent.serviceImpl(WebComponent.java:397)
at org.glassfish.jersey.servlet.WebComponent.service(WebComponent.java:349)
at org.glassfish.jersey.servlet.ServletContainer.service(ServletContainer.java:379)
at org.glassfish.jersey.servlet.ServletContainer.service(ServletContainer.java:312)
at org.glassfish.jersey.servlet.ServletContainer.service(ServletContainer.java:205)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:231)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166)
at org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:53)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:193)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:202)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:96)
at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:541)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:139)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:92)
at org.apache.catalina.valves.StuckThreadDetectionValve.invoke(StuckThreadDetectionValve.java:206)
at org.apache.catalina.valves.AbstractAccessLogValve.invoke(AbstractAccessLogValve.java:690)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:74)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:343)
at org.apache.coyote.http11.Http11Processor.service(Http11Processor.java:373)
at org.apache.coyote.AbstractProcessorLight.process(AbstractProcessorLight.java:65)
at org.apache.coyote.AbstractProtocol$ConnectionHandler.process(AbstractProtocol.java:868)
at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1590)
at org.apache.tomcat.util.net.SocketProcessorBase.run(SocketProcessorBase.java:49)
at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136)
at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)
at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
at java.base/java.lang.Thread.run(Thread.java:840)
quentin.leroy January 23, 2025

Thank you @Saif Allah AZZAZA for the follow up. 

It looks like your organisation has restricted the access of the connector to specific projects. It could be the reason why you get an error when the connector is trying to validate the JQL query. 

- Are you be able to generate a connector, without using a JQL query? 

- Can you get in touch with your Jira administrator to know which projects are restricted? 

If it is easier, we can also switch to French :) 

Thanks! 

Saif Allah AZZAZA January 23, 2025

Hello, 

thank you Quentin for your reactivity. My colleagues are able to access query on the same project. I checked that I am within the groups that have access to use PowerBi Connector on jira. It'll be easier if we setup team call to share screen ?

If it is okay for you, we can plan it for the next Tuesday.

Thanks

quentin.leroy January 23, 2025

Yes, we can jump on a call and look at it together.

Here is a Calendly link so you can book a slot with me: https://calendly.com/quentin-leroy-appfire/power-bi-demo 

Looking forward to a productive session! 

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
PREMIUM
PERMISSIONS LEVEL
Product Admin
TAGS
AUG Leaders

Atlassian Community Events