SuggestiMate for Jira Release Notes

Version 3.3.3 - October 22, 2020

Jira 8.13 support.

Version 3.3.2 - November 2, 2019

Added functionality of showing similar issues in backlog.

Minor bugfixes.

Version 3.3.1 - September 20, 2019

Jira 8.4 support.

Version 3.3.0 - June 3, 2019

Jira Data Center certified version.

Version 3.2.7 - February 19, 2019

Jira 8 support.

Version 3.2.6 - April 12, 2018

Compliance with the new Atlassian naming guidelines.

Version 3.2.5 - May 12, 2017

Support for multibyte characters improved. This makes SuggestiMate much more useful for non-Latin languages.

Version 3.2.4 - May 3, 2017

A minor fix to overcome UPM license expiration issue in Jira 6.3 and below.

Version 3.2.3 - February 21, 2017

A minor fix for collapsed mode header.

Version 3.2.2 - February 7, 2017

Added ability to restrict suggestions to recently created issues.

Version 3.2.1 - May 1, 2016

Fixed an issue with resource management.

Version 3.2.0 - April 19, 2016

Performance on large projects drastically improved!

Compatibility with Jira Data Center added.

Support for search across multiple projects added.

Client side issue page loading sped up with asynchonous suggestion loading.

Issue type and priority displayed for suggestions.

Version 3.1.1 - March 25, 2016

Fixed an indexing bug introduced in version 3.1.0.

Version 3.1.0 - March 10, 2016

Improved first-time use experience. Custom field is created and configured automatically.

Improved UI for suggestions in collapsed mode.

Improved add-on configuration UI.

Version 3.0.1 - October 8, 2015

Support for Jira 7 added!

Version 3.0.0 - July 11, 2015

We sell via Atlassian Marketplace now!

Enhancera, LLC is the new company behind the tool.

Version 2.2.1 - Aug 6, 2013

Resolved conflict with Compass plugin.

Version 2.2.0 - May 31, 2013

Support for Jira 6 added!

Configuration menu locations are updated to be compatible with newer Jira versions.

Icon and logo added for the plugin.

Configuration is available directly from plugin details.

Version 2.1.4 - Jan 10, 2013

A minor improvement in SuggestiMate code that fixes UPM update check behavior. Now UPM is capable of automatically finding if SuggestiMate is compatible with the Jira version to which you want to update when you perform Jira update check.

Version 2.1.3 - Sep 6, 2012

A very important bug fix released. All users with Jira instances allowing browsing issues to anonymous users are strongly encouraged to upgrade. Due to the bug in version 2.1.0 anonymous users were unable to see suggestions. This is fixed now.

Version 2.1.2 - Apr 9, 2012

Another maintenance release which fixes a couple of UX issues related to Jira 5. If you are still using Jira 3 or Jira 4 you don't need to upgrade.

Version 2.1.1 - Mar 10, 2012

This is just a minor maintenance release which fixes a couple of small issues introduced with our last major release.

Version 2.1.0 - Feb 12, 2012

SuggestiMate is now compatible with Jira 5!

We also made a couple of minor UI improvements that make finding similar issues even easier. The links are nicely aligned and you don't get confirmation requests from browser when clicking links on create issue screen.

Version 2.0.4 - Jun 8, 2011

We improved SuggestiMate in two unrelated areas in this release.

The first one is the way it strikes through the suggested issues. Previously issue status was used to determine if the link should be displayed as striked-through. However Jira in issue links uses a different approach. It checks if there is a resolution and srikes-through the issues with it. So we switched to the same algorithm to be concise with Jira in this aspect.

The second improvement is performance-related. From time to time SuggestiMate refreshes its index. Usually this doesn't happen very often and doesn't take too much time but occasionally a new issue is being added at the time of refresh. Previously you would experience a delay in page display after the issue was created. Now we changed the way new issues are processed while index refresh is performed and there is no delay anymore.

Version 2.0.3 - Apr 12, 2011

A minor bug with summary parsing fixed. As a result of this bug error messages were logged in Jira log on rare occasions.

Version 2.0.2 - Feb 12, 2011

Two minor bugs which don't affect most of our users were fixed. One of them was incorrect license keys for companies with & character in the name. The other was appearance of error messages about incorrect query format in the Jira log.

Both problems had no impact on plug-in and Jira performance. So if you haven't noticed them that's pretty normal and you don't need to upgrade for this version.

Version 2.0.1 - Dec 14, 2010

A small bug related to dealing with open files fixed. This bug caused "Too many open files" error on some Linux machines. The issue is resolved now.

Version 2.0.0 - Nov 16, 2010

We are happy to announce our new major version. SuggestiMate for Jira 2.0 is the same great tool but now it works faster, consumes less resources and produces better results.

We completely rewrote our similar issues search engine to better serve our clients' needs. SuggestiMate has wonderful Apache Lucene under the hood now. This feels like having Ferrari V12 engine.

All good things you knew about SuggestiMate are still there.

Version 1.2.0 - Oct 24, 2010

Jira 4.2 was finally officially released last week. We updated SuggestiMate to support the latest changes in user interface so now Jira 4.2 is officially supported.

We also fixed a very rare but rather annoying bug. In previous versions there could be a situation when a deleted issue would still appear on the list of suggestions. The problem was caused by outdated cache. Fixed now.

Version 1.1.4 - Sep 30, 2010

This version does not fix bugs. Instead it gives more power to our users.

The first change is that now the users of commercial version are able to hide the links to our website from their Jira pages. Yes, you are able to remove those 'Powered by SuggestiMate' links if they annoy you. Please use plugin configuration for this. We ask you not to do it without reason because those links help us to make our work more visible and in the long run improve the quality of our software.

Another feature is that you can now choose which of the two main SuggestiMate features you want to use. You can show similar issues on create issue page only, on issue details page only or on both as you have been doing till now. To choose just go to the configuration and play with 'Show on issue create/browse' options.

One more option for similar issues in issue details view is to display found similar issues in collapsed mode. In this case you see only the total number of issues. If you want to expand the list and view them you should click the header. This saves you space on your issue details page when needed but you don't immediately see related issues. So use carefully.

Finally, if no similar issues are found you see word None instead of blank field now. We hope it makes the result more explicit.

Version 1.1.3 - Sep 4, 2010

The only change in this release is the proper work with security level configuration. Jira lets administrators specify which users are able to see each issue. Previously those settings were ignored by SuggestiMate and it showed to the user summaries of similar issues for which he didn't have browse permissions. Now this problem is fixed.

Version 1.1.2 - Aug 21, 2010

This release fixes the annoying bug from which the users of the trial version suffered a lot. On some systems license checking code failed to assign trial license. Now license checking works fine in all cases.

Version 1.1.1 - Jul 24, 2010

The main improvement in this version is how evaluation start date is stored. There were occasional problems with this on some systems and therefore trial version used to say that it had expired before the user could even try it. We're happy to say that this is fixed now.

We also fixed an issue with the 'Powered by SuggestiMate' link on view issue page which was not displayed in Jira 4.0. We did some work on infrastructure, automated build number tracking, switched to Mercurial for source control, started formal change log and automated version numbering.