Do not input private or sensitive data. View Qlik Privacy & Cookie Policy.
Skip to main content

Announcements
Qlik and ServiceNow Partner to Bring Trusted Enterprise Context into AI-Powered Workflows. Learn More!
cancel
Showing results for 
Search instead for 
Did you mean: 
greg_lag
Contributor III
Contributor III

Qlik jira connector - 410 error message

Hello

I was sucessfully using qlik jira connector. But since few days there some error start to appear. It seems that I'm not longer able to retrieve list of issues. What is strange, is that I'm still able to retrieve for example list of projects. When I'm trying to retrieve issues I'm experiencing error message "The remote server returned an error : (410) Gone.

Did you have some similar issue - it is connection with jira cloud using qlik jira connector.

 

Labels (1)
20 Replies
hugo_andrade
Partner - Specialist
Partner - Specialist

Hi @greg_lag ,

My first reaction is that Jira index might be still have some deleted issues.

So when Qlik tries to load them, they are not returned.

Try this as an immediate measure to generate your reports. Add the following code before you load your Jira data:

SET ErrorMode = 0;

This will modify the error mode within the app, and if it finds an issue with a particular item, it will throw the error, but continue executing the script.

This will help you and the data should be good.

Let me know your results. Also, try to validate using JQL if possible.

I'm a certified Jira Administrator, but not excellent in JQL... But I can try to help you build the query to validate the results coming from Qlik. OK?

Live and Breathe Qlik & AWS.
Follow me on my LinkedIn | Know IPC Global at ipc-global.com

greg_lag
Contributor III
Contributor III
Author

In my opinion it seems that after some changes in jira cloud - qlik connector to jira stops to work totally.

As you can see in attachment my script is as easy as possible. JQL is as easy as possible. 

It looks like problem how qlik connector internally is sending request to jira i think

linero3101
Contributor II
Contributor II

Hola Greg. 

Me ocurre lo mismo desde el día 02/09/2025.

He hecho las siguientes comprobaciones:

1. Permisos de usuario. 

2. Crear conexión de nuevo con el usuario incial y otros usuarios administradores.

3. He creado un conector con REST que en postman sí nos devuelve datos pero en qlik no. Esto es lo extraño. Y me dice que hay algo en nuestros conectores Qlik que falla. Adjuntos capturas de conexión ok en postman y conexión error con REST en Qlik.

en POSTMAN 200 OK.

linero3101_2-1757066335226.png

en QLIK 

linero3101_3-1757066432674.png

La conexión al crearla no da ningun problema. Es al intentar recargar los datos cuando sale este error:

linero3101_1-1757066194206.png

 

 

 

greg_lag
Contributor III
Contributor III
Author

I'm wondering if anyone from Qlik is monitoring this thread and there is plan to fix this issue with JIRA connector? Does any one knows if qlik developers are monitoring this threads? Or is any way to raise an issue to this connector directly to qlik developers?

hugo_andrade
Partner - Specialist
Partner - Specialist

Hi team, 

Jira deprecated the Search API. I've found the link below on a thread. Might need to change the code used.

https://community.atlassian.com/forums/Jira-questions/Clarification-on-Deprecation-of-rest-api-3-sea...

and the Deprecation Notice: https://developer.atlassian.com/changelog/?utm_source=postoffice&utm_medium=in-product&utm_sfdc-camp... 

Live and Breathe Qlik & AWS.
Follow me on my LinkedIn | Know IPC Global at ipc-global.com

hugo_andrade
Partner - Specialist
Partner - Specialist

@greg_lag and @linero3101 ,

I've just created a new connection to Jira and started pulling data using the built-in connector.

Look at the new parameter on the code below: useLegacySearchApi = 'false'

This showed up automatically when I inserted script, which aligns with my previous comment on the Search API deprecation.

[Issues]:
LOAD key as [Issues.key], 
fields_summary as [Issues.fields_summary];
 
[Issues]:
LOAD key as [Issues.key], 
	fields_summary as [Issues.fields_summary];

SELECT key,
	fields_summary
FROM Issues
WITH PROPERTIES (
projectIdOrKey='SUPPORT',
createdAfter='',
createdBefore='',
updatedAfter='08-09-2025',
updatedBefore='',
customFieldIds='',
jqlQuery='',
maxResults='',
useLegacySearchApi='false'
);
 

Live and Breathe Qlik & AWS.
Follow me on my LinkedIn | Know IPC Global at ipc-global.com

greg_lag
Contributor III
Contributor III
Author

Hi, I've just checked and it seems that in my case adding this >>useLegacySearchApi='false'<<

doesn't change anything (with and without this i'm receiving 410 erro). Is it possible that I have older version of qlik to jira connector on server? 

hugo_andrade
Partner - Specialist
Partner - Specialist

@greg_lag , 

Yes, it could be.

But also the query itself.

Try one thing for me. Avoid using the Search parameter.

While calling for the issues on a project, just pass the Project Key = 'GDC' and let's see how it goes.

[Issues]:
LOAD key as [Issues.key], 
	fields_summary as [Issues.fields_summary];

SELECT key,
	fields_summary
FROM Issues
WITH PROPERTIES (
projectIdOrKey='GDC',
createdAfter='',
createdBefore='',
updatedAfter='08-09-2025',
updatedBefore='',
customFieldIds='',
jqlQuery='',
maxResults='',

);

Live and Breathe Qlik & AWS.
Follow me on my LinkedIn | Know IPC Global at ipc-global.com

greg_lag
Contributor III
Contributor III
Author

With this properties unfortunatly exectly the same : Failed on attempt 1 to GET. (The remote server returned an error: (410) Gone.)

Suhr
Contributor II
Contributor II

I updated the QlikSense Server to the latest release (May 2025 SR5) and it fixed the problem for me. So it may be an outdated connector.