Issue Summary

Assets textarea attributes fail to render over Jira Issue view in Assets custom field after upgrading JSM from version 5.13 or lower to version higher than 5.13 when Assets contains objects where object ID and object key not aligned.

Steps to Reproduce

1. Upgrade JSM from version 5.15 or lower
2. Over the Assets schemas objects exists having textarea attributes.
3. The above objects have object ID and object key misaligned due to changes in Insight version 5.5.5.
4. There is an Assets custom field that is set to show this textarea attribute over the Issue view.
5. Browse the Issue view for one issue pointing to the abive objects and notice that the textarea attribute do not render (blank).

Expected Results

After upgrade the textarea attribute should render in Issue view custom field

Actual Results

The textarea attribute do not render and looks blank in custom field in Issue view

In the browser console logs can be found an error. Here as an example the TextArea attribute ID is 297 and the ObjectId is 121:

Could not find the element to mount the renderer. The selector is '#customfield_10230-val [data-key$="121"] #rlabs-text-area-attribute-value-297'
push.3497.d.a @ batch.js:49021

NOTE:

In the previous version, when we implemented the integration for the AKRenderer for the Jira Issue View with Assets custom fields, we introduced a selector that is intended to work for attributes. The original implementation of the selector used the object ID.

const selector = `#${customfieldValueId} [data-key$="${objectId}"] #rlabs-text-area-attribute-value-${objectTypeAttributeId}`;

However this proved to be invalid because the object ID and its object key are not aligned. This has caused the code to fail because the element could not be found in the DOM to mount and render the attributes. In addition to this, there could be potential cases where multiple objects on the same custom field, whose IDs are both partially matched, such that the selector would pick up both data-key attributes as a match.

Workaround

Currently there is no known workaround for this behavior. A workaround will be added here when available

Versions Tested