Birst connector to Jira is returning no data

Jira Development Jira Cloud
1

Hello

We are trying to get the data from Jira to Birst and we are able to see the objects in Birst but it is returning no row.

Is there some settings to change, something to do in the token ?

Thanks

2

@RabiaHarriche to see if it has something to do with authentication (i.e. revoked token), try making the API call in a REST client with your creds, or check your logs.

Is this on Jira Cloud or Jira Server/DC?

3

Hi,

Thanks for your answer Neil.
It is on Cloud.

Thanks.

4

@RabiaHarriche It could be one of many things. If you can’t debug it, then any other information you can share about the integration would be handy. For example, if it’s something you built, or built by a third-party… or if it’s using REST API via basic auth, or OAuth 1.0a (application links), etc.

5

Hi

Thanks for your inputs, We tried to connect to JIRA cloud using JIRA connector by giving credential without using token then we got error message as Basic Authentication is deprecated, So we created the API Token and used label as user name and Token as password then we are able to login and see the columns structure but data we are unable to see even with admin access in Jira.

Regards
Prasad

6

Hi @nmansilla ,

We are able to connect and fetch data for most of the objects from Birst except for “Issue” object which is giving below error message. We checked by accessing from other tools also where we are able to get data only if accessed from any particular project else object is throwing error, but from birst its is not working in any method.

org.codehaus.jettison.json.JSONException: A JSONObject text must begin with ‘{’ at character 1 of <!doctype html>HTTP Status 400 – Bad Requestbody {font-family:Tahoma,Arial,sans-serif;} h1, h2, h3, b {color:white;background-color:#525D76;} h1 {font-size:22px;} h2 {font-size:16px;} h3 {font-size:14px;} p {font-size:12px;} a {color:black;} .line {height:1px;background-color:#525D76;border:none;}

HTTP Status 400 – Bad Request

Type Exception Report

Message Request header is too large

Description The server cannot or will not process the request due to something that is perceived to be a client error (e.g., malformed request syntax, invalid request message framing, or deceptive request routing).

Exception

java.lang.IllegalArgumentException: Request header is too large org.apache.coyote.http11.Http11InputBuffer.fill(Http11InputBuffer.java:766) org.apache.coyote.http11.Http11InputBuffer.parseHeader(Http11InputBuffer.java:921) org.apache.coyote.http11.Http11InputBuffer.parseHeaders(Http11InputBuffer.java:594) org.apache.coyote.http11.Http11Processor.service(Http11Processor.java:283) org.apache.coyote.AbstractProcessorLight.process(AbstractProcessorLight.java:65) org.apache.coyote.AbstractProtocol$ConnectionHandler.process(AbstractProtocol.java:868) org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1590) org.apache.tomcat.util.net.SocketProcessorBase.run(SocketProcessorBase.java:49) java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61) java.lang.Thread.run(Thread.java:748)

Note The full stack trace of the root cause is available in the server logs.

Apache Tomcat/9.0.36

Regards
Prasad

7

Hi @SNPrasadGundabolu. Is this Birst integration something that you built, or was is built by a third-party?

8

Hi @nmansilla

We are using default JIRA cloud connector available in Birst and didn’t built anything else.

Regards
Prasad