Portfolio by HeroCoders Documentation

Portfolio Insights Rovo agent

What it is

Portfolio Insights Agent helps teams find the right people for the right work faster, and identify any potentail risks before overbooked schedules, missing expertise, or delivery risks slow you down. Ask questions in Portfolio Insights chat like ‘Do we have a developer available next week?’ and get clear, read-only explanations of capacity, risks, roles, and skills using the same rules as Portfolio by HeroCoders - so you can see what needs attention and choose the next best action with confidence.


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 Booking 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

  • Booking 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 Insights Agent from the agent list. The generic Rovo assistant don’t 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 Insights Agent.

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

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.

Questions you can ask

Try questions like these — use your own project keys, issue keys, names, roles and skills.

Q1 — Find problems in a project

Q: What looks unhealthy in the CMS project?

A: A short list of issues with capacity or delivery alerts, including the issue keys, people affected and the reason each item needs attention.

Q2 — Understand one issue

Q: What’s wrong with CMS-1009?

A: A quick explanation of the main problem, such as missed dates, unfinished work or whether the assignee has a capacity alert.

Q3 — Open the right capacity view

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

A: A link to the assignee’s capacity planner, plus a short note about what you can check there.

Q4 — Get ideas for fixing an alert

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

A: Practical options, such as rescheduling the work, reassigning it, reducing the estimate or splitting it across days or people.

Q5 — Find someone with the right role or skill

Q: Do we have a developer with Java available next week for a 10 hour task?

A: A list of matching people, if any, with their role or skill match and whether they appear to have enough availability in the requested time window.

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.