3.6.5 (Security fix)

• The packed SQL+JQL Driver has been upgraded (+9.7.0) to fix a critical vulnerability. Please upgrade the SQL+JQL Driver on Jira ASAP (it might require to upgrade the JDBC driver to access remotely)

3.6.4 (Security fixes)

• As a result of deep research to find security vulnerabilities in the app some URLs have been fixed to avoid potential XSRF attacks to Jira administrators. Read more...
• In addition, the packed SQL+JQL Driver has been updated to the 9.6.0 version which also fixes critical vulnerabilities in the Driver.

3.6.3 (Security fix)

• FIX: It was possible to perform an XSS attack from one URL. Credits for Ivan Rumak and Alexey Rumak that reported it via https://detectify.com/. Thank you! 

3.5.4

• Eclipse BIRT remains 100% free at no cost. But the Driver has a dual license (free and commercial) until Jira 9 when only the commercial version will be supported. This version of Eclipse BIRT upgrades the Driver to the 8.0.2 version (← COMMERCIAL!. If you want to run the free version of the Driver, please downgrade it to the latest 7.x version). Of course, if your BIRT reports do not use the SQL+JQL Driver as a data source you are not impacted by this.

3.5.3

• SQL+JQL Driver upgraded to 7.17.0 version. Please read more details from here.

3.5.0

• IMPROV: Support for a new WEB location that allows sharing the BIRT report URL and embedding it into an iframe.
• IMPROV: New action to run reports from the administrator's report listing.

3.4.0

• SQL+JQL Driver upgraded to the 7.14.0 version.

3.3.0

• IMPROV: BIRT Runtime 4.8.0 moved from OpenText to Innovent Solutions. A brief history to understand this change: The Eclipse BIRT project is sponsored by three companies. IBM, Open Text and Innovent Solutions. In early 2015, OpenText acquired Actuate Corporation. Actuate was the leading company developing Eclipse BIRT. Unfortunately, since its acquisition, Open Text made developers' live a lot harder and stopped providing critical parts to integrate BIRT with third-party tools like Jira. Perhaps they thought many developers would stop supporting Eclipse BIRT and this would bring new business opportunities to them. Anyway, we were able to migrate Actuate's BIRT runtime (4.6.0) to OpenText's 4.8.0 versions for Jira which took us a lot of weeks, instead of hours. Fortunately, Innnovent Solutions come to the rescue and published its own version of the Eclipse BIRT Runtime for the 4.8.0 version. Now, we have used the Innovate Solutions version to run Eclipse BIRT on Jira which resolves some bugs too. We expect that replacing the provider of Eclipse BIRT will help to support this app for Jira in the short and long-term.
• FIX: Support for Jira 8.5.0
• FIX: Some graphs are missing from the reports on Jira.

3.2.1

• FIX: reports without author did not work in the previous version

3.2.0

• IMPROV: Reports can now be upgraded by uploading it again. Deleting and uploading a new version is no longer required.
• FIX: Gadgets support scroll bars when the content exceeds the size of the gadget
• Fix: Selecting mode (Run vs Frameset) did not work in recent versions of Jira
• DISC: Pre-built reports are no longer supported.
• CHANGE:
  • Uploading and configuring reports have been revamped. Now, the author, title and description are taken from the report.
  • New configuration policy: now, the reports are shared with none and no locations by default.

3.1.9

• FIx: massive failure displaying reports and others due to a library conflict with Jira

3.1.8

• SQL+JQL Driver upgraded to the 7.13.2 version to avoid not closed connections when accessed remotely via JDBC

3.1.7

• SQL+JQL Driver upgraded to the 7.13.0 version to improve security. Please upgrade ASAP and configure the new global permissions to grant access to SQL+JQL if required.

...

• Security fix: only Jira administrators and explicitly granted users and groups can upload BIRT reports. This is a critical security threat and you must upgrade to this version ASAP. Please read more about this Security Thread Alert!Bulletin

• Rebranding: after contacting to Eclipse.org, our previous app logo and name was not compliant with the Guidelines for Eclipse Logos and Trademarks. So, we have modified them according their instructions.

...