Changelog

3.6.5

  • Jira 8 support

3.6.4

  • Driver upgraded to the 7.6.4 version

3.6.2

  • FIX: No cubes and other errors with MySQL
  • IMPROV: SQL+JQL Driver upgraded to 7.6.2

3.6.1

  • SQL+JQL Driver upgraded to the 7.1.0 version

3.6.0

  • SQL+JQL Driver plugin packed within: it is deployed as plugin instead of being embedded as library.

3.4.0


The Analytics Client is now packed within the Server app (in previous versions, it was just the opposite)

This allows organizations purchasing a license for the JQL Analytics app at a lower price without buying the SQL for Jira Driver app which is more expensive.

The app is fully backward compatible with the Analytics Client which has been archived on the Marketplace as it is now deployed with the Server.

Customers having purchased the SQL for Jira Driver before July, 31th 2018 can get a perpetual free license for this app. Please contact to our support team!



==============================

3.11-19

  • Fix: saved schemas reference temporary data and they do not work if the Jira's temp directory is cleaned up.
  • Support for Jira Software: A new cube for Jira Software is available from the Agile Boards with support for Epics, Sprints, etc. Please read more details in the documentation

3.11-18

  • New charts supported
  • Performance improved a lot.

3.11-17

  • Fix: Release and Archive version labels exchanged.

3.11-15/16

  • Commercial: it requires purchase a license for the SQL for Jira Driver app. In previous versions a free edition of the Driver app was packed within this app. Unfortunately, this is no longer possible due a lot of reasons (technology and business)
  • All the dependencies are packed and deployed automatically on Jira:
    • Analytics Server (Penatho Mondrian supporting MDX and XMLA)
    • SQL for Jira Driver (H2 supporting SQL+JLQ via JDBC over HTTP) → Requires a valid license (free trial or commercial) to fetch any  data from Jira.
  • Support for Issue Comments (author and creation date)
  • Support for more custom field types:
    • Group (Simple, Multiple)
    • Version (Simple, Multiple)
    • User (Simple, Multiple)
    • Project
    • Label

3.11-14

  • Saved schemes become corrupted
  • No data in the Analytics Console (remote connections)
  • Fixed a number of  minor issues.

3.11-13

  • Fix: Unexpected results. It might not be considered a fix because the results were always correct strictly. However, all the linked issues were included in the cube in addition  to the issues returned by the user's JQL. This might cause a lot of confusion. For example: if a user's wanted to analyze the following JQL: "project = XXX",  and some of the issues in the XXX project was linked to some issue outside the JQL scope (some issue in the YYY project, for instance), those linked issues (YYY) were included in the facts of  cube by default (XXX+linked in YYY). Therefore, if the user asked about the projects in the cube (JQL) the result was XXX+YYY. XXX because the user's JQL and YYY due the linked issues . This is not the expected result. Now, it is possible to ask about linked issues too, but those issues are not included in the cube facts. Users were not aware of linked issues were also included in the facts and therefore they got unexpected results.

3.11.-12

  • Fix: same user working with more than one schema at time might get wrong data intermittently. 
  • Fix: some links go broken in previous version
  • Fix: some attributes had different caption depending the client tool (Saiku, Excel,..)
  • Improv: Some internal parts of the integration with Saiku has been re-engineered.

3.11-11

  • Almost all the issues related to concurrency have been fixed. The most important at least: multiple users working with cubes at the same time might cause severe conflicts: inexact results, global errors and even compromise data privacy under some circumstances. It is highly recommended that all the organizations upgrade to this version ASAP or uninstall any previous version. 
  • ​Performance has also been improved in this version ​by supporting multi threading internally to resolved users' queries more efficiently in heavily loaded environments with large amounts of users.

3.11-10

  • Support for Links
  • Performance improved A LOT
  • Support for multiple Saiku instances running in parallel (an user can now analyze different schemes right within the same user's session).

3.11-9

  • The Mondrian schema template has been re-engineered from the scratch. Now it performs better, it is much easier to maintain, it is much easier to use and it is also capable to relate all the Jira data with no restrictions.

3.11-8

  • Support for custom fields: now, a dialog allows to select the custom fields to be added into the cubes fro analytics...

3.11-6

  • All the dependencies are packed in the app. 
  • It is free (no cost)

3.11-05

  • MAJOR RELEASE: It no longer requires the SQL for Jira Driver. Now, it requires the Analytics Server for Jira app, so it becomes free for use.

3.11-04

  • FIX: Dimension levels not loaded in Jira 7. 4 and above

3.11-03

  • FIX: Plugin does not initialize due a missing resource
  • New branding (Kinto Soft replaced by Marketplace Expert)

3.11-02

  • No longer mandatory to run SQL for JIRA Driver (it requires SQL for JIRA Driver 3.2.0)

3.11-01

  • IMPROV: Java 8 required
  • IMPROV: Saiku upgraded to 3.9 
  • FIX: SQL for JIRA Software/Agile tables raise NullPointerException