Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 12 Next »

This feature is disabled by default and it must be explicitly enabled by copying a library (jar file)  somewhere in the file system


We strongly recommend using our SQL+JQL Driver as data source to access to the Jira data, However, some times organizations might require to access to the Jira database directly. A JDBC Driver is supported for this. Read how to:


First, develop a report against the Jira database remotely by using the database vendor's JDBC Driver. Example for PostgreSQL:



Once the report is finished and remotely working from the Eclipse Report Designer, download and copy the JDBC driver below to somewhere in the Jira host filesystem readable by the OS user running the Jira service:

jira-db-driver.jar

Then reference the driver above from your BIRT report as described here and change the data source configuration to:


  • Driver Class: com.kintosoft.jira.birt.JiraDBDriver

  • Database URL: jdbc:jira-db:

  • Username:

  • Password:


Upload the BIRT report to Jira.


The report will take a connection from the Jira database connection pool (the same connections that are used by the Jira application internally)

Of course, you can use the database vendor's JDBC driver instead. This approach has some drawbacks and advantages compared to our JDBC driver. The advantage is that the database administrator can provide a database user with limited access to the data model (read-only and with reading privileges for some tables only, for instance). The drawback would be that it might require to include the users' credentials (username & password) in the BIRT report to access to Jira database connection. You have to evaluate the pros and cons and make the right decision for your organization.


  • No labels