Skip to content

Rovo

AutoPage ships a Rovo agent called AutoPage Assistant. It summarizes a complete Jira work item — its details and its discussion — and answers directly in the Rovo chat.


There are two ways to summarize a work item:

The Card Macro shows a Summarize button when the Summarize option is enabled in its configuration. Clicking the button opens the Rovo chat with the AutoPage Assistant, pre-filled with the connected work item’s key.

The button is only displayed when Rovo is available on the site and the viewing user has a Jira licence.

Open the Rovo chat, select the AutoPage Assistant agent, and ask it to summarize an issue — for example by using the suggested starter:

Summarize DEV-123

Replace DEV-123 with the key of the work item you want summarized.


The agent fetches the complete work item and writes a concise summary structured as follows:

  • What the work item is about and its current state
  • The key decisions from the discussion
  • Open questions and action items

The source data includes the issue details (summary, status, type, priority, assignee, reporter, created/updated dates, labels, and description) together with the external comments (author, date, and text).

Only external comments are included. A comment is treated as internal — and excluded from the summary — when either of the following applies:

  • It is a Jira Service Management agent-only comment (jsdPublic is false).
  • It has a visibility restriction set (a role or group can see it).

This matches the behaviour of the Comment Macro.

If the work item has no (external) comments, the agent summarizes the issue details alone and notes that there is no discussion yet.


The work item is loaded with the permissions of the user who asked the question. A user who cannot open the work item in Jira receives a clear error instead of the summary. Internal comments are filtered out before the content reaches the agent, so restricted comment text is not included in a summary.


To create a summary, the work item’s details and external comments are processed by Atlassian Rovo. Review your site’s Rovo and data-residency configuration if your organization has strict data-processing requirements.