What’s New – ScriptRunner for Jira Server v6.23.0

Release Date: 07 April 2021

Who should care about this Update: Jira Administrators

Reference Link: https://docs.adaptavist.com/sr4js/latest/release-notes/release-6-x 

New Features:

New Workflow Functions!!!!!

In this release Adaptavist has added the following new workflow functions:

 Click their links for more information on how to use them.

 

 

Bug Fixes:

There were several good bugs fixed on this release, including:

  •  Select Lists slow to open when there are lot of items to display
  • Copy Project has problems if the project in question has sub-tasks that need to be copied
  • Cloning Issues don’t get created when the issue type in question doesn’t exist in the destination project 
  • and if the Drop-down options of the Context Field have more than 3 lines of information, they will overlap each other.

Screenshot 2021-03-23 at 9.18.52 PM.png

 

And our favorite, (that still appears to be broken as of the time of this post)

  • Checkboxes in Automation for Jira are hidden when ScriptRunner is Enabled. 

We expect this last one to get fixed eventually, but until then, go here to follow these Steps to Reproduce if you’re curious: https://productsupport.adaptavist.com/browse/SRJIRA-5012  

 Should You Update?

Yes, Absolutely.

What’s New – ScriptRunner for Jira Server v6.22.0

Release Date: 24 Mar 2021

Who should care about this Update: Jira Administrators

Reference Link: https://docs.adaptavist.com/sr4js/6.22.0/release-notes/release-6-x 

New Features:

None

Bug Fixes:

There were two bugs fixed in this release. The first is only applicable for those of us using javax.xml.stream.XMLInputFactory when constructing the XML parser for behaviors configuration data and Adaptavist has fixed this bug. See https://productsupport.adaptavist.com/browse/SRJIRA-5097 for more information.

The other bug is a bit more interesting…

Did you know that if you uninstall an add-on that uses a custom field on a Screen, Jira’s API still maintains a reference to that custom field’s ID even though it doesn’t exist? This can also happen when the add-on isn’t just uninstalled, but even if it’s disabled. The reference to it still exists in the API.

The (now) invalid custom field ID is used to lookup the custom field, which fails causing an exception error to be thrown when attempting to retrieve the field name.

v6.22.0 fixes this “Bug”.

How do you know if you’re effected by this Bug?

Here are the Steps to Reproduce

  • Add a ScriptRunner scripted validator to a workflow transition with a screen.
  • Install a third party custom field app (e.g. Watcher custom field).
  • Add a custom field provided by the app to the tab configuration for the screen configured for the transition from the above step.
  • Disable the app providing the custom field.
  • Execute the workflow transition and check for the exception.

 Should You Update?

Yes.

What’s New – Insight Asset Manager for Jira Server v8.7.7

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

 

What’s New in ScriptRunner for Jira v6.21.0

Release Date: 10 Mar 2021

Who should care about this Update: Administrators

Reference Link: https://docs.adaptavist.com/sr4js/6.21.0/release-notes/release-6-x/release-6-21-x

New Features:

The Headliner New Feature:

Besides these usual Bug Fixes and a few requested new features, the big What’s New is what Adaptavist has done with their workflow functions. They’ve been moved and are now visible alongside all the other Jira workflow functions.

See https://docs.adaptavist.com/sr4js/6.21.0/features/workflows for a very helpful animation on how to use this new Feature.

 

How to Use this New Feature:

  1. From the Administration Cog, go to Manage Apps
  2. As in previous versions go to ScriptRunner Console, Workflows.
  3. Click Create Workflow Function
  4. Once configured, proceed to Administrator > Issues > Workflows and edit your workflow in Diagram View.
    Access the transition and select Conditions, Validators or Post Function and create your new action.
    Your new workflow function will be available alongside all the other functions in the Jira Workflow Edit screens.

Should You Upgrade?

Definitely. This new update will make your job of creating and then implementing workflow functions a LOT easier.

 

What’s New in Tempo Timesheets for Jira Server 11.3.0

Release Date: 09 Mar 2021

Who should care about this Update: Tempo Administrators

Reference Links:

