Description:
Currently, Rovo Agents and "Ask Rovo" cannot natively retrieve or reference specific Jira Service Management (JSM) portal metadata, such as portalId, groupId, or requestTypeId. While Rovo indexes JSM tickets and project descriptions as searchable content, it does not have a mapped understanding of the underlying portal infrastructure required to generate functional URLs or documentation.

Testing in a controlled environment confirms that even when an Agent is explicitly instructed to "use the JSM API," it fails to retrieve these IDs. This is because these values exist as configuration-level metadata in the JSM REST API (/rest/servicedeskapi/portal/) and are not currently indexed in the Teamwork Graph or exposed via a default Agent Action (Skill). Without this, Agents must either admit they cannot find the IDs or risk hallucinating incorrect values to satisfy the prompt.

Enhancement:

1. Native JSM Configuration Action: Introduce a built-in "JSM Portal Skill" that allows Agents to query a project’s Request Type hierarchy, including associated portalId, groupId, and requestTypeId.

1. Metadata Visibility: Expose JSM portal configuration as a searchable entity for Agents, allowing them to accurately identify which Request Types are visible to customers versus hidden.

1. URL Constructor: Enable the Agent to automatically resolve and construct the standard JSM portal URL format (/servicedesk/customer/portal/{id}/group/{id}/create/{id}{}) based on the retrieved metadata.