Problem / Use Case

Rovo agents can already read Jira issues and Confluence pages and return synthesized answers in natural language. However, they can't generate a new PowerPoint (.pptx) file.

Many enterprise teams rely on recurring slide-based status reports (e.g., weekly project updates, release review, risk/issue reviews) for stakeholders who aren't in Jira every day. They'd like to ask a Rovo agent to read Jira issues, Confluence pages, and automatically generate an editable PowerPoint deck they can share and collaborate on with their team.

 

Today, users can get a good narrative from Rovo, but still have to manually rebuild that content in PowerPoint on a regular cadence.

Current Behavior

• Rovo agents:
  • Can read Jira issues and Confluence pages within the user's permissions
  • Can summarize, analyze, and structure the information in chat (e.g., can produce narrative, bullets, tables).
  • Can write back to Jira or Confluence depending on the configured actions.
•  Rovo agents can't:
  • Produce any new or attach a .pptx file as an outcome.
  • Map their output into slide-level sections (e.g., summary, metrics, risks, next steps).
  • Reuse any kind of standard slide template for reports.

Suggested Solution

Introduce a capability for Rovo agents to generate an editable PowerPoint (.pptx) file as part of an agent run. For example:

1. Input / context{}

• The agent is invoked with:
  • A set of Jira issues defined by a JQL query, saved filter, board, epic, or project; and/or
  • One or more Confluence pages for additional narrative or requirements context.
• The user provide a high-level instruction, such as:
  • "Create a weekly status deck for these Jira issues."
  • "Generate a release review deck for all issues in this filter." 

2. Agent behavior

• Read the referenced Jira issues, and any specified Confluence pages, within the user's permissions.
• Extract all key information for stakeholders:
  • Overall status and progress.
  • Basic metrics (e.g., counts by status, done / in progress/ blocked).
  • Top risks, issues, and dependencies.
  • Notable changes or notable decisions made since the last report.
• Organize this into a slide structure, such as:
  • Title / cover.
  • Summary / key takeaways.
  • Progress and metrics.
  • Risks / issues / blockers.
  • Next steps / upcoming work.

3. Output / result

• Generate an editable `.pptx` file that:
  • Uses reasonable default layouts (e.g., titles, bullets, tables where appropriate).
  • Can be downloaded by the user from Rovo chat, and/or
  • Can be attached to a Jira issue or Confluence page (i.e., selected by the user).

Ideally this is exposed as a reusable "skill" that custom Rovo agents can call: e.g., "Generate a PowerPoint report from this context", so builders can incorporate it into their own agents.

Workaround

• Use a Rovo agent to create a text-based summary or structured report (e.g., headlines, bullets, tables).
• Copy / paste that content into a PowerPoint and manually:
  • Create slides
  • Reformat text, tables, and headings.
  • Update the deck (i.e., for each new reporting cycle).

These workarounds:

• Are time-consuming for teams that report weekly or bi-weekly.
• Introduce copy / paste errors and inconsistencies.
• Reduce the efficiency benefit of Rovo for end-to-end reporting.