This resolves the problem of embedding the database user's credentials in the BIRT reports in production. Thanks to this special driver, the database credentials are no longer necessary and the BIRT report can reuse the Jira database pool in production while the BIRT report developers can use their own database users for developing. This is very easy to check since BIRT reports are text files by simply searching for the jdbc connect string: "jdbc:jira-db:". In addition, this feature is disabled by default and requires that someone copies the special driver into some directory in the Jira host.
Anyway, 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:
...
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.