New Features:

  • Bug Fixes; and
  • It is now possible to filter users by Tempo Program IDs (a Program is a collection of Tempo Teams) in the Manage Staff page.

Upgrading from a version prior to 11.0?

Heads Up.  With the latest major version of Tempo Timesheets (v11.0.0) features changes to the Jira SPI and Jira REST API. This results in the Tempo Team custom field being returned as an object rather than as a string and also makes it possible to update the Jira SPI with an object. While it is still possible to use the existing Jira REST API endpoints to update the team custom field with name or ID, it is no longer possible to use the Jira SPI to do so. 

The goal in making these changes is to give you more flexibility when integrating with the Tempo Team custom field through the Jira SPI and API interfaces, and to allow those of you who use these interfaces to simplify your third party integrations. These changes will return a Team object that includes both the team name and the team ID (instead of just the team ID), which will allow you to access more information when you use the Jira SPI and REST API interfaces.

The Main Take-Aways?

  1. Please note that these changes may have an impact on third party apps and integrations within your organization. We recommend that you confirm that your critical third party apps are compatible with this change before upgrading.
  2. If you’ve built any ScriptRunner scripts referencing the team custom field, you will likely need to update them.

You can find more technical information about these changes here. Tempo has compiled information to help you understand how to update the team custom field in ScriptRunner scripts.

Other Improvements Include:

  • Tempo Team custom field is now returned as an object (rather than a string) that includes both the team name and the team ID.
  • CSV exports of Jira issue data now include team name instead of team ID in the Team field. This applies to data exported to CSV from Tempo’s Logged Time report as well as data exported to CSV directly from Jira.
  • Deprecation warning: Private endpoint rest/tempo-core/1/users/search is being deprecated and slated for removal.

Should You Upgrade?

YES, this upgrade is a minor one.

But if you’re coming from before v11.0.0 we always recommend testing your update in a sandbox environment first to make sure your changes don’t conflict with other add-ons or break any customizations or integrations you currently have in place.

Good Luck!

What’s New in ScriptRunner for Confluence v6.21.0

Release Date: 10 Mar 2021

Who should care about this Update: Confluence Administrators

Reference Link: https://docs.adaptavist.com/sr4c/6.21.0/release-notes/release-6-x/6-21-x

New Features:

Well, this is a first. Adaptavist has published a major version release just to update in-app documentation links to point to their new documentation site. No bugs, no other features, just a documentation link update.

From their website: “Welcome to the new documentation site! We don’t have any major changes in this ScriptRunner for Confluence release, but we have updated the in-app documentation links to point here.”

I suppose there are worse reasons to create a release.

Has it been awhile since you last upgraded?

 

 

If so, from Adaptavist’s NEW documentation site, here’s a synopsis of what you may have missed along with some of the newest headline features:

  • v6.20.0 – https://docs.adaptavist.com/sr4c/6.21.0/release-notes/release-6-x/6-20-x
    • Script Editor New Feature – The compile context in the Script Editor is now set when open opening it from an edit page.
    • Manage Labels Built-In Script – The Bulk Add/Remove Labels on One or ore Pages and Rename Labels scripts have been removed, and the functionality has been combined into the new Manage Labels built-in script. Using this script, you can rename, add, and remove page labels in bulk. The script is available for Confluence administrators and space administrators.
  • v6.19.0 – https://docs.adaptavist.com/sr4c/6.21.0/release-notes/release-6-x/6-19-x
    • Just Bug Fixes
  • v6.18.0 – https://docs.adaptavist.com/sr4c/6.21.0/release-notes/release-6-x/6-18-x
    • Notifications Control for Copy Page Tree Space Administration – The Copy Page Tree built-in script for space administrators is the latest to be updated. Using the Notifications checkbox, choose if you want to send a notification to users when copying the page tree from Advanced Space Functionality
    • Other New Feature: Now you can configure LDAP resource environment properties.
  • v6.17.0 – https://docs.adaptavist.com/sr4c/6.21.0/release-notes/release-6-x/6-17-x
    • Integration with Slack – Adaptavist has added a new resource type representing a connection to Slack. That, plus a simple API, allows you to message users and channels from within your event listeners and other extension points.
    • New Bulk Delete Attachment Versions Built-In Script – A new script was added for Confluence space administrators to delete old attachment versions.
    • Notifications Control for Copy Page Tree – Adaptavist is continuing to add more detailed notifications control to our built-in scripts. The Copy Page Tree built-in script is the latest to be updated. Using the Notifications checkbox, choose if you want to send a notification to users when copying the page tree.
  • v6.16.0 – https://docs.adaptavist.com/sr4c/6.21.0/release-notes/release-6-x/6-16-x
    • Better Handling for Templates in Create Page Macro – In this release, ScriptRunner has improved support for using templates with the Create Page macro. When you select a template as the source to create a page and that template contains variable expressions, users will be directed to a form to provide values for those variables first.
  • v6.15.0 – https://docs.adaptavist.com/sr4c/6.21.0/release-notes/release-6-x/6-15-x
    • Bulk Delete Attachment Versions – A new script was added for Confluence administrators to delete old attachment versions.

