Release Date: 2021-03-22

Who should care about this Update: Jira Administrators

Backstory

If you’re like us, you might be a little behind on all of the updates for Insight – Asset Manager. Yes, some of it is due to procrastination but mostly it’s been due to a fear of just clicking that “Update” button.  If you saw this, wouldn’t you hesitate too?

“Before upgrading to v8.7, read the preparation guide here.”

Prerequisites

First things first. When you click the “here” link you’re greeted with an announcement banner telling you that “Insight is now part of Jira Service Management Data Center. View the latest documentation“. If this is news to you, take a moment and familiarize yourself with what this might mean to your organization.  Especially if you’re considering migrating from Server to Data Center soon.

More and more Jira Administrators need to do a little homework before they’re sure they can update their add-ons (apps). Some require updating the add-on’s database beforehand while others just want you to confirm your application’s or database’s versions. According to Mindville we had these things to verify (https://documentation.mindville.com/display/INSSERV/Preparing+for+Insight+Version+8.7):

  • Server customers need to upgrade the Universal Plugin Manager (UPM) to the latest version, in order to see the license details.
  • There is no other specific preparation you need to do to upgrade to Insight 8.7. However, if you are upgrading from any version below Insight 8.4 it’s very important that you follow the 8.4 preparation guide.
  • Specific to the 8.7 version – If using MySQL, make sure to upgrade your database driver to a 8.x version. You can find them here: https://dev.mysql.com/downloads/connector/j/

Wasn’t it the UPM’s job to make sure something is ready to be updated? How hard is it for Atlassian or the Add-on Vendor to write code that can check if you’re using MySQL instead of PostgreSQL? Or to find out what database driver version you have installed? Moving on.

Release Notes

Version 8.7.7  Released 2021-03-22 – Bug Fix Release

v8.7.7 is mostly Bug Fixes and they’re the same on Data Center as they are on Server

  • Fixed an issue where checking the option “Process data sources via temp file during imports” was not set in the UI.
  • Fixed an issue where object schema managers couldn’t add users in the role section.
  • Improved the re-index process.
  • Security Updates

Should You Update?

Yes, sure, but make sure you meet all of the prerequisites or you’ll be performing a roll-back and probably a database restore to boot.

NOTE: It should go without saying that add-on updates are changes that can effect your suite’s functionality and your employee’s productivity. Use proper Change Management processes, research, and testing before doing any upgrades or updates to a production instance.

 

Has it been awhile since you last updated?

Here’s a synopsis of updates, in REVERSE chronological order, that you may have missed over the past 3+ months.
As usual we’ve highlighted those that you might want to take note of.

Version 8.7.6  Released 2021-03-08 – Bug Fix Release

  • Fixed an issue where exporting objects using encoding, other than UTF-8, ignored the users choice.
  • Improved performance when doing object schema export to minimise risk for Java OutOfMemory exception.
  • Fixed an issue where moving an object removed all inbound references.
  • Fixed an issue where users with object type developer permission couldn’t choose users in a user attribute field when creating or editing objects.
  • Fixed an issue where object showing in User Profile, did not expand and it was not possible to navigate to the Object Page.
  • Fixed an issue where automation actions with multiple values in a placeholder didn’t add all the values.
  • Fixed an issue where the condition in an automation rule was ignored.

 Version 8.7.4  Released 2021-02-18 – Bug Fix Release

  • Fixed an issue where object showing in User Profile, did not expand and it was not possible to navigate to the Object Page.
  • Fixed an issue where board configuration loaded empty page.
  • Fixed an issue where customers, in rare cases, couldn’t pick correct objects in Insight custom field in the customer portal.

Version 8.7.3  Released 2021-02-11 – Bug Fix Release

  • Fixed an issue where users with schema developer permissions could not create/edit objects with user attributes.
  • Fixed an issue where users with schema developer permissions could not bulk edit
  • Fixed an issue where hidden inherited attributes was cleared when users edited objects without permission for the hidden attribute.
  • Fixed an issue where the insight custom field in customer portal would change place whenever an issue was edited. 
  • Fixed an issue where object showing in User Profile, did not expand and it was not possible to navigate to the Object Page
  • Fixed an issue where exporting objects with multiple references was missing delimiter.
  • Fixed an issue where exporting parent object types were not exporting inherited objects.
  • Fixed an issue where inbound references from inherited attributes was not showing the reference type in the new object page.
  • Fixed an issue where it was not possible to edit objects in new object page for objects with attribute type URL that has a multiple cardinality
  • Fixed an issue where exporting filtered objects with references, in the object search page, was not displaying correct data.
  • Fixed an issue were IQL search with Key as placeholder did not return objects in the new object page.
  • Fixed an issue where mentions on the new object page did not trigger notification
  • Fixed an issue where scheduled imports did not run 

Version 8.7.2  Released 2021-02-03 – Bug Fix Release

  • Security update
  • Fixed an issue where board configuration loaded empty page

Version 8.7.1  Released 2021-02-02 – Feature/License Change Release

  • Changes to allow DC customers use the app at no cost

Version 8.6.15  Released 2021-01-26 – Bug Fix Release

  • The import security has been refined so that all import types, except LDAP and Database imports, can be handled by schema managers. LDAP and Database imports are still restricted to Jira administrators.
  • Fixed an issue where board configuration loaded empty page
  • Fixed an issue where insight objects were not visible in service desk customer portal.
  • Fixed an issue where mentions with @ on Object Page did not trigger a notification to the user.
  • Fixed an issue where running a scheduled import manually, with http request as action, failed.
  • Added support to anonymise users.

Version 8.6.13  Released 2021-01-12 – Bug Fix Release

  • Fixed a Discovery import issue where objects was not referencing according to the reference mapping, in some cases
  • Fixed an issue where objects with inherited user attribute was not showing on the users profile
  • Improved performance on User attributes with strict equal operator
  • Fixed an issue where adding empty groups to Roles displayed an alert wrongly.
  • Fixed an issue where schema managers could not create objects with user attribute in object picker
  • Minor fixes
  • Security updates

Version 8.6.12  Released 2020-12-14 – Bug Fix Release

  • Fixed an issue where mapping identifier for reference attributes during import caused creation of duplicate objects
  • Other Minor fixes

Version 8.6.11  Released 2020-11-30 – Bug Fix Release

  • Fixed an issue where the outbound references were not removed even when the “Missing Objects” field was configured correctly
  • Fixed permission issues in Automation
  • Fixed errors with long IQL queries while exporting objects
  • Fixed an issue where creating an object through the custom field on issue screens resulted in errors
  • Improvement to support IQL date time functions in “Attribute Value” automation action
  • Fixed an issue with template imports
  • Fixed an issue were Groovy script in Automation did not update multiple values
  • Fixed an issue where objects are not deleted in CSV imports
  • Fixed an issue where the option of creating a predefined import configuration was missing
  • Performance improvements and UI bug fixes
  • Other bug fixes and improvements
  • Due to security updates, only Jira Administrators can view and configure import configurations