Issue Summary

Rovo Chat cannot surface information from the "General" tab of Jira Assets object types. Specifically, the Name, Description, and Icon fields configured at the object type level in Assets schema configuration are not indexed by Rovo and therefore not returnable via natural language search.

Tested on: adobe-summit-2026.atlassian.net
Schema: Application Portfolio (ID: 34)
Object Types tested: Business Capability (37), Application (38), Categories (73)
Assets Workspace ID: a8c0ca2c-8d9d-4dfe-8747-8caa981191a2

Steps to Reproduce

1. Navigate to Jira Assets on your site
2. Open an object type configuration page (e.g., /jira/assets/configure/object-type/37)
3. Add a meaningful description in the General tab and save
4. Open Rovo Chat on the same site
5. Ask: "What is the Business Capability object type?" or "Describe the Application asset type"

Expected Results

Rovo Chat returns the description configured in the object type's General tab, allowing users to ask natural language questions about their Assets schema structure.

Actual Results

Rovo Chat returns no information or a generic response. It cannot surface object type descriptions even when explicitly configured in the General tab.

Root cause hypothesis: Rovo's Assets indexing pipeline calls the Assets object query API (/object/aql) to index asset instances, but does not call the object type metadata endpoints:

GET /jsm/assets/workspace/{workspaceId}/v1/objecttype/{id}
GET /jsm/assets/workspace/{workspaceId}/v1/objectschema/{schemaId}/objecttypes/flat

These endpoints return the name, description, and icon for object types — the exact data shown in the General tab — but appear not to be included in Rovo's indexing pipeline.

Workaround

Currently there is no known workaround for this behavior. As a partial mitigation, rich descriptions can be added to individual asset objects (instances) within each type, which Rovo does index. However, this does not surface the object type-level description from the General tab.