Should You Update?

No. Not unless you’re coming from a much older version and/or you use their in-app documentation a lot.

What’s New – Configuration Manager for Jira Server v6.8.1

Release Date: 2021-02-12

Who should care about this Update: Jira Administrators

New Features:

Version 6.8.1 • Released 2021-02-12

New Features:

  • Option to change the ranking strategy
  • Compatibility with Jira 8.15 and Jira Service Management 4.15
  • +Bug fixes

The Headliner New Feature

Just like clockwork and true to form, Botron always has something new every month for us admins to use for our deployments and/or migrations. For this month’s newest feature Botron has added an option that allows us to change the ranking strategy during the deployment. Cool, huh? 

But why would you do this and when?

First, we need to understand ranking. Ranking is the order of issues in your Jira instance and it’s a Global setting. Meaning, if you have issues ordered by one method in one board, they’ll maintain that method in all other boards.

Normally, when you create a snapshot in preparation for a deployment, Configuration Manager exports the rank values for all the issues based on each ranking field. Then, when you deploy the snapshot, Configuration Manager assigns new ranks to all of the imported issues based on these exported values. By default, Configuration Manager for Jira updates the ranking for all fields on the target instance based on these exported values. Once the import and ranking updates are complete the subsequent issue indexing will run much faster.

To the New Feature

As of v6.8.1, Botron has added an option in the General Settings called “Do not lock the Lexorank table when ranking issues during deployment“ that allows you to change the ranking method during the ranking phase of deployment.

When you enable this feature, Configuration Manager will not lock any rows in the Lexorank table during the issue ranking phase of the snapshot deployments. Then, issues can be ranked manually during the entire deployment process.  There is a small chance that two or more issues could be assigned an identical rank but this problem can be fixed by manually ranking any of the conflicting issues in Jira after the deployment is finished.

When is this useful?

When doing small deployments on a large live instance.

 

 

Should You Update?

Yes, if…

  • You haven’t updated since 6.7.2 due to the Security Patch
  • You recently upgraded Jira to v8.15 or Jira Service Management to v4.15
  • You need to unlock the Lexorank table so you can rank issues during deployment

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.

Version 6.8.0 • Released 2021-01-21

New Features:

  • Improvements to memory usage when deploying large snapshots
  • Overlapping email channel settings are handled during deployment
  • +Bug fixes

Version 6.7.3 • Released 2020-12-23

Security:

  • Fixes to security vulnerabilities
  • +Bug fixes

Version 6.7.2 • Released 2020-12-05

New Features:

  • Binary snapshots
  • Handling of function parameters in JQL queries
  • Compatibility with Jira 8.14 and Service Desk 4.14
  • +Bug fixes

Version 6.7.1 • Released 2020-10-26

New Features:

  • Project key size check during deployment
  • Improvements to selecting filters/boards/dashboards during snapshot creation.
  • +Bug fixes

Version 6.7.0 • Released 2020-10-06

New Features:

  • Selective Merge for users and groups
  • Deploy a snapshot from Jira’s file system
  • Support for new/omitted system fields in JQL
  • Migration of ranking for multiple ranking fields
  • Support for JSD-specific items in JQL
  • Power Admin 1.7.0
  • + Bug fixes