JIRA Connector

With the Qlik JIRA connector allows you to retrieve data from your JIRA projects and project problems and put it in your Qlik Sense or QlikLoad view apps.

Ways to Access Data

To access your JIRA data, you must verify the connector with your JIRA account data. Make sure your credentials contain only ASCII characters. Enter the JIRA base URL you want to connect to and your JIRA username and password. Your credentials are stored on the connector.

Load data from tables

After you verify the connector with your account information, you can use the following tables to select and load data:

Projects
Use this table to get the list of JIRA projects to which you have access.

Problems
Use this table to retrieve the problems in a project. You need the project key or ID to run this table.

WorkLog
Use this table to retrieve work history for a JIRA issue. You need the JIRA release key or ID to run this table.

Comments
Use this table to get the comments for a JIRA issue. You need the JIRA release key or ID to run this table.

History
Use this table to get the history of a JIRA problem. You need the JIRA release key or ID to run this table.

Working with the JIRA API quota limits

De Qlik Web Connectors use the JIRA API to extract data from JIRA and into your Qlik Sense app. While reloading your JIRA-based app, you may receive an error message that the connector has reached the JIRA API speed limit and all subsequent API calls will fail until the connector drops below the throttle limit.

Troubleshooting

You receive an error message that you have reached the API limit.

Possible cause
You have exceeded the API limits set by the JIRA API Qlik Web Connectors are imposed.

Proposed action
To reduce the impact of reaching the API speed limits, develop your app with the following in mind:

• Extract only the data you need.
• Reload one JIRA-based application at a time.
• Make sure that loops in your script that make API calls don't lead to infinite loops.

You cannot verify the connector with your JIRA credentials.

Possible cause
Your JIRA login, your JIRA password, or both contain non-ASCII characters.

Proposed action
Try to change your login details via your JIRA account or use a different JIRA account.