Skip to main content
Skip table of contents

Portfolio Insights Rovo agent

What it is

Portfolio Agent is a Rovo agent for Portfolio by HeroCoders. It answers questions about capacity (overbooking) and delivery (dates vs progress, parent/child timelines) using the same rules as the Portfolio app. It is read-only: it analyses and explains; it does not edit Jira for you yet.

Portfolio Insights agent is availble on the latest Portfolio version for customers on Jira plans that include Rovo. As it uses Atlassian’s Rovo AI, we recommend independently verifying the insights provided before taking any critical actions based on them.

Prerequisites

Before Portfolio Agent can answer usefully, all of the following should be true. If something is missing, you may see errors, empty lists, or messages about configuration.

Prerequisite

Why it matters

Jira Cloud with Rovo available to you

The agent only runs inside Rovo chat; without Rovo (or if it is off for your site/profile), you cannot select or use the agent.

Portfolio by HeroCoders installed

The agent is part of this app; it reads portfolio rules and data through the app.

Portfolio app settings configured

Portfolio start and end fields (and related options your admin set) must exist; otherwise delivery checks (and related answers) may not run.
The portfolio time value field should be Original estimate or Remaining estimate. Other choices mean many capacity checks do not apply; the agent should tell you that instead of showing overload.

Data on issues

  • Portfolio start and end dates (whatever your admin mapped in Portfolio settings). Delivery alerts and date-based reasoning need both dates set where the rules apply. Issues without them often cannot be evaluated for delivery the same way.

  • Assignee. Capacity alerts are about people. Unassigned issues usually will not show personal overload for capacity in the same way.

  • Original or Remaining estimate (or the portfolio time value your site uses, when it is one of these). Capacity / overbooking logic for those features depends on estimates being present and distributed across dates; empty estimates mean little or no scheduled load to compare to capacity.

  • Realistic dates + estimates. Even with fields filled, zero-hour or very narrow plans may produce no alerts — that can mean “nothing flagged,” not “the agent is broken.”

Permissions to see the work

You must be able to view the issues, projects, and people you ask about in Jira; the agent cannot show what your user cannot access.

Correct agent selected

In Rovo chat, pick Portfolio Agent from the agent list. The generic assistant may not use this app’s actions.

How to talk to the agent?

  1. Open Rovo chat in Jira (Atlassian’s AI chat — the entry point depends on your Jira layout; it is usually a Rovo / chat icon or panel in the product chrome).

  2. Select the agent from the agent picker / dropdown (not the generic assistant, unless that is your only option).

  3. Choose Portfolio Agent (or the name your admin configured if it differs slightly).

  4. Type your question in natural language. You can use issue keys (CMS-1067), project keys (CMS) and users mentions (@JohnDoe).

Tip: If the agent picker is not visible, your site may need Rovo enabled or the app updated — ask your Jira admin.

What “unhealthy” usually means

In portfolio terms, an issue is often unhealthy if it has either:

Type

Meaning (plain language)

Capacity alert

The assignee looks overbooked on one or more days (workload vs capacity, per your Portfolio settings).

Delivery alert

Something is off about dates vs reality — e.g. past start with no progress, past end and not done, or child work past the parent’s end.

Broad questions like “list unhealthy issues” are intended to combine both views where applicable.

Example conversation (Q&A)

Use these as patterns; your real keys and names will differ.

Q1 — List problems in a project

Q: Please list unhealthy issues from the CMS project.

A (typical shape):

  • Explains that “unhealthy” = capacity and/or delivery alerts.

  • Capacity alerts: e.g. issues where the assignee is overbooked on specific dates (with issue keys and assignee name).

  • Delivery alerts: a list of issue keys that fail delivery checks.

Q2 — What is wrong with one issue?

Q: CMS-1009 — what’s wrong with it?

A (example):

  • States the main reason (e.g. “past its end date and not done”).

  • Clarifies capacity separately when relevant (e.g. “no capacity alert for this issue”).

Q3 — Link to Capacity planner

Q: Can you show the capacity planner link for CMS-1067?

A (typical shape):

  • A clickable link titled something like Capacity planner for [assignee name] (planner is for the person, not the issue key — the issue is used to find the assignee).

  • Short note that the link opens workload / overbooking detail in Portfolio.

Q4 — How to fix a capacity alert

Q: How can I resolve the capacity alert for CMS-1067?

A (typical shape — general guidance, not automatic fixes):

  1. Reschedule the issue so work falls on days where the assignee is not overloaded.

  2. Reassign to someone with free capacity.

  3. Reduce estimated work so it fits the window.

  4. Split the work across days or people.

  5. Open Capacity planner (link again) to see overload and adjust dates or assignments with full context.

More questions you can try

Your goal

Example question

Overall health of one issue

“Is PROJ-123 healthy from a portfolio perspective?”

Capacity only

“Is the assignee overbooked on ABC-2?”

Many issues in one project

“Which issues in PROJ have a capacity alert?”

Several projects

“Which issues in PROJ and ABC have a delivery alert?”

Person + time

“Is [name] overbooked this week?” / “How many days are they available next week?”

Good to know

  • Project lists usually focus on non-Done work (status category Done excluded unless you ask differently where supported, e.g. includeDone for assignee-window style questions).

  • Large projects: results can be capped (Portfolio Agent analyses up to 5000 issues); the agent may say results could be incomplete.

  • Capacity need portfolio Original or Remaining estimate as the time value field; otherwise capacity checks may not apply and the agent should say so.

  • Weeks in time windows are ISO (Monday–Sunday).

If something fails

  • “Settings not configured” / missing start or end field → your Jira admin must finish Portfolio app settings.

  • Ambiguous person → use a clearer name or ask for the assignee’s capacity planner link from a known issue they own.

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.