Issue Summary

XML export of issue is missing the value from Asset Custom field.

Steps to Reproduce

1. Install a Jira Service Management Data Center version above 10.5.0 (replicated on v10.5.0, v10.5.1, v10.7.0).
2. Create an Assets Schema, Object Type and Objects
3. Create an "Assets Object" custom field and add to the screens. Configure the context of custom field to get objects from the schema created earlier.
4. Create an issue with a value selected for this custom field
5. From issue view, use the Export menu --> XML.

Expected Results

The XML export provides values of all issue fields including the Assets Object custom field

Actual Results

The XML export missing the value of Assets Object custom field. As we can see here, the field value is empty. Other export options (Printable and Word) work well and include value.

<customfieldname>assets_field1</customfieldname>
<customfieldvalues>
<customfieldvalue/>
</customfieldvalues>

The below exception is thrown in the atlassian-jira.log file:

025-07-07 16:59:25,178+1000 http-nio-9121-exec-19 url: /si/jira.issueviews:issue-xml/SM4-19/SM4-19.xml; user: binoy WARN binoy 1019x7666x1 1t8rq4f 0:0:0:0:0:0:0:1 /si/jira.issueviews:issue-xml/SM4-19/SM4-19.xml [velocity] Invocation blocked as method is not allowlisted: com.riadalabs.jira.plugins.insight.services.model.InsightObject#toString()

Workaround

• Please make sure to test it on non-prod environment before applying on Prod:
• Take backup of the file $JIRA_INSTALL/atlassian-jira/WEB-INF/classes/velocity-default.properties
• Edit the file and locate the property: introspector.proper.allowlist.methods
• Add the blocked method in the correct format. In this case, com.riadalabs.jira.plugins.insight.services.model.InsightObject#toString()
• Save the file.
• Restart Jira and the changes will take effect after a Jira restart.