Assets script methods changes with Java 17

General Questions
,
1

We asked in this ticket EASE-45324 if there were any script changes/deprecations we had to have in mind when upgrading Jira and Exalate to Java 17 and the Exalate support told us there was nothing to worry about.

We later created this ticket EASE-45328 since we were in fact having problems.
We noticed that a script involving Assets fields stopped working.
This particular line:
def exalateAttribute = firstObject.objectAttributes.find { (it.objAttributeTypeId.toString() == “138”) }
Was failing with this error:
”No such property: objectAttributes for class com.riadalabs.jira.plugins.insight.services.moder.MutableObjectBean

This script was working eprfectly fine before the upgrade.
We requite help.
Thanks,

Alvaro H.

2

Thanks for sharing the details and error message. When upgrading Jira and Exalate to Java 17, some Groovy scripts—especially those interacting with third-party apps like Assets (formerly Insight)—may break due to changes in underlying APIs or stricter Java/Groovy compatibility.

The error you’re seeing:

No such property: objectAttributes for class com.riadalabs.jira.plugins.insight.services.moder.MutableObjectBean

suggests that the objectAttributes property is no longer available or has changed in the Assets API after your upgrade. This is a common issue when Jira or its plugins are updated, as their internal models can change.

Here’s what you should do:

  • Check the Assets (Insight) API documentation for your current Jira version to see if the property or method to access object attributes has changed. Sometimes, properties are renamed or replaced with getter methods.
  • Update your script to use the new way of accessing attributes. For example, you might need to use a method like getObjectAttributeBeans() or similar, depending on the new API.

Exalate’s documentation doesn’t provide direct support for third-party app APIs, but it does recommend keeping your external scripts up to date after upgrades. See: Updating External Scripts to be Compatible with Exalate 5.2.2 Onwards.

Next steps:

  1. Review the Assets/Insight API for your Jira version to find the correct way to access object attributes.
  2. Update your script accordingly.
  3. If you’re unsure about the new API, you may need to consult Atlassian’s Assets documentation or reach out to their support.

If you need help updating the script once you know the new method/property, feel free to share the updated API details and I can help you adjust the code!

3

I have already updated the line to:
def exalateAttribute = firstObject.getObjectAttributeBeans().find { (it.objAttributeTypeId.toString() == “140”) }

And now I get this error:
No such property: objAttributeTypeId for class: com.riadalabs.jira.plugins.insight.services.model.MutableObjectAttributeBean

In the payload of the issue, I see that indeed the way to get the attributes is objAttributeTypeId, so I do not get what I should change.
Thanks.

4

Hi @ahonorio ,

Apologies for the inconvenience caused here but indeed, the upgrade should not break this. But it is impossible to troubleshoot the issue without the full script. The actual problem is in the lines preceding the line you pasted. So, please share the full script that you are using, and also share the full error trace, and I will be happy to test this for you to see why this is not working.

Thanks
Majid